Can't access Portainer through NGINX Proxy Manager

[tealtxgr]

Ask a Question!

I'm running into an issue where, with npm, any way I try to access Portainer redirects me to a /login page, which then 404s. If I access it with the IP directly then it's totally fine. I've tried the following configurations:

• directing NPM to /portainer
• directing NPM to 172.17.0.1
• directing NPM to my public IP

Tried all three with ports 9443 and 9000, while portainer shares a network with npm.
My friend is using Portainer behind NPM and I copied his configuration and it still didn't work.
Anytime I try to connect to it, it leads me to a /login page which leads me to believe that npm is "correctly" directing traffic but I always hit the same 404.

Here's my compose file:

services:
  portainer:
    image: portainer/portainer-ce
    container_name: portainer
    restart:  always
    environment:
      - VIRTUAL_HOST=same.url.in.npm
      - VIRUTAL_PORT=9443
    ports:
      - '9443:9443'
      - '9000:9000'
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - portainer_data:/data
    networks:
      - urlbridge

networks:
  urlbridge:
    external: true

volumes:
  portainer_data:
    external: true

I've tried many different things here, like specifying the same version of portainer-ce, not using env variables, different ports, etc.

What am I doing wrong?

[tealtxgr]

I am sorry, this ended up being a browser issue. I have no idea why it's happening but it's neither npm or Portainer, it's my browser. Sorry all!

[hafidzlvm]

I GOT THE SAME ISSUE, AND HAVE BEEN DEBUGGING FOR A WHILE, 😮‍💨 , its kinda frustated, but yeah what ever, it is what it is, i just relized it after i saw this discussions. thank you so much for give that anwser