[GH-ISSUE #2598] Admin Login Bad Gateway Error after routine restart (Route53 connection?) #1810

Closed
opened 2026-02-26 07:32:33 +03:00 by kerem · 10 comments
Owner

Originally created by @DerLeole on GitHub (Feb 8, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2598

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug
After a routine restart of the docker container for npm I found myself unable to login to the admin page.
The only report I get is a red "Bad Gateway" text under the login field.
The proxying works fine in the background as I would expect it, I just can't login.

Nginx Proxy Manager Version
v2.9.19

To Reproduce
I honestly don't quite know how to reproduce this, as it just happened after a routine restart without any changes.

Expected behavior
Ability to login without problems.

Screenshots
image

Operating System
Debian 11

Additional context
The only error I can find in my logs.

 [2/8/2023] [1:20:40 PM] [Global   ] › ✖  error     Command failed: pip install certbot-dns-route53==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') 
 

 WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/
 

 WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/
 

 WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/
 

 WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/
 

 WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/
 

 ERROR: Could not find a version that satisfies the requirement certbot-dns-route53==1.31.0 (from versions: none)
 

 ERROR: No matching distribution found for certbot-dns-route53==1.31.0
 

 WARNING: There was an error checking the latest version of pip.
Originally created by @DerLeole on GitHub (Feb 8, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2598 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** After a routine restart of the docker container for npm I found myself unable to login to the admin page. The only report I get is a red "Bad Gateway" text under the login field. The proxying works fine in the background as I would expect it, I just can't login. **Nginx Proxy Manager Version** v2.9.19 **To Reproduce** I honestly don't quite know how to reproduce this, as it just happened after a routine restart without any changes. **Expected behavior** Ability to login without problems. **Screenshots** ![image](https://user-images.githubusercontent.com/12782603/217541452-bff060ea-0759-42c4-86ba-f611ad99a27b.png) **Operating System** Debian 11 **Additional context** The only error I can find in my logs. ``` [2/8/2023] [1:20:40 PM] [Global ] › ✖ error Command failed: pip install certbot-dns-route53==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/ WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/ WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/ WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/ WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/certbot-dns-route53/ ERROR: Could not find a version that satisfies the requirement certbot-dns-route53==1.31.0 (from versions: none) ERROR: No matching distribution found for certbot-dns-route53==1.31.0 WARNING: There was an error checking the latest version of pip. ```
kerem 2026-02-26 07:32:33 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@DerLeole commented on GitHub (Feb 8, 2023):

I managed to fix the login error, by manually editing the database entries to no longer use DNS Challenges with Route 53.
But the error itself still should be addressed.

<!-- gh-comment-id:1423340864 --> @DerLeole commented on GitHub (Feb 8, 2023): I managed to fix the login error, by manually editing the database entries to no longer use DNS Challenges with Route 53. But the error itself still should be addressed.
Author
Owner

@whenthelight commented on GitHub (Feb 23, 2023):

same Error on latest PR from Docker-Hub , fixed it with exec in Container and update with: "pip install certbot-dns-route53"

<!-- gh-comment-id:1442443251 --> @whenthelight commented on GitHub (Feb 23, 2023): same Error on latest PR from Docker-Hub , fixed it with exec in Container and update with: "pip install certbot-dns-route53"
Author
Owner

@franzbischoff commented on GitHub (Feb 24, 2023):

cffi fails to compile the wheel.

this solves:

pip3 install https://www.piwheels.org/simple/cffi/cffi-1.15.1-cp37-cp37m-linux_armv7l.whl#sha256=bf9242179d15bac1bf6d9b03d83d058019b3f6bca8c08ad699de315e5fbfa6d3

<!-- gh-comment-id:1442652772 --> @franzbischoff commented on GitHub (Feb 24, 2023): cffi fails to compile the wheel. this solves: pip3 install https://www.piwheels.org/simple/cffi/cffi-1.15.1-cp37-cp37m-linux_armv7l.whl#sha256=bf9242179d15bac1bf6d9b03d83d058019b3f6bca8c08ad699de315e5fbfa6d3
Author
Owner

@franzbischoff commented on GitHub (Feb 24, 2023):

fixed image. Only Arm7l

https://hub.docker.com/r/franzbischoff/nginx-proxy-manager

<!-- gh-comment-id:1442667059 --> @franzbischoff commented on GitHub (Feb 24, 2023): fixed image. Only Arm7l https://hub.docker.com/r/franzbischoff/nginx-proxy-manager
Author
Owner

@baiyz0825 commented on GitHub (Feb 27, 2023):

same Error on latest PR from Docker-Hub , fixed it with exec in Container and update with: "pip install certbot-dns-route53"

thanks this s work for me

<!-- gh-comment-id:1446862463 --> @baiyz0825 commented on GitHub (Feb 27, 2023): > same Error on latest PR from Docker-Hub , fixed it with exec in Container and update with: "pip install certbot-dns-route53" thanks this s work for me
Author
Owner

@BartAgterbosch commented on GitHub (Apr 15, 2023):

Unfortunately none of the mentioned solutions work for me, this issue happened to me immediately after updating to the latest 2.9.19 version, and none of the above unfortunately seem to work, worst of all, all of the websites it's supposed to redirect have gone down (presumably because of nginx)
Edit: nvm, for some reason the new version either needed specifically a dns server mentioned, or it somehow got wiped when recreating the image, probably the first one.. Problem fixed now

<!-- gh-comment-id:1509923671 --> @BartAgterbosch commented on GitHub (Apr 15, 2023): Unfortunately none of the mentioned solutions work for me, this issue happened to me immediately after updating to the latest 2.9.19 version, and none of the above unfortunately seem to work, worst of all, all of the websites it's supposed to redirect have gone down (presumably because of nginx) Edit: nvm, for some reason the new version either needed specifically a dns server mentioned, or it somehow got wiped when recreating the image, probably the first one.. Problem fixed now
Author
Owner

@Ja50n-Kru commented on GitHub (May 6, 2023):

I am now seeing this after update to 2.10 - how can I fix it? When I try to login I get 'bad gateway'.

<!-- gh-comment-id:1537134653 --> @Ja50n-Kru commented on GitHub (May 6, 2023): I am now seeing this after update to 2.10 - how can I fix it? When I try to login I get 'bad gateway'.
Author
Owner

@conichonhaa commented on GitHub (Oct 3, 2023):

Hi, same problem with 2.10.4 update.
Tried to add config.json and json file path in docker-compose.yml as the documentation said, but same bad gateway result

<!-- gh-comment-id:1745467398 --> @conichonhaa commented on GitHub (Oct 3, 2023): Hi, same problem with 2.10.4 update. Tried to add config.json and json file path in docker-compose.yml as the documentation said, but same bad gateway result
Author
Owner

@github-actions[bot] commented on GitHub (Apr 18, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2062847493 --> @github-actions[bot] commented on GitHub (Apr 18, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Jun 13, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2968775262 --> @github-actions[bot] commented on GitHub (Jun 13, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1810
No description provided.