0

Outcome

Able to run and access sitecore container within Corporate VPN network (Global Protect) so that we can rollout sitecore docker container practice for all developers.

Problem

We managed to get the container running with various hacks such as copying zscalar root cert and setting InterfaceMetric priority to low etc. However, I can access the sitecore only when disconnecting from VPN. As soon as I connect to VPN (Global Protect), I see this error below:

enter image description here

Not able to find any concrete solution at the moment. Keen to hear how you've rolled Sitecore Docker practices to your corporate network.

4
  • What worked for me, was ensuring that I was logged into Sitecore in CM, browse some URLs in CD, and browse some more URLs on whatever Rendering Host you have setup, whilst Global Protect is disconnected. Then reconnecting to Global Protect, the connection somehow remains between the containers and everything works. Your mileage may vary depending on your corporate VPN setup. Oct 13 at 2:50
  • You (your IT team) need to update the Global Protect settings. This is not something you are going to solve otherwise.
    – Mark Cassidy
    Oct 13 at 7:29
  • See also forums.docker.com/t/…
    – Mark Cassidy
    Oct 13 at 10:36
  • Are you routing all your traffic through the VPN or is it a split tunnel? If you are on a split tunnel then you(/IT) could route the .local traffic away from the VPN. A tool like proxifer gives lots of flexibility around this but it would be best to talk to the team that administer the Global Protect VPN. 2 days ago

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.