starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2270] Proxy Hosts with port in the domain field fail to redirect properly #1619

New issue

Closed

opened 2026-02-26 07:31:47 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:31:47 +03:00

Owner

Originally created by @0chroma on GitHub (Sep 17, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2270

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug
When adding a port to the end of a proxy host's domain, NPM fails to set the proxy up properly

Nginx Proxy Manager Version
1.26.1

To Reproduce
Steps to reproduce the behavior:

Go to Proxy Hosts
Create new Proxy Host
Enter a domain with a port on the end (ie my.domain.com:8114)
Forward to working host and save
connection to my.domain.com:8114 fails

Expected behavior
proxy host forwards correctly

Screenshots
n/a

Operating System
raspberry pi OS, docker image

Additional context
I found that adding listen 8114 ssl default_server; to the custom config tab made it work as expected. If there's no SSL cert selected for the domain, then you can omit the ssl part.

Originally created by @0chroma on GitHub (Sep 17, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2270 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** When adding a port to the end of a proxy host's domain, NPM fails to set the proxy up properly **Nginx Proxy Manager Version** 1.26.1 **To Reproduce** Steps to reproduce the behavior: 1. Go to Proxy Hosts 2. Create new Proxy Host 3. Enter a domain with a port on the end (ie my.domain.com:8114) 4. Forward to working host and save 5. connection to my.domain.com:8114 fails **Expected behavior** proxy host forwards correctly **Screenshots** n/a **Operating System** raspberry pi OS, docker image **Additional context** I found that adding `listen 8114 ssl default_server;` to the custom config tab made it work as expected. If there's no SSL cert selected for the domain, then you can omit the `ssl` part.

kerem

2026-02-26 07:31:47 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:31:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 9, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 9, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:31:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 25, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 25, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 07:35:42 +03:00

[GH-ISSUE #3749] Document all available API endpoints #2472

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#1619

No description provided.

Rows
Columns