mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #337] URL based Reverse Proxy #296
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#296
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 @armagankaratosun on GitHub (Mar 24, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/337
Hello all,
I want to use nginx-proxy-manager to access my internal web services. But my problem is, I only want to use the IP of the nginx-proxy-manager to redirect my services based on URL, like
internal-service-1 -> http://nginx-proxy-manager-ip/internal-service-1
internal-service-2 -> http://nginx-proxy-manager-ip/internal-service-2
internal-service-3 -> https://nginx-proxy-manager-ip/internal-service-3
like;
Is it possible? If yes, how?
Regards,
@miguelwill commented on GitHub (Mar 24, 2020):
yes, It works
only check with DNS
@armagankaratosun commented on GitHub (Mar 25, 2020):
The problem is I don't have DNS, I only have IP address of the proxy-manager. I can't even edit my /etc/hosts file (or Windows equivalent).
@miguelwill commented on GitHub (Apr 6, 2020):
to take advantage of the option to use a name that is addressed to several IPs I would recommend using dnsmasq, since you can define them using the hosts table
@wtf911 commented on GitHub (Apr 15, 2020):
You can use the custom location in nginx-proxy-manager to do this super easy no dnsmasq needed. make /service1/ point to service 1 and add location for /service/2 to point to service 2 ...and poof it works. www.test.com/service2/ etc.....
@miguelwill commented on GitHub (Apr 16, 2020):
That's right, using folders you can route to other destinations and ports
the use of DNS was to direct in round-robin mode to more than one system or IP in the backend, as in the case of a cluster of web servers
@Motordom commented on GitHub (May 8, 2020):
@wtf911 could you share your setup for qbittorrent? I cant get it working, keep getting 502 :(
@wtf911 commented on GitHub (May 8, 2020):
@Motordom You need to change a setting in qbittorrent. You have to disable one of those security ones under webui in options so it will allow that kind of redirect I think that's what I did. Also note the slashes "/" I used in my previous comments screenshot making sure to have or not have a slash can be the difference of it working or not.