rancher: rancher doesnt update var/lib/rancher/etc/agent.conf properly

I am running Rancher behind a HTTPS Proxy with Apache using a signed SSL certificate, I can connect to Rancher server normally via browser, but the Rancher agent is unable to connect to the server.

The Rancher agent log says:

ERROR: https://my-server/v1 is not accessible

But I can invoke that URL in the browser without problems:

image


Useful Info
Versions Rancher v1.1.0 Cattle: v0.165.4 UI: v1.1.12
Access Disabled
Orchestration Cattle
Route hosts.new.index

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 16 (1 by maintainers)

Most upvoted comments

I change the title of this and added the bug label.

I think there is a legitimate bug here around how we manage /var/lib/rancher/etc/agent.conf. It could be that we are not updating this file properly if the environment changes.

Also, it looks like we have an issue that causes the agent to not be able to connect at all. We could perhaps make rancher more resilient to a bad config in that file.

I have a kind of the same issue. i think its the socket connection trying to connect with http.

Caddy Server Proxy logs: http: response.Write on hijacked connection

maybe you should give some info about your os and your docker version.

i got the same problems running rancher v1.0.1 with docker 1.11 and Ubuntu 16.04. back then (#4630) i switched to ubuntu 14.04 with docker 1.10.3 and it worked, but with rancher v1.1.0 i cant tell.