Unable to connect to AWS ECR if proxy is set within Octopus and outbound traffic is restricted #6843
Open
5 tasks done
Labels
area/core
feature/packaging
kind/bug
This issue represents a verified problem we are committed to solving
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.
Prerequisites
The bug
Unable to connect to an AWS ECR if outbound traffic is blocked on the network and proxy details are set within Octopus.
What I expected to happen
If the proxy settings are entered, it should be able to connect to AWS ECR
Steps to reproduce
Haven't reproduced
Screen capture
N/A
Log excerpt
Affected versions
Octopus Server:
Workarounds
Setting the proxy at the OS level will work
Links
Internal link - https://octopus.zendesk.com/agent/tickets/67788
We (not me, JW - ty!) noticed that the code for this may not work using a proxy'd configuration from the web request proxy setting - https://github.com/OctopusDeploy/OctopusDeploy/blob/master/source/Octopus.Core/Packages/AwsElasticContainerRegistry/AwsElasticContainerRegistryCredentials.cs#L75-L77
The text was updated successfully, but these errors were encountered: