8000 502 Bad gateway error with latest version 5.3.2 · Issue #1325 · overleaf/overleaf · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

502 Bad gateway error with latest version 5.3.2 #1325

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

Open
wakawakaaa opened this issue Mar 14, 2025 · 4 comments
Open

502 Bad gateway error with latest version 5.3.2 #1325

wakawakaaa opened this issue Mar 14, 2025 · 4 comments

Comments

@wakawakaaa
Copy link

With new Docker image (sharelatex/sharelatex:5.3.2) there is nothing runs on 4000, and I get 502 Bad Gateway error, Is there any one have fix for it? Thanks

root@8f2ec5328495:/overleaf# netstat -tulpn
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:8080            0.0.0.0:*               LISTEN      202/nginx: master p
tcp        0      0 127.0.0.1:3054          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3049          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3048          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3042          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3036          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3026          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3016          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3013          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3010          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3009          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:3003          0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.11:46723        0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      202/nginx: master p
tcp6       0      0 :::3100                 :::*                    LISTEN      -
tcp6       0      0 :::10843                :::*                    LISTEN      -
udp        0      0 127.0.0.11:39936        0.0.0.0:*                           -
@wakawakaaa wakawakaaa changed the title 502 Bad gateway error with latest version 502 Bad gateway error with latest version 5.3.2 Mar 14, 2025
@eric-gitta-moore
Copy link

google pls.

I can follow this #1188.

@wakawakaaa
Copy link
Author

@eric-gitta-moore I have already long time search for it, same issue was in the past with old overleaf version and it seems came back again. the issue #1188 has nothing to do with this. This issue overleaf/sharelatex service do not start at port 4000 which is basically mentioned in nginx config file inside docker. please let me know the fix if you know it. Thanks. Just to mention mongo db works fine in my case.

@eric-gitta-moore
Copy link
eric-gitta-moore commented Mar 17, 2025

I don't seem to have any problems here, just start new one as docker compose up -d

#1188 (comment)

root@c7a29a54af9e:/overleaf# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
> tcp        0      0 127.0.0.1:4000          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3009          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3010          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3042          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3013          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.11:35173        0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3016          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3048          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3049          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3054          0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      205/nginx: master p 
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      205/nginx: master p 
tcp        0      0 127.0.0.1:3026          0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:3000            0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3003          0.0.0.0:*               LISTEN      -                   
tcp        0      0 127.0.0.1:3036          0.0.0.0:*               LISTEN      -                   
tcp6       0      0 :::10843                :::*                    LISTEN      -                   
tcp6       0      0 :::3100                 :::*                    LISTEN      -                   
udp        0      0 127.0.0.11:42959        0.0.0.0:*                           -                   

image hash:

sharelatex/sharelatex@sha256:3046aa526f5816c5c11758e743055df56f2335e85070b84fe5f86f0ecbb0884d

@wakawakaaa
Copy link
Author

@eric-gitta-moore Thanks for reply. I have tried to dig more into it and found out that when docker-compose.yml run directly after git clone repo then it works.
but as soon as you dont have git clone repo and tries to run only docker-compose.yml it dont work, can not connect to mongo db. It is strange to always pull repo and docker image can not just run independantly.
Please let me know if you have any fix for this. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0