mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #689] Multiple listening ports / services for single domain / host #584
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#584
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 @wasn-eu on GitHub (Nov 5, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/689
Describe the solution you'd like
i have sometimes more than one port for a domain that i need to open and use a lets encrypt certificat.
i would like to add a the same domain multiple times with different listen ports and forward these to different ips and ports.
@chaptergy commented on GitHub (May 12, 2021):
As the advanced config is inserted inside the
server { }block:you can add custom nginx configuration there to do this. As the advanced tab is just normal nginx code, support on this github repo will be very limited for this. If anyone wants to share their working configuration, you are very welcome to do so, but unfortunately we can't provide nginx help.
@ylluminate commented on GitHub (Sep 13, 2021):
@chaptergy thank you for your example and suggestion. Can you clarify that if simply wanting to listen to (pass through) multiple ports, say 80, 443, and 3000, one might simply have the following without any
ssl_certificate_key,location, etc. definitions so that Nginx Proxy Manager handles those aspects for us?:In my use case I'm attempting to configure CapRover and it requires other ports in addition to just standard http(s).
@Freddyqt commented on GitHub (Jul 31, 2022):
I had a similar problem, that I needed to open port 8080 of a service. what I did was set up the docker-compose.yml file and add '8080:8080' , then create a proxy host and manually had to set it to listen on port 8080 and not port 80.