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).
MBender I've encountered a similar issue before, and it can indeed be frustrating to pinpoint the cause. Based on what you've described, it does seem likely that your firewall/proxy setup is causing this. To get a better understanding, you might want to check the configuration of your firewall or proxy, especially how it handles the traffic between your public URL and your internal network address.
Additionally, you could look into the server logs or any error messages to see if there's more specific information about why these "Administer Security" operations are failing when using the public URL. Sometimes, error logs can provide valuable clues.
Lastly, you may consider reaching out to your firewall/proxy vendor's support or community forums to see if others have encountered a similar issue and found a solution. They might be able to provide specific guidance based on your setup.
Troubleshooting Windows Server Errors
Hope this helps, and good luck with resolving this!