portainer/portainer-compose

Stucked to: Connecting to the Docker endpoint...

pascalandy opened this issue · 13 comments

pascalandy commented

Hey Tony!

I'm running a docker stack with Traefik, Wordpress, Nginx, Caddy, Whoami and Portainer.
For some reason Portainer don't want to launch ...

screen shot 2017-09-20 at 11 14 21 pm

Do you want to take a look? You'll see you can run the whole stack via one command via play-with-docker.

I would really like to have Portainer to be part of this Docker Stack boiler template.

Thanks in advance!
Pascal

deviantony commented

Hey @pascalandy

I had a quick look, I think that this might be related to the reverse proxy configuration.

Are you sure about the traefik options passed here:

      labels:
        - "traefik.backend=portainer"
        - "traefik.frontend.rule=PathPrefixStrip:/portainer"
        - "traefik.port=9000"
        - "traefik.enable=true"
        - "traefik.frontend.entryPoints=http"
        - "traefik.docker.network=ntw_front"
        - "traefik.weight=10"
        - "traefik.frontend.passHostHeader=true"

Ah, I was able to access Portainer using http://pwd10-0-33-3-80.host1.labs.play-with-docker.com/portainer/ instead of http://pwd10-0-33-3-80.host1.labs.play-with-docker.com/portainer

Note the trailing slash in the first URL.

  • 👍2
pascalandy commented

Good catch! I updated the stack.

Traefik was having issue about this few months ago and they fixed this. I know there is now labels to handle this use case.

Many many cheers!

EDIT: See how it's done here: https://github.com/pascalandy/docker-stack-this/blob/master/traefik_stack5/toolportainer.yml#L55

  • 👍2
kylesnipes commented

@pascalandy Did you ever resolve this issue? I'm now running v1.6 of Traefik and this issue is happening to me. Without the trailing '/', portainer won't hit the login page.

ttresse commented

Hello
I have the same issue here ! Any news ?

  • 👍2
Dave3991 commented

Hello,
same problem here (traefik 1.6) , any updates ?

  • 👍1
exNewbie commented

It is happening to me too

# cat /etc/*release
NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
Amazon Linux AMI release 2018.03

# rpm -aq | grep docker
docker-18.06.1ce-6.24.amzn1.x86_64

# docker images 
REPOSITORY                                                        TAG                  IMAGE ID            CREATED             SIZE
portainer/portainer                                               latest               89c72b64ab63        5 days ago          74.2MB
staticgroup commented

Hey guys,
simmilar issue here with nginx, was working initially now its stuck at this point. I followed the config guide

staticgroup commented

Just following up on the above comment

exNewbie commented

@SConnery surely nobody cares about this issue. I also contacted them on Slack but got ignored :|

staticgroup commented

yep i did as well :(
trying 2 docker servers to try this.

deviantony commented

Shipping this compose setup with a valid reverse proxy configuration (using jwilder/nginx), should be fixed via #20

staticgroup commented