You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, as the title suggests I can't reverse proxy to the app, which is how I handle TLS certificates.
I expose the app to traefik by connecting it on the proxy network, which traefik watches for to automatically route traffic. Additionally, the container is on the peppermint_default network automatically generated by docker-compose, which is how it connects to the database.
I notice that the app is only listening to traffic on the interface for peppermint_default, as you can see in this image:
Judging from the output of running docker container inspect peppermint (irrelevant lines truncated), we can see that it is listening only to the interface on peppermint_default network, not proxy:
For the time being, I can work around by directly exposing the port to localhost using docker-compose and then setting up traefik to route to that port, but I feel it would be a cleaner solution to have the service listen on 0.0.0.0 to avoid this happening in the first place.
I was wondering if it was possible to change this behavior?
The text was updated successfully, but these errors were encountered:
I faced a similar issue and resolved it by using an additional NGINX reverse proxy inside the docker-compose.yml file. Below is the configuration I used:
Hi, as the title suggests I can't reverse proxy to the app, which is how I handle TLS certificates.
I expose the app to traefik by connecting it on the
proxy
network, which traefik watches for to automatically route traffic. Additionally, the container is on thepeppermint_default
network automatically generated by docker-compose, which is how it connects to the database.I notice that the app is only listening to traffic on the interface for
peppermint_default
, as you can see in this image:Judging from the output of running
docker container inspect peppermint
(irrelevant lines truncated), we can see that it is listening only to the interface onpeppermint_default
network, notproxy
:For the time being, I can work around by directly exposing the port to localhost using docker-compose and then setting up traefik to route to that port, but I feel it would be a cleaner solution to have the service listen on 0.0.0.0 to avoid this happening in the first place.
I was wondering if it was possible to change this behavior?
The text was updated successfully, but these errors were encountered: