[GH-ISSUE #634] Update issue - Help! #536

Closed
opened 2026-02-26 06:33:18 +03:00 by kerem · 5 comments
Owner

Originally created by @crazybadger on GitHub (Oct 6, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/634

I've been running this for a few months and it works beautifully, so thanks to begin!

I'm running this in a ubuntu 18.4.5 VM on FreeNAS and have about 15 subdomains for various services I'm running configured with Proxy Hosts and SSL certificates I noticed that the certificates that are due for renewal on the 18 October hadn't, so manually updated one, which worked fine. When I came to look on the website and then here, I noticed I was a little behind (I was running 2.2.3) so through I'd update.

I couldn't see any specific instructions so pulled the latest images and then stopped and started the containers using:

docker pull jc21/nginx-proxy-manager
docker pull jc21/mariadb-aria
docker-compose down
docker-compose up -d

It started back up and I can access the WUI and see I now have 2.5.0, but when I click on a few of the menus nothing happens, specifically the Dashboard and SSL Certificate menus.

It's still working, and even appears to have updated the certificates that were due, but I can't see the menu to check.

Any ideas what I've done wrong and how to fix?

Thanks in advance

Originally created by @crazybadger on GitHub (Oct 6, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/634 I've been running this for a few months and it works beautifully, so thanks to begin! I'm running this in a ubuntu 18.4.5 VM on FreeNAS and have about 15 subdomains for various services I'm running configured with Proxy Hosts and SSL certificates I noticed that the certificates that are due for renewal on the 18 October hadn't, so manually updated one, which worked fine. When I came to look on the website and then here, I noticed I was a little behind (I was running 2.2.3) so through I'd update. I couldn't see any specific instructions so pulled the latest images and then stopped and started the containers using: docker pull jc21/nginx-proxy-manager docker pull jc21/mariadb-aria docker-compose down docker-compose up -d It started back up and I can access the WUI and see I now have 2.5.0, but when I click on a few of the menus nothing happens, specifically the Dashboard and SSL Certificate menus. It's still working, and even appears to have updated the certificates that were due, but I can't see the menu to check. Any ideas what I've done wrong and how to fix? Thanks in advance
kerem 2026-02-26 06:33:18 +03:00
Author
Owner

@crazybadger commented on GitHub (Oct 13, 2020):

I guess I'll just roll back to the previous version.

It would be helpful to add some update guidance on the website/github page to avoid similar issues.

<!-- gh-comment-id:707814225 --> @crazybadger commented on GitHub (Oct 13, 2020): I guess I'll just roll back to the previous version. It would be helpful to add some update guidance on the website/github page to avoid similar issues.
Author
Owner

@LewisSmallwood commented on GitHub (Oct 18, 2020):

I also have this problem @crazybadger when I upgraded from version 2.2.3 to 2.6.1.

How did you get it working again?

<!-- gh-comment-id:711432888 --> @LewisSmallwood commented on GitHub (Oct 18, 2020): I also have this problem @crazybadger when I upgraded from version 2.2.3 to 2.6.1. How did you get it working again?
Author
Owner

@k9barry commented on GitHub (Oct 18, 2020):

Try clearing your browser cache..... worked for me.

<!-- gh-comment-id:711441126 --> @k9barry commented on GitHub (Oct 18, 2020): Try clearing your browser cache..... worked for me.
Author
Owner

@jc21 commented on GitHub (Oct 19, 2020):

When you have these kind of problems more information is required. The docker logs would contain something if it were a backend issue and the browser console (F12) would contain something if it were frontend related.

@k9barry's solution is probably correct. Assuming this was a frontend caching issue, I have not encountered this before. The javascript assets of the UI are appended with the version number which should prevent browser caching and the UI will forcibly auto-reload if the backend is updated to a different version than the one the UI has expected. If clearing the browser cache doesn't fix the problem for you, please take a look at the logs/console and paste here if you need more help.

<!-- gh-comment-id:711457076 --> @jc21 commented on GitHub (Oct 19, 2020): When you have these kind of problems more information is required. The docker logs would contain something if it were a backend issue and the browser console (F12) would contain something if it were frontend related. @k9barry's solution is probably correct. Assuming this was a frontend caching issue, I have not encountered this before. The javascript assets of the UI are appended with the version number which should prevent browser caching and the UI will forcibly auto-reload if the backend is updated to a different version than the one the UI has expected. If clearing the browser cache doesn't fix the problem for you, please take a look at the logs/console and paste here if you need more help.
Author
Owner

@crazybadger commented on GitHub (Oct 25, 2020):

If it was something as simple as clearing the browser cache, that would support my suggestion for some better documentation around updating even more.

<!-- gh-comment-id:716114934 --> @crazybadger commented on GitHub (Oct 25, 2020): If it was something as simple as clearing the browser cache, that would support my suggestion for some better documentation around updating even more.
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#536
No description provided.