starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

Redirect - doesn't work on https #1999

New issue

Closed

opened 2026-02-26 07:33:38 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 07:33:38 +03:00

Owner

Originally created by @quadcom on GitHub (May 15, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2920

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

NPM v2.10.3
NPM > Settings > Default Site

I have this set to redirect to google.com.

I went to test it hitting my public IP and the redirect works for 443 but not for 80.

I then used an old subdomain I had set up which was still pointing to my IP.

If I hit the domain naked, I get the unknown domain redirection
If I add the protocol 'http' I get the redirection
If I add the protocol 'https' I don't get the redirection.

Nginx Proxy Manager Version
Unraid
jc21/nginx-proxy-manager
v2.10.3

To Reproduce
Steps to reproduce the behavior:

Go to - Setting > Default Site - Set to redirect to any (ie, google.com)
Browse to your public IP or a naked URL that is not currently listed as a host -> The redirect works
Browse to the same IP/URL but add https protocol -> Redirect will not happen

Expected behavior
I expected any hit on the NPM server with an unknown host would be redirected.

Additional context

Tested in FireFox -> 112.0.2 (64-bit), Windows 10

Originally created by @quadcom on GitHub (May 15, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2920 **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** NPM v2.10.3 NPM > Settings > Default Site I have this set to redirect to google.com. I went to test it hitting my public IP and the redirect works for 443 but not for 80. I then used an old subdomain I had set up which was still pointing to my IP. If I hit the domain naked, I get the unknown domain redirection If I add the protocol 'http' I get the redirection If I add the protocol 'https' I don't get the redirection. **Nginx Proxy Manager Version** Unraid jc21/nginx-proxy-manager v2.10.3 **To Reproduce** Steps to reproduce the behavior: 1. Go to - Setting > Default Site - Set to redirect to any (ie, google.com) 2. Browse to your public IP or a naked URL that is not currently listed as a host -> The redirect works 3. Browse to the same IP/URL but add https protocol -> Redirect will not happen ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/7085931/dfd8225e-a6c2-4885-9950-7f1ebab921c8) ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/7085931/93d6606d-2754-4879-bca4-e1b03d3d45e0) **Expected behavior** I expected any hit on the NPM server with an unknown host would be redirected. **Additional context**  Tested in FireFox -> 112.0.2 (64-bit), Windows 10

kerem

2026-02-26 07:33:38 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:33:38 +03:00

Author

Owner

@XNarno commented on GitHub (May 31, 2023):

Same issue here

@XNarno commented on GitHub (May 31, 2023): Same issue here

kerem commented

2026-02-26 07:33:38 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 19, 2024):

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

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

kerem commented

2026-02-26 07:33:38 +03:00

Author

Owner

@quadcom commented on GitHub (Jan 19, 2024):

I consider this issue not insignificant.

I think this needs to be addressed or an explanation as to why this isn't a security concern.

@quadcom commented on GitHub (Jan 19, 2024): I consider this issue **not** insignificant. I think this needs to be addressed or an explanation as to why this isn't a security concern.

kerem commented

2026-02-26 07:33:38 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 8, 2024):

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

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

kerem commented

2026-02-26 07:33:38 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 29, 2025):

Issue was closed due to inactivity.

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

kerem referenced this issue

2026-02-26 08:30:57 +03:00

[PR #1999] [CLOSED] Streams Basic Load Balancing (Allows multiple Forwarding Hosts) #3521

kerem referenced this issue

2026-02-26 08:31:53 +03:00

[PR #3841] feat(streams): Simple Load Balancing of Streams #3769

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

No description provided.

Rows
Columns