-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy - WebApp Health Check Performed on Server Doesn't Respect Custom Proxy #7544
Proxy - WebApp Health Check Performed on Server Doesn't Respect Custom Proxy #7544
Comments
Starting work on this now. I'm using Squid proxy in a Docker container as my proxy for testing. You can run up an instance with: docker run --rm --name squidproxy -p 3128:3128 datadog/squid then set your proxy to docker exec squidproxy tail -f /var/log/squid/access.log |
I've identified the root cause of this. There's a bug in the underlying Azure SDK library we use to run the Health Check, which doesn't respect the Proxy settings that have we configured when establishing a connection to Azure. The health-check uses a specific method in the SDK which the deployment behaviours don't use, which is why this shows up only for the health-check. The replacement library is still in beta, but it sounds like the old version which we're using is in maintenance mode and not receiving further fixes. I've checked in with MS on that linked issue, but in the meantime I'm re-writing the health-check to use the newer SDK. The health check is low enough complexity that I'm happy to use the beta version, but I don't want to touch the deployment code itself until the new SDK stabilises. |
Fixes OctopusDeploy/Issues#7544 Updates the HealthCheck to use the new version of the Azure SDKs. It's in beta, so not touching the actual deployment code at this stage.
The fix has been merged into the |
Release Note: Fixed an issue where the configured Web Request Proxy was not respected in Health Checks for Azure App Service deployment targets |
🎉 The fix for this issue has been released in:
|
Team
Severity
Workaround Exists
Version
Found in 2022.1.2133 but confirmed in latest
Latest Version
I could reproduce the problem in the latest build
What happened?
When configuring a Custom Proxy for Octopus Web Requests, the proxy isn't used when performing an Azure WebApp health check directly on the Octopus Server.
Proxy is used when using the proxy server configured in Internet Explorer.
Reproduction
Error and Stacktrace
More Information
Previous issue:
#6958
Workaround
Either run the Azure WebApp health check from Tentacle or configure the Proxy within Windows:
The text was updated successfully, but these errors were encountered: