starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #273] Redirect IP:Port access to my domain w SSL #243

New issue

Closed

opened 2026-02-26 06:31:42 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 06:31:42 +03:00

Owner

Originally created by @hogmac on GitHub (Jan 14, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/273

I've successfully created my domain along with sub domains and they redirect to the proper IP:Port with no issue. The problem I'm facing is that my sites are still accessible using IP:Port and that does not redirect the URL to the domain and does not enable SSL.

Is there a way to set this up in the Custom Nginx Configuration?

What I'm trying to achieve as that when people access the site as x.x..x.x:8000 (being this my external IP address) they get redirected to the URL for the domain name instead since my domain already have SSL enabled.

Any ideas? Thank you

Originally created by @hogmac on GitHub (Jan 14, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/273 I've successfully created my domain along with sub domains and they redirect to the proper IP:Port with no issue. The problem I'm facing is that my sites are still accessible using IP:Port and that does not redirect the URL to the domain and does not enable SSL. Is there a way to set this up in the Custom Nginx Configuration? What I'm trying to achieve as that when people access the site as x.x..x.x:8000 (being this my external IP address) they get redirected to the URL for the domain name instead since my domain already have SSL enabled. Any ideas? Thank you

kerem

2026-02-26 06:31:42 +03:00

closed this issue
added the
stale
label

kerem commented

2026-02-26 06:31:43 +03:00

Author

Owner

@Cerothen commented on GitHub (Jan 26, 2020):

The easiest is to just close all the random open ports. That would force people to use the proper path since the existing path no longer exists.

To transition you could forward every currently open port (except 80/443) to a web server somewhere indicating the change.

@Cerothen commented on GitHub (Jan 26, 2020): The easiest is to just close all the random open ports. That would force people to use the proper path since the existing path no longer exists. To transition you could forward every currently open port (except 80/443) to a web server somewhere indicating the change.

kerem commented

2026-02-26 06:31:43 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 31, 2024):

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

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

kerem commented

2026-02-26 06:31:43 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 10, 2025):

Issue was closed due to inactivity.

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

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

No description provided.

Rows
Columns