Cannot start container, stuck with worker processes #1187
Replies: 2 comments
-
That's the expected output for an instance that has just been started and has not received any request yet, so the problem is somewhere before the container is even reached. You said you suddenly saw a blank screen. Have you checked the browser console? There should be more info there. If you have a reverse proxy in front of your instance, have you checked its logs? Maybe it's having trouble forwarding traffic to it. |
Beta Was this translation helpful? Give feedback.
-
Hello, thanks for your response. Oh I see now. I should've checked accessing it locally. It seems to be the Authelia authorization I put on the reverse proxy. If I switch it to just basic auth, it works now. Thank you! |
Beta Was this translation helpful? Give feedback.
-
shlink-web-client version
4.1.2
How do you use shlink-web-client
Docker image
Current behavior
I actually had it running then deleted a short URL and suddenly the screen went blank. Restarted the web client and this is all I get in the logs. My actual shlink instance and DB are running fine.
I even tried removing the container, deleting the image from Docker, and spinning up the
docker-compose.yml
file again, but this is all I get.My
docker-compose.yml
file:My
servers.json
file:Any help would be appreciated. Thank you!
Expected behavior
The Shlink web client should run.
Minimum steps to reproduce
Beta Was this translation helpful? Give feedback.
All reactions