[GH-ISSUE #1847] Reverse proxy with a path #1354

Closed
opened 2026-02-26 07:30:38 +03:00 by kerem · 6 comments
Owner

Originally created by @Ferrox12 on GitHub (Feb 12, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1847

Hi,
this is a question.
I have installed Nginx proxy manager on my terramaster nas on docker.
I have reserved a hostname (es. example.com) that point to my router. With that and with the port forwarding I reach the services I expone on the net (es. example.com:A, example.com:B).
Is it possible with the reverse proxy to reach them without entering the port but with a specific name? (es. example.com/A, example.com/B)

Originally created by @Ferrox12 on GitHub (Feb 12, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1847 Hi, this is a question. I have installed Nginx proxy manager on my terramaster nas on docker. I have reserved a hostname (es. example.com) that point to my router. With that and with the port forwarding I reach the services I expone on the net (es. example.com:A, example.com:B). Is it possible with the reverse proxy to reach them without entering the port but with a specific name? (es. example.com/A, example.com/B)
kerem 2026-02-26 07:30:38 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@AlthaTechnology commented on GitHub (Feb 13, 2022):

I use this with docker swarm. You put in the service name and it is able to redirect to that stack/service without having to bind ports.

All of our entries use service names and most of them on port 80, I think this is what you are asking. Does that answer the question?

This may be swarm specific behavior, I'm not sure. Swarm does it's own loadbalancing through an internal DNS server.
https://docs.docker.com/engine/swarm/ingress/

<!-- gh-comment-id:1038195767 --> @AlthaTechnology commented on GitHub (Feb 13, 2022): I use this with docker swarm. You put in the service name and it is able to redirect to that stack/service without having to bind ports. All of our entries use service names and most of them on port 80, I think this is what you are asking. Does that answer the question? This may be swarm specific behavior, I'm not sure. Swarm does it's own loadbalancing through an internal DNS server. [https://docs.docker.com/engine/swarm/ingress/](https://docs.docker.com/engine/swarm/ingress/)
Author
Owner

@Ferrox12 commented on GitHub (Feb 14, 2022):

No.
At the moment I have installed Nginx Proxy Manager on docker and with a hostname that is CNAME type I reach one of my services. I would like to use only a hostname (es. example.com) to reach everyone of them (es. example.com/name1, example.com/name2).
I don't know if this is possible. If it is, how can I set Nginx Proxy Manager?

<!-- gh-comment-id:1038710367 --> @Ferrox12 commented on GitHub (Feb 14, 2022): No. At the moment I have installed Nginx Proxy Manager on docker and with a hostname that is CNAME type I reach one of my services. I would like to use only a hostname (es. example.com) to reach everyone of them (es. example.com/name1, example.com/name2). I don't know if this is possible. If it is, how can I set Nginx Proxy Manager?
Author
Owner

@hoiber commented on GitHub (Feb 15, 2022):

Hey Mate,
I would suggest using subdomains rather than a url extension. eg name1.example.com instead of example.com/name1. This will allow you to set up DNS using the subdomain, doesn't have to be public unless you want the service to be available outside your local network (wouldn't recommend this would look at SD WAN or VPN solutions unless you need it available to others) but it will still work either way. The will allow you to enter the port and "link" it to the subdomain.

image

<!-- gh-comment-id:1040180057 --> @hoiber commented on GitHub (Feb 15, 2022): Hey Mate, I would suggest using subdomains rather than a url extension. eg name1.example.com instead of example.com/name1. This will allow you to set up DNS using the subdomain, doesn't have to be public unless you want the service to be available outside your local network (wouldn't recommend this would look at SD WAN or VPN solutions unless you need it available to others) but it will still work either way. The will allow you to enter the port and "link" it to the subdomain. ![image](https://user-images.githubusercontent.com/51186531/154056232-789a34c4-f8b9-42ff-8ca5-d913e10b87fd.png)
Author
Owner

@Ferrox12 commented on GitHub (Feb 15, 2022):

This is what I don't want to do. I don't want have a number of subdomains. Maybe I cant't do what i want with Nginx, I don't know...

<!-- gh-comment-id:1040298605 --> @Ferrox12 commented on GitHub (Feb 15, 2022): This is what I don't want to do. I don't want have a number of subdomains. Maybe I cant't do what i want with Nginx, I don't know...
Author
Owner

@hoiber commented on GitHub (Feb 15, 2022):

ah right, yeah i dont think it will work they way you want it to sorry.

<!-- gh-comment-id:1040864047 --> @hoiber commented on GitHub (Feb 15, 2022): ah right, yeah i dont think it will work they way you want it to sorry.
Author
Owner

@Ferrox12 commented on GitHub (Feb 15, 2022):

Thanks for the help

<!-- gh-comment-id:1040871516 --> @Ferrox12 commented on GitHub (Feb 15, 2022): Thanks for the help
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#1354
No description provided.