mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #57] Ombi having weird issue #53
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#53
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 @KillerKongFu on GitHub (Jan 23, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/57
Ombi isn't working with this. I see the website but I can't login. If I try to log into Ombi with my plex account it just sends me to small login window again. Looks like this: https://snag.gy/3ldut5.jpg Any ideas?



My settings -
@vrelk commented on GitHub (Jan 24, 2019):
Did you set the application URL in ombi?
looking at the configs listed at
https://github.com/tidusjar/Ombi/wiki/Reverse-Proxy-Examples
try adding the following in advanced as they are missing in the default settings for NPM.
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Ssl on;
proxy_read_timeout 90;
@KillerKongFu commented on GitHub (Jan 24, 2019):
Yep application URL is correct in ombi. :(
Tried that and it didn't work.
A person in the Unraid forum provided this fix.
"If you disable Websockets Support then Plex authentication should work. I haven't looked into exactly why though." It worked right away after that.
@jc21 commented on GitHub (Jan 25, 2019):
Websockets support shouldn't be an issue here. I don't use ombi so I don't really know what's going on either. If using another nginx reverse proxy produces correct results, then there must be an issue with this project and we can find the point of difference.
@firrae commented on GitHub (Jan 27, 2019):
So by just turning off Websocket Support my forwarding works. No advanced options set, just the URL settings in Ombi itself.