-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] nginx container starts but no tcp ports exposed #164
Comments
I am not sure how you set up your Portainer network to help you troubleshoot. Can you take some screenshots? |
i tried also from docker-compse command from command line with same result |
After you start the docker-compose command, can you run |
here is the output:
|
This looks identical to my output as well. From another machine, if you try to ping your server, does it get through? And what is the output when you try to do Did you perform the docker-compose command on a different VM/machine or on the same VM/machine that runs Portainer? |
curl http://192.168.1.xxx:2283/server-info/ping |
all other container i have the tcp port are working wihtout any problem also the postgres |
So you are running this on the same VM that runs Portainer, correct? Can you change the binding port of Maybe nginx:
container_name: proxy_nginx
image: nginx:latest
volumes:
- ./settings/nginx-conf:/etc/nginx/conf.d
ports:
- 2283:80
- 2284:443
[...] |
curl http://192.168.1.112:12283/server-info/ping |
seems to be something related to nginx proxy not working this container also has no log working ~ docker logs proxy_nginx
|
You can comment out the logging:
driver: none in |
this is the nginx log:
|
AH I see, it is looking for the |
ok now it's working. |
Hello eveybody
can't access port 2283 or 2284
l: (7) Failed to connect to 192.168.1.xxx port 2283 after 0 ms: Connection refused
on portainer nginx container starts but no tcp port exposed
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: