Using Monaco with a proxy server
In network environments where access to Dynatrace API endpoints is only possible or allowed via a proxy server, the Dynatrace Monaco CLI provides an option to specify the address of your proxy server when running a command. For details, see the documentation.
Troubleshooting tips
If you're having issues reaching your Dynatrace environment via a proxy, this guide collects frequent issues and troubleshooting tips.
In general, a good indicator that there are problems with your proxy configuration are error logs of the following form, mentioning `proxyconnect`:
2023-12-05T12:00:00+01:00 error : HTTP request failed: : proxyconnect tcp: dial tcp:
Issue | Solution |
| HTTP_PROXY (HTTP) is set, but the connection fails. | HTTPS_PROXY (HTTPS) is needed for the configuration to apply to HTTPS connections to the environment. |
| The proxy connection works for some commands but not others. | Ensure the environment variable is set for the current terminal session or command that you're executing. |
| The proxy connection works from one machine but not from another. (For example, it works on a local device but not a Dynatrace laptop.) | Ensure you're connected to the same network and there are no other network configurations (e.g. a firewall) that allow only specific devices to connect to the proxy server. |
| The proxy URL contains a username/password with special characters, and the connection fails. | Ensure that the whole value of HTTPS_PROXY is URL encoded. Special characters that are not correctly encoded will lead to the value being parsed incorrectly. |
In network setups requiring a proxy, it is recommended to involve internal network experts (e.g. the IT department) as early as possible.
There are often additional factors and rules to networking that are not related to functional or configuration issues of Monaco and can't be addressed by Dynatrace Support.
