[GH-ISSUE #118] Add url path for custom location #104

Closed
opened 2026-02-26 05:34:35 +03:00 by kerem · 4 comments
Owner

Originally created by @jancoow on GitHub (Apr 15, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/118

Hi there.

I'm trying to add a few custom locations for a specific proxy host. However, I'm unable to get this working with the web interface. It's not possible to add an URL path for the forward host name.

For example: This is the generated proxy pass:
proxy_pass http://192.168.1.2:9005;

However, I need to add a trailing slash:
proxy_pass http://192.168.1.2:9005/;

It works fine when I manually edit the nginx config. But it would be more useful if this can be done from the web UI.

Originally created by @jancoow on GitHub (Apr 15, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/118 Hi there. I'm trying to add a few custom locations for a specific proxy host. However, I'm unable to get this working with the web interface. It's not possible to add an URL path for the forward host name. For example: This is the generated proxy pass: proxy_pass http://192.168.1.2:9005; However, I need to add a trailing slash: proxy_pass http://192.168.1.2:9005/; It works fine when I manually edit the nginx config. But it would be more useful if this can be done from the web UI.
kerem closed this issue 2026-02-26 05:34:35 +03:00
Author
Owner

@jlesage commented on GitHub (Apr 15, 2019):

It should work. In the Forward Hostname / IP field, set the following value (see the ending slash):

192.168.1.2/
<!-- gh-comment-id:483264827 --> @jlesage commented on GitHub (Apr 15, 2019): It should work. In the `Forward Hostname / IP` field, set the following value (see the ending slash): ``` 192.168.1.2/ ```
Author
Owner

@jancoow commented on GitHub (Apr 15, 2019):

@jlesage

That only works when no port is given. Otherwise it will be set to 192.168.1.2/:9005

<!-- gh-comment-id:483267679 --> @jancoow commented on GitHub (Apr 15, 2019): @jlesage That only works when no port is given. Otherwise it will be set to 192.168.1.2/:9005
Author
Owner

@jlesage commented on GitHub (Apr 15, 2019):

Make sure to use the latest image version. This has been fixed.

<!-- gh-comment-id:483269078 --> @jlesage commented on GitHub (Apr 15, 2019): Make sure to use the latest image version. This has been fixed.
Author
Owner

@jancoow commented on GitHub (Apr 15, 2019):

@jlesage
Thanks, that solved the issue.

I pulled the latest version a weeks ago, and was running the image created on 2019-03-05. It should be working in this version, according the change log:
"Also adds sub-folder locations for Proxy Hosts, many thanks to kolbii"

It does work as expecting in the 2019-04-11 version.

<!-- gh-comment-id:483275325 --> @jancoow commented on GitHub (Apr 15, 2019): @jlesage Thanks, that solved the issue. I pulled the latest version a weeks ago, and was running the image created on 2019-03-05. It should be working in this version, according the change log: "Also adds sub-folder locations for Proxy Hosts, many thanks to kolbii" It does work as expecting in the 2019-04-11 version.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#104
No description provided.