-
Notifications
You must be signed in to change notification settings - Fork 36
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 #52
Comments
hm, |
Here is my Docker Compose file. Everything was functioning until I upgraded Docker. I attempted to revert to the previous version, but it no longer works.
|
I tried to update /etc/nginx/sited-enabled/sharelatex.conf with this overleaf/overleaf@2514570 |
It seems that overleaf is just not starting. When I try to run it manually in the container I get:
|
I can confirm that vanilla sharelatex 4.2 or 4.2.4 container is working properly |
Can you post the Dockerfile you are using as well?
|
Dockerfile:
And yes, I did run that scripts. |
I have instances running with: hm, did you extract the files for exactly the same version you use in the Dockerfile? |
I somehow have problems starting my running overleaf container since I updated docker to |
For me the only thing which helped was to downgrade Docker back to the previous version:
I did get the normal sharelatex:5 container running on the latest docker version though - so we should find a upgrade way to sharelatex:5 using ldap soon :) |
The reason for this is ipv6 support in docker 26. |
For me, I have encountered the same 502 Bad Gateway error and fixed it following this guide - my instance is deployed on K8S |
Hi guys. Thank you for the great project. After setting everything up and following the readme, I am getting a
502 Bad Gateway error
when trying to reach the login page. I can confirm that MongoDB and Redis are started and working properly. In the Docker Compose logs, there are no errors on start, and I can see that the database is replicated properly.I found the following error in the Nginx error logs:
Then I went into the Docker container and found that indeed there is nothing on port 4000:
Here is what I found in
/var/log/sharelatex/web.log
. Could this error be related to my issue?Thank you in advance! And please let me know if I can provide any additional logs?
The text was updated successfully, but these errors were encountered: