Upgraded to v2.9.4 - frontend no longer usable
See original GitHub issueChecklist
- 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
Describe the bug
I am running NPM using docker-compse. where I ran docker-compose pull
and then docker-compose up -d
When the app started, I logged into the new version and instead of having the dashboard/proxy hosts I cannot see anything. I check the Chrome console tab and see a bunch of these:
Welcome to Nginx Proxy Manager
main.bundle.js?v=2.9.4:3 You are logged in as Daniel Anner
main.bundle.js?v=2.9.4:1 TypeError: Cannot read property 'extend' of undefined
at Object.213 (7.bundle.7.js:1)
at r (main.bundle.js?v=2.9.4:1)
at Object.181 (7.bundle.7.js:1)
at r (main.bundle.js?v=2.9.4:1)
at main.bundle.js?v=2.9.4:27
r.oe @ main.bundle.js?v=2.9.4:1
Promise.catch (async)
showNginxProxy @ main.bundle.js?v=2.9.4:27
Ze @ main.bundle.js?v=2.9.4:3
(anonymous) @ main.bundle.js?v=2.9.4:3
(anonymous) @ main.bundle.js?v=2.9.4:3
execute @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:27
Ct @ main.bundle.js?v=2.9.4:3
loadUrl @ main.bundle.js?v=2.9.4:27
start @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:3
m @ main.bundle.js?v=2.9.4:27
f @ main.bundle.js?v=2.9.4:27
d @ main.bundle.js?v=2.9.4:27
o.trigger @ main.bundle.js?v=2.9.4:27
O @ main.bundle.js?v=2.9.4:27
render @ main.bundle.js?v=2.9.4:27
ae @ main.bundle.js?v=2.9.4:27
show @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:3
Promise.then (async)
onStart @ main.bundle.js?v=2.9.4:3
O @ main.bundle.js?v=2.9.4:27
start @ main.bundle.js?v=2.9.4:27
(anonymous) @ main.bundle.js?v=2.9.4:293
d @ main.bundle.js?v=2.9.4:27
l @ main.bundle.js?v=2.9.4:27
setTimeout (async)
(anonymous) @ main.bundle.js?v=2.9.4:27
u @ main.bundle.js?v=2.9.4:27
fireWith @ main.bundle.js?v=2.9.4:27
fire @ main.bundle.js?v=2.9.4:27
u @ main.bundle.js?v=2.9.4:27
fireWith @ main.bundle.js?v=2.9.4:27
ready @ main.bundle.js?v=2.9.4:27
V @ main.bundle.js?v=2.9.4:27
7.bundle.7.js:1 Uncaught (in promise) TypeError: Cannot read property 'extend' of undefined
at Object.213 (7.bundle.7.js:1)
at r (main.bundle.js?v=2.9.4:1)
at Object.181 (7.bundle.7.js:1)
at r (main.bundle.js?v=2.9.4:1)
at main.bundle.js?v=2.9.4:27
Nginx Proxy Manager Version 2.9.4
Screenshots
Operating System Alpine Linux 3.13.5, Docker 20.10.3, Docker-Compose 1.27.4
Additional context Logs: https://pastebin.com/swz7nvse
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Upgraded to v2.9.4 - frontend no longer usable · Issue #1219
This is not specific to 2.9.4. This issue pops up from time to time with some users. Forcibly clearing your browser cache has...
Read more >2022.12: It does matter! - Home Assistant
Everything became more stable and faster, and the UX made leaps forwards ... Update frontend to 20221208.0 (@bramkragten - #83551) (frontend ...
Read more >Frequently Asked Questions - MythTV Official Wiki
If a backup of the mythconverg database was not made before upgrading, a downgrade will likely be impossible without recreating the database ( ......
Read more >ThemeNectar | Changelogs - Salient
v15 is a major release. After updating, remember to clear the cache from any performance plugins you have active as well as your...
Read more >Changelog - Sourcegraph docs
The extension registry no longer supports browsing, creating, or updating legacy ... CACHE_DIR has been removed from the sourcegraph-frontend deployment.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I experienced this issue too.
Running Edge Version 91.0.864.70 (Official build) (64-bit)
Tried clearing site data via Developer console. No change. Tested Incognito and there was no problem.
Cleared site data again and restarted Edge, still the same issue.
Going into Privacy, search and services > Clear browsing data > Cached images and files This fixed it.
I just upgraded from 2.9.0 to 2.9.4 and encountered this briefly, quick browser cache refresh did the trick