Skip to content
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

502 Bad Gateway, Mikrotik #297

Open
Men1steR opened this issue Jul 1, 2023 · 2 comments
Open

502 Bad Gateway, Mikrotik #297

Men1steR opened this issue Jul 1, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@Men1steR
Copy link

Men1steR commented Jul 1, 2023

Current Behavior

Hi all!
I use this container on mikrotik host, the webserver is also in docker on the same bridge, on the network 10.17.224.0/27, but when I connect, I get 502 Bad Gateway, packets from container don't even go out towards the webserver

Expected Behavior

No response

Steps To Reproduce

No response

Environment

  • OS: ROS 7.10.1

Container creation

Created a container using Mikrotik, forwarding only the storage

Container log

I can’t look, but if you tell me where they are in the container, I’ll get them

Container inspect

No response

Anything else?

No response

@Men1steR Men1steR added the bug Something isn't working label Jul 1, 2023
@jlesage
Copy link
Owner

jlesage commented Aug 4, 2023

Did you try to connect to the container (docker exec -ti <container name> sh) and then ping the IP of the web server ?

The container's log can be obtained by executing docker logs <container name>. The output of docker inspect <container name> would also be useful to have the full configuration of the container.

You should also share the configuration of your proxy host.

@tan00
Copy link

tan00 commented Nov 8, 2023

I have same error , the nginx log is

/config/log # cat fallback_error.log
2023/11/08 15:40:10 [error] 403#403: *12 connect() failed (111: Connection refused) while connecting to upstream, client: 10.10.100.200, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "10.10.100.47:8181", referrer: "http://10.10.100.47:8181/login"

upstream 127.0.0.1:3000 is not listen

/config/log # netstat  -lntp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:4443            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:8181            0.0.0.0:*               LISTEN      -
tcp        0      0 :::4443                 :::*                    LISTEN      -
tcp        0      0 :::8080                 :::*                    LISTEN      -
tcp        0      0 :::8181                 :::*                    LISTEN      -

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants