Hi All,

I've set up Nginx proxy manager and have  Organizr linked based on my personal domain. the issue I can't seem to understand is how to get custom locations to work

I would really like to have

mydomain.com/sonarr ect

does anyone else have this set up and could you please help me achieve the same.

 

I've tried under the custom location

Location: /sonarr

Host: 10.0.0.19

port: 8989

 

yet it doesn't work 

 

Many thanks

 

Edited February 9, 20251 yr by Phairplay

... hard ask... I think subdomains and other spacing... unless you are using the tailscale server feature alongside nginx???

Configuring Nginx Proxy Manager (NPM) to serve applications like Sonarr under a subdirectory (e.g., mydomain.com/sonarr) can be challenging due to how certain web applications handle base paths. Many applications are designed to run at the root (/) and may not support being served from a subdirectory without additional configuration

 

Challenges:

Application Base Path: Applications like Sonarr may not have built-in support for running under a subdirectory. This means that even if NPM is configured to proxy mydomain.com/sonarr to http://10.0.0.19:8989, Sonarr might still generate URLs pointing to / instead of /sonarr, leading to broken links and missing assets.

 

Potential Solutions:

Subdomain Approach: Instead of using a subdirectory, consider setting up a subdomain for Sonarr, such as sonarr.mydomain.com. This approach is generally more straightforward and avoids many of the issues associated with subdirectory configurations.

 

Custom Nginx Configuration: If a subdomain is not desirable, you can attempt to modify the Nginx configuration to rewrite URLs appropriately. However, this can be complex and may not work seamlessly with all applications.

As its not clear...if using nginx with tailscale

 

What is Tailscale's Serve Feature?

Tailscale's Serve feature allows you to route traffic through a Tailscale device, making internal services accessible over a secure, private Tailscale network without needing public exposure.

For example:

Tailscale URL: https://<tailscale-device-name>.tailscale.net/sonarr

Internal Nginx URL: Proxies traffic to an internal service like Sonarr at http://10.0.0.19:8989.

Asumeing tailscale plugin is installed and you have tailscale VPN up

tailscale serve https /sonarr http://10.0.0.19:8989

or 

subdomain name setup:

tailscale serve https://sonarr.yourdomain.tailscale.net http://10.0.0.19:8989

 

Other docs and examples:

 

nginx proxy rewrite example for sonar:

location /sonarr/ {
    proxy_pass http://10.0.0.19:8989/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;

    # Optional: Handle URL rewrites for Sonarr assets and API paths
    sub_filter '/css/' '/sonarr/css/';
    sub_filter '/js/' '/sonarr/js/';
    sub_filter_once off;

    # Handle trailing slashes for API routes
    rewrite ^/sonarr/(.*)$ /$1 break;
}

 

Otherwise you will need to heavily edit sonar and how its web pages and systems work and point back to xyz file...

Steps to Configure a Custom Location in NPM:

Access NPM Admin Interface:

Navigate to your NPM dashboard.

Edit Proxy Host:

Select the proxy host associated with your domain (mydomain.com).

Add Custom Location:

Click on the "Custom Locations" tab.

Add a new location with the following details:

Location: /sonarr

Forward Hostname/IP: 10.0.0.19

Forward Port: 8989

 

Advanced Configuration:

In the "Advanced" tab of the custom location, you might need to add additional Nginx directives to handle URL rewrites and header modifications.

example:

location /sonarr/ {
    proxy_pass http://10.0.0.19:8989/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    sub_filter '/css/' '/sonarr/css/';
    sub_filter '/js/' '/sonarr/js/';
    sub_filter_once off;
}

Community Insights: Users have reported mixed success with similar configurations. For instance, a discussion on the Nginx Proxy Manager GitHub issue tracker highlights challenges and potential solutions when setting up custom locations. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1563

Hi,

thank you for the detailed response.

I do think the solution I will take is the subdomain as it'll be cleaner and more manageable.