mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #32] HTTP Services all 404 #29
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#29
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 @coolsaber57 on GitHub (Dec 4, 2018).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/32
Hello,
This may be more of an NGINX issue, but I'm trying to proxy my internal services (just HTTP at this point)(Sonarr/Radarr/Lidarr/etc.) to my server that's running the services, but all show the 404 page.
I'm trying to access, for example:
my.site/embyMy config for this is:
I have a working config on another machine (just command line/config files only) where this works.
For other services, I had to use:
proxy_pass http://localip:8800/sabnzbd/Which appends a "/sabnzbd" after the Port number (Sonarr/Radarr/Lidarr/Sabnzbd require this).
My questions are:
@coolsaber57 commented on GitHub (Dec 5, 2018):
As an addendum to this, setting these up as sub-domains instead of the folder structure does work (forwards correctly).
@cTurtle98 commented on GitHub (Feb 19, 2019):
I believe you are having the same problem as issue #40
@chaptergy commented on GitHub (May 10, 2021):
Closing this, as there now are custom locations available for hosts.