mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #933] Unhandled Exceptions - All Modal Dialogs Broken in 2.8.0 When Routing NPM to localhost #791
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#791
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 @LanceMcCarthy on GitHub (Mar 8, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/933
Are you in the right place?
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
v2.8.0This used to work before the update, now it's not working any more. I don't know what version the regression started, but it's definitely in 2.8.0.
Add Proxy Host Error
Add SSL Certificate Error
Add 404 Host Errors
To Reproduce
Steps to reproduce the behavior:
127.0.0.1:81,localhost:81orhostname.local:81for the destinationExpected behavior
The model dialog appears, without exceptions, allowing you to complete the task that dialog is for.
Operating System
I have reproduced this issue on all of the following:
Additional Context - Works in hostname.local Confirmation
Just to make it clear this is only a problem over the proxied route, visit NPM via either
This is probably something wrong with the scripts being loaded, because it works fine when using localhost or hostname.local.
The error messages are similar to when you have incorrect relative URLs, or hardcoded paths in the s cript.
I can eliminate the script loading problem because main,js loads comepletely fine to the script tags and those methods are loaded in memory
Here's a final screenshot to prove it does work
@LanceMcCarthy commented on GitHub (Mar 12, 2021):
Update - Weirdly enough this does not occur when using the front-end from a mobile browser (MSFT Edge on Android 10)
@rclough commented on GitHub (Jun 13, 2021):
I'm also experiencing the same issue - the UI is unusable when I access it in Opera, but works fine when I use it in chrome (thanks to the issue I realized can workaround in a different browser)
@rclough commented on GitHub (Jun 13, 2021):
granted I use the unraid docker image, and I dont think I use localhost for it
@chaptergy commented on GitHub (Jun 14, 2021):
@LanceMcCarthy Which browser were you using? Ist this an opera-specific / browser-specific problem or does it appear in most browsers?
@LanceMcCarthy commented on GitHub (Jun 14, 2021):
It was chromium-based Microsoft Edge.
@LanceMcCarthy commented on GitHub (Jul 4, 2021):
This is still occurring in v2.9.4 with a fresh installation of nginxproxymanager (raspberry pi using docker-compose with default config settings)
These errors look a lot like when the root operator is null.
Broken UX
Due to the handled exceptions, the execution of the UI's layout is halted, which results in missing elements. Here is what the main page looks like after initial install and changing the the default admin credentials:
Consequential Side Effects
Environment
Windows 10 (latest 21H1 service update, build 19041)
Chromium-based Microsoft Edge