When Chocolatey Agent is installed on a machine that sits behind an NGinx proxy, the proxy settings that have been applied to Chocolatey explicitly appear to be ignored, which results in the following error in the chocolatey-agent.log file:
The follow error is produced during the reporting process:
There was no endpoint listening at https://dummyurl.com/ChocolateyManagementService
What is Expected?
The agent picks up Chocolatey's explicit proxy settings and is able to communicate to the Chocolatey Central Management service.
How Did You Get This To Happen? (Steps to Reproduce)
Install Chocolatey
Configure explicit proxy settings
Configure Chocolatey for Central Management with config updates and installation of the chocolatey-agent package
Restart agent to force a check-in
Observe error in the agent log
Code for Reproduction Steps
There is a similar but not exact configuration for NGinx available for the reproduction of this issue in the linked ZenDesk ticket. I will admit it is a lot of effort to get this to a state where Engineering can reproduce it.
System Details
Operating System: Server 2019
Windows PowerShell Version: 5.1
Chocolatey CLI Version: 1.4.0
Chocolatey Licensed Extension version: 5.0.2
Chocolatey License type (Professional / Business / ?): Business
These are the steps that must be completed to consider the issue as 'Done' and the label added. Depending on the bug there maybe additional factors that need to be considered such as documentation being updated, manual or automated tests being added to ensure we detect the bug in future, etc. Please add and remove steps as needed.
[ ] Documentation has been updated.
[ ] Automated tests have been added to cover this bug.
[ ] Manual tests have been added to cover this bug.
What You Are Seeing?
When Chocolatey Agent is installed on a machine that sits behind an NGinx proxy, the proxy settings that have been applied to Chocolatey explicitly appear to be ignored, which results in the following error in the chocolatey-agent.log file:
The follow error is produced during the reporting process:
What is Expected?
The agent picks up Chocolatey's explicit proxy settings and is able to communicate to the Chocolatey Central Management service.
How Did You Get This To Happen? (Steps to Reproduce)
Code for Reproduction Steps
There is a similar but not exact configuration for NGinx available for the reproduction of this issue in the linked ZenDesk ticket. I will admit it is a lot of effort to get this to a state where Engineering can reproduce it.
System Details
Output Log
Workarounds
Proposed Solution
Related Issues and Tickets
Zendesk Ticket Slack thread with additional context
Done Checklist
These are the steps that must be completed to consider the issue as 'Done' and the label added. Depending on the bug there maybe additional factors that need to be considered such as documentation being updated, manual or automated tests being added to ensure we detect the bug in future, etc. Please add and remove steps as needed.
┆Issue is synchronized with this Gitlab issue by Unito