[GH-ISSUE #3899] Unable to log in after upgrading from 2.11.2 to 2.11.3 #2558

Open
opened 2026-02-26 07:36:00 +03:00 by kerem · 9 comments
Owner

Originally created by @wxyShine on GitHub (Jul 26, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3899

2.11.2 has been working fine, but after updating to 2.11.3, it's not working.

image

image

Originally created by @wxyShine on GitHub (Jul 26, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3899 2.11.2 has been working fine, but after updating to 2.11.3, it's not working. ![image](https://github.com/user-attachments/assets/f58a8774-e0b8-4c0c-870d-8b5ebfb37b3b) ![image](https://github.com/user-attachments/assets/4c2e50bc-a61f-4731-ba88-d79539862907)
Author
Owner

@wxyShine commented on GitHub (Jul 26, 2024):

#1769 It looks the same as this one.

<!-- gh-comment-id:2252238736 --> @wxyShine commented on GitHub (Jul 26, 2024): #1769 It looks the same as this one.
Author
Owner

@Mariyo commented on GitHub (Aug 2, 2024):

Same for me, unfortunately downgrade even to 2.10 does not help. Snapshot from docker logs:

image

<!-- gh-comment-id:2265421191 --> @Mariyo commented on GitHub (Aug 2, 2024): Same for me, unfortunately downgrade even to 2.10 does not help. Snapshot from docker logs: ![image](https://github.com/user-attachments/assets/65f90660-623d-4d58-8e5d-2b025997116e)
Author
Owner

@wxyShine commented on GitHub (Aug 3, 2024):

Same for me, unfortunately downgrade even to 2.10 does not help. Snapshot from docker logs:

image

I chose to delete the existing one and reinstalled it

<!-- gh-comment-id:2266689485 --> @wxyShine commented on GitHub (Aug 3, 2024): > Same for me, unfortunately downgrade even to 2.10 does not help. Snapshot from docker logs: > > ![image](https://private-user-images.githubusercontent.com/1678254/354612213-65f90660-623d-4d58-8e5d-2b025997116e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI2ODY2NDksIm5iZiI6MTcyMjY4NjM0OSwicGF0aCI6Ii8xNjc4MjU0LzM1NDYxMjIxMy02NWY5MDY2MC02MjNkLTRkNTgtOGU1ZC0yYjAyNTk5NzExNmUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgwMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MDNUMTE1OTA5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZjI0NmQzZGExMzVlNTY5ZmI0NjZhOWRjM2ZkZTRhMDIxZTZiYWU4ZDRkNTRjYmVjNmY2NTJmZTZmNGEyZDc1NCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.qenDDmHbP6nZg9D5n8O9VQxpFyDzaCe0J0_vDlCfFQs) I chose to delete the existing one and reinstalled it
Author
Owner

@CosinusJay commented on GitHub (Aug 10, 2024):

I have the same problem right now, reinstalling did not fix it :(
Are there any external directories and or configs outside of the docker compose directory that i need to remove?

<!-- gh-comment-id:2282188356 --> @CosinusJay commented on GitHub (Aug 10, 2024): I have the same problem right now, reinstalling did not fix it :( Are there any external directories and or configs outside of the docker compose directory that i need to remove?
Author
Owner

@CosinusJay commented on GitHub (Aug 10, 2024):

Nevermind, i deleted the folders but not the containers 🤦🏻‍♂️

<!-- gh-comment-id:2282192676 --> @CosinusJay commented on GitHub (Aug 10, 2024): Nevermind, i deleted the folders but not the containers 🤦🏻‍♂️
Author
Owner

@Mariyo commented on GitHub (Aug 22, 2024):

I had to reinstall it too and decided to:

  • switch from :latest tag to exact ones image: 'jc21/nginx-proxy-manager:2.11.3'
  • stay on sqlite database
  • implement backup process of data and letsencrypt folders

Lets hope it will help me to manage next upgrades more carefully so I can revert easily in similar case 🤞

<!-- gh-comment-id:2304231558 --> @Mariyo commented on GitHub (Aug 22, 2024): I had to reinstall it too and decided to: - switch from `:latest` tag to exact ones `image: 'jc21/nginx-proxy-manager:2.11.3'` - stay on `sqlite` database - implement backup process of `data` and `letsencrypt` folders Lets hope it will help me to manage next upgrades more carefully so I can revert easily in similar case :crossed_fingers:
Author
Owner

@wxyShine commented on GitHub (Dec 2, 2024):

v2.12.1 also has this problem after a short time of normal use, Request a solution

<!-- gh-comment-id:2510408971 --> @wxyShine commented on GitHub (Dec 2, 2024): v2.12.1 also has this problem after a short time of normal use, Request a solution
Author
Owner

@wxyShine commented on GitHub (Dec 2, 2024):

compose.yml

services:
  app:
    container_name: npm-app
    image: jc21/nginx-proxy-manager:latest
    restart: unless-stopped
    ports:
      - 80:80
      - 81:81
      - 443:443
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
networks: {}
<!-- gh-comment-id:2510410153 --> @wxyShine commented on GitHub (Dec 2, 2024): `compose.yml` ```yml services: app: container_name: npm-app image: jc21/nginx-proxy-manager:latest restart: unless-stopped ports: - 80:80 - 81:81 - 443:443 volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt networks: {} ```
Author
Owner

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

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

<!-- gh-comment-id:3017533011 --> @github-actions[bot] commented on GitHub (Jun 30, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
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#2558
No description provided.