Comments (12)
I solved this by adding this to my docker-compose.yml. And make sure you are using the docker-compose v2 API. (docker compose up
instead of old way docker-compose up
)
services:
[...]
overleaf:
[...]
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
This will disable ipv6 for this container at all.
from overleaf.
@mlevans0 At least on my machine 5.0.1 works fine without any changes - I upgraded yesterday already... Don't know about OP, though!
from overleaf.
I get the same error, but just running the container with native linux. Its the same image I build two weeks ago. Did not find the error, yet.
Edit 1: Found this in the logs. There are no more error logs.
{"name":"filestore","hostname":"01b21db226d3","pid":141,"level":40,"err":{"message":"We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.\n\nPlease migrate your code to use AWS SDK for JavaScript (v3).\nFor more information, check the migration guide at https://a.co/7PzMCcy","name":"NOTE","stack":"NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.\n\nPlease migrate your code to use AWS SDK for JavaScript (v3).\nFor more information, check the migration guide at https://a.co/7PzMCcy\n at emitWarning (/overleaf/node_modules/aws-sdk/lib/maintenance_mode_message.js:37:13)\n at Timeout._onTimeout (/overleaf/node_modules/aws-sdk/lib/maintenance_mode_message.js:45:5)\n at listOnTimeout (node:internal/timers:569:17)\n at process.processTimers (node:internal/timers:512:7)","info":{}},"msg":"Warning details","time":"2024-03-22T10:25:04.121Z","v":0}
Edit 2: After further investigation:
root@01b21db226d3:/var/log# 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.11:44207 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 135/nginx: master p
tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 135/nginx: master p
tcp6 0 0 :::3100 :::* LISTEN -
tcp6 0 0 ::1:4000 :::* LISTEN -
tcp6 0 0 ::1:3042 :::* LISTEN -
tcp6 0 0 ::1:3054 :::* LISTEN -
tcp6 0 0 ::1:3048 :::* LISTEN -
tcp6 0 0 ::1:3049 :::* LISTEN -
tcp6 0 0 ::1:3013 :::* LISTEN -
tcp6 0 0 ::1:3010 :::* LISTEN -
tcp6 0 0 ::1:3009 :::* LISTEN -
tcp6 0 0 ::1:3016 :::* LISTEN -
tcp6 0 0 ::1:3026 :::* LISTEN -
tcp6 0 0 ::1:3036 :::* LISTEN -
tcp6 0 0 ::1:3005 :::* LISTEN -
tcp6 0 0 ::1:3003 :::* LISTEN -
tcp6 0 0 :::10843 :::* LISTEN -
udp 0 0 127.0.0.11:52238 0.0.0.0:* -
root@01b21db226d3:/var/log# curl http://127.0.0.1:4000
curl: (7) Failed to connect to 127.0.0.1 port 4000: Connection refused
root@01b21db226d3:/var/log# curl -vvv http://[::1]:4000
* Trying ::1:4000...
* TCP_NODELAY set
* Connected to ::1 (::1) port 4000 (#0)
> GET / HTTP/1.1
> Host: [::1]:4000
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
[...]
Checking the nginx config
root@01b21db226d3:/var/log# cat /etc/nginx/sites-enabled/sharelatex.conf
server {
listen 80;
server_name _; # Catch all, see http://nginx.org/en/docs/http/server_names.html
root /overleaf/services/web/public/;
# block external access to prometheus /metrics
location /metrics {
internal;
}
location / {
proxy_pass http://127.0.0.1:4000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_read_timeout 10m;
proxy_send_timeout 10m;
}
location /socket.io {
proxy_pass http://127.0.0.1:3026;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_read_timeout 10m;
proxy_send_timeout 10m;
}
[...]
Seems like nodejs is only listening on net6 address, but nginx tries to proxy to net4 address.
Edit 3:
After changing the nginx-conf to proxy to [::1]
, I get at least the mainentance site.
But after this, I have ... questions: Why is there something updating without me updating the docker container? I am not using the official one, as I pre-download the textLive Environment. So the container is the same for about two weeks.
Why it's running updates on its own. This is not how docker is supposed to work. Container Images should be static and only be updated by building a new container.
Edit 4:
OK Pardon me, it's seems its the updated docker engine that creates trouble.
I just read the Release Notes of 26 Release (https://docs.docker.com/engine/release-notes/26.0/)
Always attempt to enable IPv6 on a container's loopback interface, and only include IPv6 in /etc/hosts if successful. moby/moby#47062
Note
By default, IPv6 will remain enabled on a container's loopback interface when the container is not connected to an IPv6-enabled network. For example, containers that are only connected to an IPv4-only network now have the ::1 address on their loopback interface.
To disable IPv6 in a container, use option --sysctl net.ipv6.conf.all.disable_ipv6=1 in the create or run command, or the equivalent sysctls option in the service configuration section of a Compose file.
If IPv6 is not available in a container because it has been explicitly disabled for the container, or the host's networking stack does not have IPv6 enabled (or for any other reason) the container's /etc/hosts file will not include IPv6 entries.
from overleaf.
Downgrading docker to 5.25
or 5.23
didn't work for me. Any way to quickfix for now?
from overleaf.
The issue referenced here seems to be similar:
#1146
The workaround mentioned there helped me to get at least to the login page and the project overview:
docker exec -it <overleaf_container_name> /bin/bash
sed -i 's/127.0.0.1/localhost/g' /etc/nginx/sites-enabled/sharelatex.conf
/etc/init.d/nginx reload
However, loading a project does not work.
from overleaf.
Yep, I can confirm that. The same workaround is described here: #1168 and works also greatly on my system.
from overleaf.
This can be fixed through #1146 (comment)
from overleaf.
This should be fixed in the latest release, 5.0.1, would you mind giving it a try?
Check the release notes, as there are several breaking changes: https://github.com/overleaf/overleaf/wiki/Release-Notes-5.x.x
from overleaf.
This should be fixed in the latest release, 5.0.1, would you mind giving it a try?
Check the release notes, as there are several breaking changes: https://github.com/overleaf/overleaf/wiki/Release-Notes-5.x.x
Can also confirm. 5.0.1 fixed the issue for me.
FYI, I'm using a regular compose.yaml, not the Overleaf Toolkit.
from overleaf.
Changes were made inside the container, so it won't matter how your instance is deployed.
from overleaf.
I can confirm, that the solution by @ykorzikowski works. Thank you very much for the hint. I was then able to upgrade docker to the newest version. I have not yet tested 5.0.1, but it seems to be a bad idea, according to the documentation, to do it now. Should I close this issue?
from overleaf.
Thanks for confirming. 5.0.2 has been released (https://github.com/overleaf/overleaf/wiki/Release-Notes-5.x.x) so I'll close this issue.
from overleaf.
Related Issues (20)
- Unable to start after upgrading from 4.2.3 to 5.0.1 HOT 4
- Texlive not picked up even after installing it in shell HOT 2
- MongoDB return ReadConcernMajorityNotAvailableYet
- No Mail sent when creating user with "node create-user"
- New user activation link is wrong (double // in the activation url) HOT 1
- Does not recompile if code has errors HOT 1
- pull sharelatex\sharelatex:lastest not working HOT 4
- Confused HOT 1
- Rebranding from ShareLaTeX to Overleaf HOT 4
- MongoDB not saved user/password HOT 1
- Upgrade to 5.0.3 CE - Installing scheme-full fails due to outdated texlive version (2023 instead of 2024) HOT 2
- history-v1 sent 404 to project-history HOT 2
- Contradictory information on the recovery of the doc version HOT 1
- How to reduce compile time when using overleaf CE 5.0.3 HOT 6
- How to Recover Files from a Local Deployment of Overleaf HOT 2
- Problems with config/variables.env when upgrading to 5.0.3CE HOT 2
- error "/etc/my_init.d/500_check_db_access.sh failed with status 1" HOT 3
- Overleaf Docker not starting but worked before
- Alternatives to MongoDB 5.0?
- Recreating Sharelatex after Changing Settings HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from overleaf.