nginx-proxy-manager icon indicating copy to clipboard operation
nginx-proxy-manager copied to clipboard

Dashboard shows 0 proxy hosts for new admin user, while lists shows all as expected

Open AcidGreg opened this issue 3 years ago • 12 comments

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: #1679 exists but was closed probably due to inability to reproduce

Describe the bug After adding a new admin user account, and logging in with it, the proxy host count on the dashboard is 0, while there are indeed defined proxy hosts. Clicking the icon gets us to the correct list, however, with all hosts shown. Just the dashboard view count is wrong. This has happened on 2/2 deployments within the last week. It might be important to note the following to reproduce: In both cases, the new admin user was added and then immediately a password was set by the original admin user, then logout, login with the new one and the issue appears.

Nginx Proxy Manager Version v2.9.18

To Reproduce Steps to reproduce the behavior: When some proxy hosts are defined and you are logged in with the original admin account and no other users yet exist:

  1. Add a new admin account
  2. Set a password for the new admin account
  3. Log out
  4. Log in with the new admin account
  5. The problem should be visible: The Proxy hosts count is 0 when some other number is expected.
  6. Click on Proxy Hosts
  7. You should now see what you expect to see in this view - the correct list of defined proxy hosts.

Expected behavior The expected behavior would be to see the correct count of defined proxy hosts in the dashboard view and not 0.

Screenshots

image image

Here are the two defined admin users: Norbert is the original admin defined after installation. image

Operating System Docker image on Ubuntu (18.04 and 20.04) x86-64

Additional context Using latest Chrome browser. Did not feel the need to try with others.

AcidGreg avatar Apr 19 '22 15:04 AcidGreg

I see the same problem!

robonuka avatar Apr 27 '22 10:04 robonuka

Same issue here.

markpsullivan avatar Jul 06 '22 20:07 markpsullivan

Same issue here

dannykorpan avatar Jul 19 '23 13:07 dannykorpan

Yeah this is an age old problem with the UI caching the result of a different API result. I'm not working on this UI in favour of the react version on the v3 branch.

jc21 avatar Jul 20 '23 05:07 jc21

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

github-actions[bot] avatar Feb 18 '24 01:02 github-actions[bot]