While trying to install a second node to a DT Managed cluster, we get the following error:
Failed to send GET request to https://10.69.0.29:8021/api/v1.0/control/serverMa... error 2 - connection error: (...)1): Max retries exceeded with url: /api/v1.0/control/serverManagement/operationState (Caused by ProxyError('Cannot connect to proxy.', error('Tunnel connection failed: 403 Tunnel or SSL Forbidden',)))
10.69.0.29 is the IP of the primary cluster node from which we downloaded the installer using the wget command. We can still reach that host using other various commands (ping, telnet, etc.). Since the two nodes are on the same network segment, there should be no proxy involvement at all. The ports between the two nodes are also open in the firewall rules.
Solved! Go to Solution.
The client is convinced that there is no proxy between the two nodes.
One thing that may be creating an issue is that, in the management console, we set up the proxy settings for connecting to DT Mission Control. Would the installer package be trying to use the same proxy settings to connect to the initial node and failing since the proxy is not involved in this connection?
Alright, so do we clear out the proxy settings on the Managed cluster before adding more nodes? It seems odd that those would be inherited by the installer.
Just to make sure, I am talking about these proxy settings in DT Managed console. https://www.dynatrace.com/support/help/deploy-dynatrace/managed/configuration/can-i-use-a-proxy-for-internet-access/
No we don't clear them. New node will get the same proxy setting from the seed node. There's also no proxy defined to connect to the other node. So this is definitely your network related issue.
I have the same problem
I want to add a second node to the first, but when I run the command to download the .sh package, i get a 404 error
Proxy request sent, awaiting response... 404 not found
@Gregory J. there should be a workaround for this. In the config.properties in server's configuration, there are several sections beginning with name http.client , each setting is used for different connection type (opc / external requests / ... )
So to turn off proxy for a type of connection, just add:
proxy-off = true
To the appropriate section to the config.properties and restart the dynatrace-server process.