NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Stream and Proxyhost side by side with default
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
Trying to setup mailu with NginxProxyManager and it requires that both http and https to be redirected to the front server.
Would be awesome if we could say if we receive:
- in the port 443 -> send through https to IP_serverA
- in the port 80 -> send through http to IP_serverA
I don't think this is possible because ssl needs to be setup in serverA and nginx need to just pass through so I don't think proxy server is possible.
But we could do it with a stream
stream {
map $ssl_preread_server_name $backend_upstream {
default 127.0.0.1:444; # fallback (optional)
mail.A.com IP_serverA:443;
mail.B.com IP_serverA:443;
mail.C.com IP_serverA:443;
}
server {
listen 443;
proxy_pass $backend_upstream;
ssl_preread on;
}
}
And because we did a default maybe we could use proxyhosts alongside if we could listen on port 444 because it would go to our default and we could redirect/proxy from there
Describe the solution you'd like
would like to have streams and proxy hosts run side by side with help of default. I don't think we would need an alteration of UI but documentation on how to do this would be awesome. didn't find anything.
Describe alternatives you've considered
maybe i can do this with 2 dockers just put default as other nginx proxy manager
Additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Mailu and Nginx Proxy Manager setup described in the issue, focusing on Nginx stream configuration, proxy hosts, and the proposed 443-to-444 fallback. Verify whether stream routing and proxy hosts can coexist as requested, or whether documentation for a two-container setup is the appropriate outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100