Hi there,
I’m testing rancher in a corporate environment but on AWS, where everything is running through a proxy and any new URL must be permitted through the proxy.
Setting up rancher with my own private AWS account and adding custom hosts work great, in the corporate environment I’m getting the “Timeout getting IP address”. I see that the host is registering on the server but most of the stacks (healthcheck, ipsec, schedular) do not come up.
The rancher server and the agent are on 2 separate AWS Instances, but using the same AZ and can perfectly reach each other.
Here’s how I start the server:
docker run -d --restart=unless-stopped -p 8080:8080 \ -e http_proxy=xxxxxx \ -e https_proxy=xxxxxx \ -e no_proxy="xxxxxx" \ -e NO_PROXY="xxxxxxxx" \ rancher/server
And here’s how I start the agent:
docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher \ -e http_proxy=xxxxx \ -e https_proxy=xxxx \ -e no_proxy="xxxxx" \ -e NO_PROXY="xxxxx" \ -e CATTLE_AGENT=10.53.121.18 -e CATTLE_AGENT_IP=10.53.121.18 \ rancher/agent:v1.2.9 \ http://10.53.126.69:8080/v1/scripts/C56ACC25E0CAE88F9083:1514678400000:EEHRvQ7BuEsae7bOzKG7hm8t5Y
Where 10.53.121.18 is the IP Address of the rancher-agent. I hope I understood this correctly.
The following ports are open through a security group
TCP: 80, 8080, 22, 443, 2379, 8081, 8085
UDP: 500,4500
I’m almost certain that the error has to do with a port or a URL that must be permitted, only rancher-agent is not telling alot what it is trying to do.
Any idea how to dig deeper?
Thanks and cheers