Forum Discussion
Solved
DevOps on-prem, public URL and 500: Internal Server Error
In our current on-prem DevOps setup the server exposed via our firewall's proxy. Most (if not all) operations are unaffected - people can access the DevOps site, log in, and generally perform operati...
Yeah, we managed to get it resolved but it's dependant on the edge device.
In our case it's a Sophos UTM which was the culprit (see https://community.sophos.com/utm-firewall/f/hardware-installation-up2date-licensing/132837/waf-issues-after-updating-to-9-709-3 for a lengthy topic on the issue). Ultimately Sophos released a workaround, which is setting a "Proxy100Continue Off" flag in the reverse proxy config on the edge device (see https://support.sophos.com/support/s/article/KB-000044067 for Sophos KB article on the workaround).
Did you discover any resolution for this issue since you posted it? I came across this question while trying to resolve this same issue in our organization. The end user website and git repositories are available remotely only when the Public URL is set to the internal machine name, but I am getting a 500 error when trying to add the server to my Visual Studio connection manager. It works just fine when connecting from within the local network, just not across the firewall boundary. Like you, I am assuming something is being blocked.
Yeah, we managed to get it resolved but it's dependant on the edge device.
In our case it's a Sophos UTM which was the culprit (see https://community.sophos.com/utm-firewall/f/hardware-installation-up2date-licensing/132837/waf-issues-after-updating-to-9-709-3 for a lengthy topic on the issue). Ultimately Sophos released a workaround, which is setting a "Proxy100Continue Off" flag in the reverse proxy config on the edge device (see https://support.sophos.com/support/s/article/KB-000044067 for Sophos KB article on the workaround).
MBenderAbsolutely brilliant. Ours is also a Sophos UTM and I have no doubt this will be our solution. Thank you!