Bitwarden is working fine other than I cant access the Admin portal. I attempt to send myself a login email, which used to work fine and now I get a error 500 after I put in my admin email address. Interestingly, if I put any other email address in I don’t get the error 500, but instead it gives me the normal “If a valid admin user with this email address exists, we’ve sent you an email with a secure link to log in.”
Any thoughts?
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1ddba1862d32 bitwarden/nginx:1.34.0 “/entrypoint.sh” 3 minutes ago Up 2 minutes (healthy) 80/tcp, 0.0.0.0:80->8080/tcp, 0.0.0.0:443->8443/tcp bitwarden-nginx
ecd6d2f27bae bitwarden/admin:1.34.0 “/entrypoint.sh” 3 minutes ago Up 2 minutes (healthy) 5000/tcp bitwarden-admin
89e8b55712a1 bitwarden/notifications:1.34.0 “/entrypoint.sh” 3 minutes ago Up 2 minutes (healthy) 5000/tcp bitwarden-notifications
3e007d80b056 bitwarden/attachments:1.34.0 “/entrypoint.sh” 3 minutes ago Up 3 minutes (healthy) bitwarden-attachments
3ce220de9811 bitwarden/api:1.34.0 “/entrypoint.sh” 3 minutes ago Up 3 minutes (healthy) 5000/tcp bitwarden-api
1bbe50e9d0a4 bitwarden/identity:1.34.0 “/entrypoint.sh” 3 minutes ago Up 2 minutes (healthy) 5000/tcp bitwarden-identity
6018e77f6365 bitwarden/web:2.14.0 “/entrypoint.sh” 3 minutes ago Up 3 minutes (healthy) bitwarden-web
f3cd796595e8 bitwarden/events:1.34.0 “/entrypoint.sh” 3 minutes ago Up 2 minutes (healthy) 5000/tcp bitwarden-events
abc989404c15 bitwarden/icons:1.34.0 “/entrypoint.sh” 3 minutes ago Up 3 minutes (healthy) 5000/tcp bitwarden-icons
7bbfe3f887d4 bitwarden/mssql:1.34.0 “/entrypoint.sh” 3 minutes ago Up 3 minutes (healthy) bitwarden-mssql
2020/06/16 10:54:28 [error] 40#40: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.20.80.80, server: bitwarden.ourdomain.org, request: “GET /admin HTTP/2.0”, upstream: “http://172.19.0.7:5000/admin”, host: “bitwarden.ourdomain.org”
2020/06/16 10:54:29 [error] 40#40: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.20.80.80, server: bitwarden.ourdomain.org, request: “GET /admin HTTP/2.0”, upstream: “http://172.19.0.7:5000/admin”, host: “bitwarden.ourdomain.org”
2020/06/16 10:54:31 [error] 40#40: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.20.80.80, server: bitwarden.ourdomain.org, request: “GET /admin HTTP/2.0”, upstream: “http://172.19.0.7:5000/admin”, host: “bitwarden.ourdomain.org”
2020/06/16 10:54:34 [warn] 40#40: *1 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/1/00/0000000001 while reading upstream, client: 172.20.80.80, server: bitwarden.ourdomain.org, request: “GET /app/vendor.c2b075c9534ce6d080ea.js HTTP/2.0”, upstream: “http://172.18.0.3:5000/app/vendor.c2b075c9534ce6d080ea.js”, host: “bitwarden.ourdomain.org”, referrer: “https://bitwarden.ourdomain.org/”
2020/06/16 10:56:15 [error] 40#40: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.20.80.80, server: bitwarden.ourdomain.org, request: “GET /admin HTTP/2.0”, upstream: “http://172.22.0.7:5000/admin”, host: “bitwarden.ourdomain.org”
2020/06/16 10:56:19 [error] 40#40: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.20.80.80, server: bitwarden.ourdomain.org, request: “GET /admin HTTP/2.0”, upstream: “http://172.22.0.7:5000/admin”, host: “bitwarden.ourdomain.org”