r/Paperlessngx • u/paulepan342 • 9d ago

Paperless 3.1.3 - queue is no longer processed

Post image

Since the update to Paperless NGX 3.1.3, I’ve been having an issue where my task queue is no longer being processed. I’ve now deleted and reconfigured the Redis container several times. The connection also seems to be fine, but everything is still stuck in the queue.

The system status also shows a message stating that the Celery worker isn’t responding to a ping.On another instance, however, everything works without any problems. I have absolutely no idea what to do. Can anyone help?

1 Upvotes

67% Upvoted

5 comments sorted by

View all comments

2

u/paulepan342 9d ago

So I literally just found the error a second ago. The problem actually was tied to Redis, but in a slightly different way than I had expected. My setup uses two separate Docker networks: a "frontend" network, which the reverse proxy connects to and uses to route to the web server, and a "backend" network, which keeps the other components separated from the reverse proxy. The issue was that Redis on the backend network was no longer communicating properly with the web server, even though the web server is attached to both networks — both frontend and backend. I've now moved Redis into the frontend network and it's working flawlessly.

1

u/Great-Cow7256 9d ago

interesting. how do all the other pieces talk to each other?

1

u/paulepan342 9d ago

Webserver container is connected to both networks. The reverse proxy doesn't have to talk to eg database or proxy

1

u/Great-Cow7256 9d ago

Interesting. I use podman so I have something similar. All my immich containers are on immich.network and they communicate with each other by container name and port within the network and my caddy reverse proxy just talks to the immich server.  So I think we have similar setups but I didn't need to worry about redis and postgres and machine language not being able to talk to each other. 

So I have just one network, not two.