Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

503 Service Temporarily Unavailable

See original GitHub issue

I’m trying to run wallabag with nginx-proxy. I can run Wallabag directly:

$ docker run --detach  -v /opt/wallabag/data:/var/www/wallabag/data -v /opt/wallabag/images:/var/www/wallabag/web/assets/images -p 80:80 wallabag/wallabag

and it works (and redirects to the login page):

$ curl -I http://localhost
HTTP/1.1 302 Found
Server: nginx
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Powered-By: PHP/7.1.14
Set-Cookie: PHPSESSID=f3977b6703abd265a234b46a8ef7ab90; path=/; HttpOnly
Cache-Control: no-cache, private
Date: Fri, 02 Mar 2018 07:49:58 GMT
Location: http://localhost/login

But then I try running it with nginx-proxy

docker run -d     --name nginx-proxy     -p 80:80     -v /var/run/docker.sock:/tmp/docker.sock:ro jwilder/nginx-proxy

docker run -d --name wallabag -v /opt/wallabag/data:/var/www/wallabag/data -v /opt/wallabag/images:/var/www/wallabag/web/assets/images -e VIRTUAL_HOST=wallabag wallabag/wallabag

and I get this error message.

curl -i http://wallabag.localhost
HTTP/1.1 503 Service Temporarily Unavailable
Server: nginx/1.13.8
Date: Fri, 02 Mar 2018 07:56:38 GMT
Content-Type: text/html
Content-Length: 213
Connection: keep-alive

<html>
<head><title>503 Service Temporarily Unavailable</title></head>
<body bgcolor="white">
<center><h1>503 Service Temporarily Unavailable</h1></center>
<hr><center>nginx/1.13.8</center>
</body>
</html>

I’m sure it’s my fault, but I’m not sure where. Any ideas where I could be messing this up? Thanks!

Issue Analytics

State:
Created 6 years ago
Comments:5

Top GitHub Comments

2reactions

ghostcommented, Mar 6, 2018

@sickill Good idea. It works well; the service was still starting up when I tried to connect to it. Running without -d allowed me to see when it was ready. Thanks!

0reactions

sickillcommented, Mar 5, 2018

No idea what’s happening here. But I would suggested dropping -d from both docker run commands and start them in foreground in 2 separate terminal tabs/windows. This way you can easily see all output/errors from the processes in these containers.