NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Support custom port for proxy host domain name
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.
Press Add Proxy Host i have option to add domain names. Added domain names then appear in Proxy Hosts table where on first column appear domain names which can be then clicked and you are forwarded to the page.
For example when i want use foo.bar.eu on different port i can add domain name 'foo.bar.eu:11111'. When i click then in Proxy Hosts table on my link i am correctly forwarded to foo.bar.eu:11111, but when i want create SSL certificate using dns the the whole address is provided to certbot but the port in domain name is causing issue.
I am curious if you can add support for custom port so i would be able generate certificate for foo.bar.eu but in table i would be able to click on foo.bar.eu:11111 to access that web page.
Describe the solution you'd like
Somehow be able to modify link for domain to access web on different port. So i would be able to generate certificate for foo.bar.eu but url for page would be foo.bar.eu:11111
Describe alternatives you've considered
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 at the Add Proxy Host flow, the Proxy Hosts table link generation, and the certificate creation path that passes the address to certbot. Trace how the domain and port are stored and used. Done means certificates use foo.bar.eu while the table link opens foo.bar.eu:11111.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx, typescript
- Domain
- backend, frontend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100