[GH-ISSUE #2304] Unable to login to Admin UI #1633

Closed
opened 2026-02-26 07:31:51 +03:00 by kerem · 5 comments
Owner

Originally created by @skirven4 on GitHub (Oct 4, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2304

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

On version 2.9.18, I am unable to login to the NPM UI. Yes, I can downgrade to 2.9.14 and get it to work, sort of.

Nginx Proxy Manager Version

2.9.18

To Reproduce
Steps to reproduce the behavior:

  1. Go to the login page at http://:81
  2. Enter your Username and Password
  3. The login just comes back with either "Bad Gateway" in red text, or simply will not login.
  4. Check the logs in your file system path ./data/logs/fallback_error.log

2.168.0.196, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "nettools.local:81", referrer: "http://nettools.local:81/login"

Expected behavior

User should be able to login to the system

Screenshots

Operating System

Raspian OS

Additional context

I find this token api error strange. I'm also getting a "Bad Gateway" nginx message on url :81/api, as I tried that after finding an older issue that seemed similar. I also rebuilt my docker-compse.yml. Additionally, the port 3000 is not open in my installation, either at the host, or inside the container.

version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:2.9.18'
    restart: unless-stopped
    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      - '81:81' # Admin Web Port
      - '8089:8089'
      - '57000:57000'
      # Add any other Stream port you want to expose
      # - '21:21' # FTP

    # Uncomment the next line if you uncomment anything in the section
    # environment:
      # Uncomment this if you want to change the location of 
      # the SQLite DB file within the container
      # DB_SQLITE_FILE: "/data/database.sqlite"

      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'

    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
Originally created by @skirven4 on GitHub (Oct 4, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2304 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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** <!-- A clear and concise description of what the bug is. --> On version 2.9.18, I am unable to login to the NPM UI. Yes, I can downgrade to 2.9.14 and get it to work, sort of. **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> 2.9.18 **To Reproduce** Steps to reproduce the behavior: 1. Go to the login page at http://<server>:81 2. Enter your Username and Password 3. The login just comes back with either "Bad Gateway" in red text, or simply will not login. 4. Check the logs in your file system path ./data/logs/fallback_error.log `2.168.0.196, server: nginxproxymanager, request: "POST /api/tokens HTTP/1.1", upstream: "http://127.0.0.1:3000/tokens", host: "nettools.local:81", referrer: "http://nettools.local:81/login" ` **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> User should be able to login to the system **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Raspian OS **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> I find this token api error strange. I'm also getting a "Bad Gateway" nginx message on url <host>:81/api, as I tried that after finding an older issue that seemed similar. I also rebuilt my docker-compse.yml. Additionally, the port 3000 is not open in my installation, either at the host, or inside the container. ``` version: "3" services: app: image: 'jc21/nginx-proxy-manager:2.9.18' restart: unless-stopped ports: # These ports are in format <host-port>:<container-port> - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port - '81:81' # Admin Web Port - '8089:8089' - '57000:57000' # Add any other Stream port you want to expose # - '21:21' # FTP # Uncomment the next line if you uncomment anything in the section # environment: # Uncomment this if you want to change the location of # the SQLite DB file within the container # DB_SQLITE_FILE: "/data/database.sqlite" # Uncomment this if IPv6 is not enabled on your host # DISABLE_IPV6: 'true' volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt ```
kerem 2026-02-26 07:31:51 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@pennyloafers commented on GitHub (Feb 10, 2023):

having this same issue, on a fresh install it works fine, but i found that any change to the docker network of nginx causes this issue and it is not resolved by undoing network changes.

<!-- gh-comment-id:1425139110 --> @pennyloafers commented on GitHub (Feb 10, 2023): having this same issue, on a fresh install it works fine, but i found that any change to the docker network of nginx causes this issue and it is not resolved by undoing network changes.
Author
Owner

@pennyloafers commented on GitHub (Feb 11, 2023):

So looking at the docker log in the container, I found an issue with certbot.

[2/11/2023] [3:43:13 AM] [Global   ] › ✖  error     Command failed: pip install certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') cloudflare

going into container and resolving the install errors by getting a few dependencies to get a successful install, restarting the container i'm now able to login again.

<!-- gh-comment-id:1426597255 --> @pennyloafers commented on GitHub (Feb 11, 2023): So looking at the docker log in the container, I found an issue with certbot. ``` [2/11/2023] [3:43:13 AM] [Global ] › ✖ error Command failed: pip install certbot-dns-cloudflare==$(certbot --version | grep -Eo '[0-9](\.[0-9]+)+') cloudflare ``` going into container and resolving the install errors by getting a few dependencies to get a successful install, restarting the container i'm **now** able to login again.
Author
Owner

@johncaipa commented on GitHub (Apr 12, 2023):

I have solved it by entering the mysql container shell and executing the following:
sudo chown -R mysql:mysql /usr/local/mysql/
sudo chmod -R 755 /usr/local/mysql/

<!-- gh-comment-id:1504495344 --> @johncaipa commented on GitHub (Apr 12, 2023): I have solved it by entering the mysql container shell and executing the following: sudo chown -R mysql:mysql /usr/local/mysql/ sudo chmod -R 755 /usr/local/mysql/
Author
Owner

@github-actions[bot] commented on GitHub (Feb 8, 2024):

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

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

@github-actions[bot] commented on GitHub (Mar 24, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2746694295 --> @github-actions[bot] commented on GitHub (Mar 24, 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#1633
No description provided.