starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #2041] Hosts of a deleted user break the host list #1475

New issue
Open
opened 2026-02-26 07:31:13 +03:00 by kerem · 18 comments
kerem commented 2026-02-26 07:31:13 +03:00
Owner
Copy link

Originally created by @v3ss0n on GitHub (May 5, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2041

Re-issued #1038 Because it is not fixed , and owner of that issue is not reopening .

This annoying bug breaks NPM rendering anyone unable to change , very bad for production environment.
Please consider looking into it.

Originally created by @v3ss0n on GitHub (May 5, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2041 Re-issued #1038 Because it is not fixed , and owner of that issue is not reopening . This annoying bug breaks NPM rendering anyone unable to change , very bad for production environment. Please consider looking into it.
kerem commented 2026-02-26 07:31:13 +03:00
Author
Owner
Copy link

@damianog commented on GitHub (May 28, 2022):

I can confirm this issue, after deleting an old admin user I get the error: Cannot read properties of null (reading 'avatar')

image

@v3ss0n have you got a solution to restore the Hosts list?

<!-- gh-comment-id:1140276883 --> @damianog commented on GitHub (May 28, 2022): I can confirm this issue, after deleting an old admin user I get the error: Cannot read properties of null (reading 'avatar') ![image](https://user-images.githubusercontent.com/2786682/170830172-3b312a5a-d356-4b33-a61a-1f6558a77722.png) @v3ss0n have you got a solution to restore the Hosts list?
kerem commented 2026-02-26 07:31:13 +03:00
Author
Owner
Copy link

@v3ss0n commented on GitHub (May 28, 2022):

Only way is to go in and fix using SQL.

<!-- gh-comment-id:1140288073 --> @v3ss0n commented on GitHub (May 28, 2022): Only way is to go in and fix using SQL.
kerem commented 2026-02-26 07:31:13 +03:00
Author
Owner
Copy link

@damianog commented on GitHub (May 28, 2022):

OK I managed to enable the user by:
update user set is_deleted = 0 where is_deleted = 1;
in mysql db

So the issue depend on the avatar icon on the host list?
image

The one with red spot is the undeleted user now only disabled.

@jc21 I whant to delete a secondary administrator user, but there are some proxy-host owned by this one.
How could I change the owner than?

<!-- gh-comment-id:1140297693 --> @damianog commented on GitHub (May 28, 2022): OK I managed to enable the user by: update user set is_deleted = 0 where is_deleted = 1; in mysql db So the issue depend on the avatar icon on the host list? ![image](https://user-images.githubusercontent.com/2786682/170835102-338fc221-4bd3-476b-9bfd-fe9e0f4ce96b.png) The one with red spot is the undeleted user now only disabled. @jc21 I whant to delete a secondary administrator user, but there are some proxy-host owned by this one. How could I change the owner than?
kerem commented 2026-02-26 07:31:13 +03:00
Author
Owner
Copy link

@danielclough commented on GitHub (Jun 15, 2022):

I was able to reset the user by:

  1. entering database
  2. using db
  3. UPDATE user SET is_deleted=1;
  4. wait for restart (or manually restart)
  5. UPDATE user SET is_deleted=0;
  6. wait for restart (or manually restart)
  7. log in

Upon logging in the deleted user is back along with their hosts.

There is probably a better way.

<!-- gh-comment-id:1156023056 --> @danielclough commented on GitHub (Jun 15, 2022): I was able to reset the user by: 1. entering database 2. using db 3. `UPDATE user SET is_deleted=1;` 4. wait for restart (or manually restart) 5. `UPDATE user SET is_deleted=0;` 6. wait for restart (or manually restart) 7. log in Upon logging in the deleted user is back along with their hosts. There is probably a better way.
kerem commented 2026-02-26 07:31:13 +03:00
Author
Owner
Copy link

@v3ss0n commented on GitHub (Jun 15, 2022):

Thats shouldn't be the way , its a critical bug. We need a fix.

<!-- gh-comment-id:1156973207 --> @v3ss0n commented on GitHub (Jun 15, 2022): Thats shouldn't be the way , its a critical bug. We need a fix.
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@wbloos commented on GitHub (Jun 24, 2022):

I was able to reset the user by:

1. entering database

2. using db

3. `UPDATE user SET is_deleted=1;`

4. wait for restart (or manually restart)

5. `UPDATE user SET is_deleted=0;`

6. wait for restart (or manually restart)

7. log in

Upon logging in the deleted user is back along with their hosts.

There is probably a better way.

That is dangerous, because it will restore the admin user with the default username and password!! (admin@example.com/changeme)

<!-- gh-comment-id:1165343352 --> @wbloos commented on GitHub (Jun 24, 2022): > I was able to reset the user by: > > 1. entering database > > 2. using db > > 3. `UPDATE user SET is_deleted=1;` > > 4. wait for restart (or manually restart) > > 5. `UPDATE user SET is_deleted=0;` > > 6. wait for restart (or manually restart) > > 7. log in > > > Upon logging in the deleted user is back along with their hosts. > > There is probably a better way. That is dangerous, because it will restore the admin user with the default username and password!! (admin@example.com/changeme)
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@etfz commented on GitHub (Oct 14, 2022):

Just encountered this very unfortunate issue. Was able to recover by assigning the affected entries to a different owner.

This is also done directly in the database. In my case I was using SQLite.

  1. First open a container shell. (use docker ps to find your container ID, if necessary)
docker exec -it <container-name-or-id> bash
  1. Install SQLite. (while inside the container)
apt update
apt install sqlite3
  1. Enter the database
sqlite3 /data/database.sqlite
  1. Find the ID of the user to which you want to reassign the affected entries. Optionally, also the ID of the removed user.
SELECT id, name FROM user;

1|etfz
2|Ghost
  1. Reassign the entries using the user IDs from the output of the previous query. You can either reassign everything to you, (first line in the example below) or only the entries owned by the removed user. (second line, useful if you still have other active users)
UPDATE proxy_host  SET owner_user_id = 1;
UPDATE certificate SET owner_user_id = 1 where owner_user_id = 2;

List all tables using .tables to find any other tables you may need to edit.

Taken from here:
https://forums.unraid.net/topic/76460-support-djoss-nginx-proxy-manager/page/52/#comment-969943

Steps 1 through 3 can probably be done outside of the container, too, since the database should be bind mounted outside of the container.

<!-- gh-comment-id:1278596026 --> @etfz commented on GitHub (Oct 14, 2022): Just encountered this very unfortunate issue. Was able to recover by assigning the affected entries to a different owner. This is also done directly in the database. In my case I was using SQLite. 1. First open a container shell. (use `docker ps` to find your container ID, if necessary) ``` docker exec -it <container-name-or-id> bash ``` 2. Install SQLite. (while inside the container) ``` apt update apt install sqlite3 ``` 3. Enter the database ``` sqlite3 /data/database.sqlite ``` 4. Find the ID of the user to which you want to reassign the affected entries. Optionally, also the ID of the removed user. ```sql SELECT id, name FROM user; ``` ``` 1|etfz 2|Ghost ``` 5. Reassign the entries using the user IDs from the output of the previous query. You can either reassign everything to you, (first line in the example below) or only the entries owned by the removed user. (second line, useful if you still have other active users) ```sql UPDATE proxy_host SET owner_user_id = 1; UPDATE certificate SET owner_user_id = 1 where owner_user_id = 2; ``` List all tables using `.tables` to find any other tables you may need to edit. Taken from here: https://forums.unraid.net/topic/76460-support-djoss-nginx-proxy-manager/page/52/#comment-969943 Steps 1 through 3 can probably be done outside of the container, too, since the database should be bind mounted outside of the container.
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@franciscopaniskaseker commented on GitHub (Nov 25, 2022):

Still happening. i followed @etfz steps and fixed the problem, but of course the bug can happen again.

<!-- gh-comment-id:1327469708 --> @franciscopaniskaseker commented on GitHub (Nov 25, 2022): Still happening. i followed @etfz steps and fixed the problem, but of course the bug can happen again.
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@fiservedpi commented on GitHub (Apr 24, 2023):

Experiencing the same on latest version (v2.10.2 © 2022 ) applied the above fix and all is well. I do not know what started all this, I was updating some containers beforehand and then all of a sudden error!
image

<!-- gh-comment-id:1520682489 --> @fiservedpi commented on GitHub (Apr 24, 2023): Experiencing the same on latest version (v2.10.2 © 2022 ) applied the above fix and all is well. I do not know what started all this, I was updating some containers beforehand and then all of a sudden error! ![image](https://user-images.githubusercontent.com/42981853/234091577-b6266c32-7363-4e87-ba52-26d3ac8ec694.png)
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@rubickecho commented on GitHub (Jun 29, 2023):

Experiencing the same on latest version (v2.10.2 © 2022 ) applied the above fix and all is well. I do not know what started all this, I was updating some containers beforehand and then all of a sudden error! image

yes, I had a problem today too, looking forward to a quick fix

<!-- gh-comment-id:1612372643 --> @rubickecho commented on GitHub (Jun 29, 2023): > Experiencing the same on latest version (v2.10.2 © 2022 ) applied the above fix and all is well. I do not know what started all this, I was updating some containers beforehand and then all of a sudden error! ![image](https://user-images.githubusercontent.com/42981853/234091577-b6266c32-7363-4e87-ba52-26d3ac8ec694.png) yes, I had a problem today too, looking forward to a quick fix
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@devuar commented on GitHub (Jul 25, 2023):

Any update on this?

<!-- gh-comment-id:1650283559 --> @devuar commented on GitHub (Jul 25, 2023): Any update on this?
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@v3ss0n commented on GitHub (Jul 26, 2023):

Consider moving to traefik . This is such a deal breaker bug that dev choose to ignore ( along with severe CVEs).

<!-- gh-comment-id:1650906045 --> @v3ss0n commented on GitHub (Jul 26, 2023): Consider moving to traefik . This is such a deal breaker bug that dev choose to ignore ( along with severe CVEs).
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@devuar commented on GitHub (Jul 31, 2023):

I was able to reset the user by:

  1. entering database
  2. using db
  3. UPDATE user SET is_deleted=1;
  4. wait for restart (or manually restart)
  5. UPDATE user SET is_deleted=0;
  6. wait for restart (or manually restart)
  7. log in

Upon logging in the deleted user is back along with their hosts.

There is probably a better way.

This worked for me!

<!-- gh-comment-id:1659014094 --> @devuar commented on GitHub (Jul 31, 2023): > I was able to reset the user by: > > 1. entering database > 2. using db > 3. `UPDATE user SET is_deleted=1;` > 4. wait for restart (or manually restart) > 5. `UPDATE user SET is_deleted=0;` > 6. wait for restart (or manually restart) > 7. log in > > Upon logging in the deleted user is back along with their hosts. > > There is probably a better way. This worked for me!
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@alexsalex commented on GitHub (Aug 30, 2023):

Same issue here...

<!-- gh-comment-id:1699572015 --> @alexsalex commented on GitHub (Aug 30, 2023): Same issue here...
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@Kevinsky86 commented on GitHub (Dec 22, 2023):

Consider moving to traefik . This is such a deal breaker bug that dev choose to ignore ( along with severe CVEs).

Can you elaborate on the CVE's?

<!-- gh-comment-id:1867605206 --> @Kevinsky86 commented on GitHub (Dec 22, 2023): > Consider moving to traefik . This is such a deal breaker bug that dev choose to ignore ( along with severe CVEs). Can you elaborate on the CVE's?
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Aug 9, 2024):

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

<!-- gh-comment-id:2277006472 --> @github-actions[bot] commented on GitHub (Aug 9, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

@kerstenremco commented on GitHub (Nov 15, 2024):

Added PR #4166 for this issue

<!-- gh-comment-id:2479161723 --> @kerstenremco commented on GitHub (Nov 15, 2024): Added PR #4166 for this issue
kerem commented 2026-02-26 07:31:14 +03:00
Author
Owner
Copy link

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

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

<!-- gh-comment-id:2974914091 --> @github-actions[bot] commented on GitHub (Jun 16, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1475
No description provided.