-
Hey, I've been wanting to cut back on exposed ports and thus wanted to use hostnames in my proxy hosts. I have encountered one problem with hostnames so far:
Edit: with ip's:
Same issue appears when trying to curl My compose.yml: services:
nginx:
image: jc21/nginx-proxy-manager:2.11.0
restart: unless-stopped
ports:
- 80:80
- 81:81
- 443:443
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
networks:
- proxy
networks:
proxy:
driver: bridge services:
pingvin:
image: stonith404/pingvin-share:v0.21.5
restart: unless-stopped
volumes:
- ./data:/opt/app/backend/data
- ./public:/opt/app/frontend/public
networks:
- nginx_proxy
networks:
nginx_proxy:
external: true Can someone help me figure this out? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 24 replies
-
First issue what is see is that your npm network is proxy not nginx_proxy so pleae put your pingvin container to the proxy network ;) |
Beta Was this translation helpful? Give feedback.
-
I have the exact same problem with any other container connected to NPM using an internal network: works with IP, not working with the container name (i.e. |
Beta Was this translation helpful? Give feedback.
I did actually try every version from
0.20.0
to0.21.5
, so the actual issue turns out to be that the files generated by0.21.5
are corrupted or something. Upgrading from0.21.0
to0.21.5
works fine.I'll close this discussion now