mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #5298] 500 error when trying to disable 2FA #3163
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#3163
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @celebrion on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5298
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
User unable to disable 2FA for admin interface.
Nginx Proxy Manager Version
v2.13.7
To Reproduce
After logging in to the admin interface with username, password and 2FA I went to the user menu on the top right, went into"Two-Factor Auth" and tried to disable 2FA. This resultet in a 500 error in the browser console akin to this:
Expected behavior
Being able to disable 2FA at will.
Operating System
Docker container on Debian 12.
@celebrion commented on GitHub (Feb 11, 2026):
Replaced my FQDN in the error message with fqdn.to.npm.tld for privacy.
@MikeTh01 commented on GitHub (Feb 12, 2026):
Same Problem.
I even have the Problem i Can't Login with 2FA. It keeps saying it is Invalid. Tried 20 times. Can only Login with Backup Code at the moment.
And i Can't make new Backup Codes and Can't Disable 2FA with the same error from This here.
@7heMech commented on GitHub (Feb 14, 2026):
When the PR gets merged this will be fixed, you can temporarily use this image
nginxproxymanager/nginx-proxy-manager-dev:pr-5303if you need it ASAP.