Closed qcasey closed 3 years ago
Well that was easy enough, I fixed this by removing the 'localhost:8000'
from gunicorn.conf.py
I have the same issue, but can't fix it as easily because I am using the docker image - will this be fixed?
I'm using the Docker hub image as well. Give this a try if you want it back up ASAP:
sudo docker exec -it paperless-ng_webserver_1 /bin/bash
cd ..
apt update && apt install nano -y
nano gunicorn.conf.py
exit
@jonaswinkler is incredibly responsive, but it's 5AM in Germany right now.
I have the same issue, but can't fix it as easily because I am using the docker image - will this be fixed?
I just rolled back to jonaswinkler/paperless-ng:0.9.9 for now
Thanks for the tip, @qcasey! I do hope that this error was not caused by my other ticket: https://github.com/jonaswinkler/paperless-ng/issues/185
This is likely caused by #184 and the followup 5c3ae44021c284f93a74cc41857a2dd8fb5710c6. Apparently gunicorn's IPv6 bind ([::]
) falls back to IPv4 when IPv6 is not available (as is the case with docker). Having an explicit IPv4 after that might cause this behaviour.
Well that's just typical. The one time I trust the image to work it doesn't.
Sorry!
My bad! Sorry! Should have done some more testing. :(
The edit that caused this to fail was mine.
However, the gunicorn documentation explicitly states that binding to localhost
and [::1]
is a valid approach for listening on both IPv4 and IPv6 at the same time. Maybe a bug in gunicorn.
Thank you for the quick repair!
Hello! This evening I updated paperless-ng to 0.9.10 and can't get it to start. The logs below basically repeat forever...
I tried using the provided
docker-compose-postgres.yml
and.env
with the same result.Did a config change happen somewhere with gunicorn?
Thanks for all the releases lately, paperless-ng has been great :smiley: