[GH-ISSUE #2588] Nginx Proxy Manager is redirecting an HTTP URL to HTTPS #1803

Closed
opened 2026-02-26 07:32:31 +03:00 by kerem · 5 comments
Owner

Originally created by @RobertBrown3 on GitHub (Feb 4, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2588

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • No
  • 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
      I have set up an HTTP proxy host on the Nginx Proxy Manager. There are no HTTPS redirects defined for this URL. In fact, there is no redirection defined in the redirect_host directory (in fact, that directory is empty).

No erros are generated when attempting to access the URL. In fact the error log for this URL (proxy-host-1_failure.log) remains empty.
Nevertheless, when attempting to access the URL using http, the proxy manager appears to redirect my request to https. I simply cannot access my page.

Nginx Proxy Manager Version
V2.9.19

To Reproduce
Steps to reproduce the behavior:

  1. Go to the dashboard
  2. Select Proxy Hosts
  3. Click on "Add Proxy Host"
  4. Enter the domain name (temp.soliannet.net in my case).
  5. Turn on "Block Common Exploits"
  6. Click "Save"
  7. Attempt to access http://temp.soliannet.net (Using Firefox)
  8. See the browser redirect to https://temp.soliannet.net

Expected behavior
The web page at temp.soliannet.net should come up

Screenshots
None.

Operating System
Almalinux V8.6

Originally created by @RobertBrown3 on GitHub (Feb 4, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2588 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - No - 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** I have set up an HTTP proxy host on the Nginx Proxy Manager. There are no HTTPS redirects defined for this URL. In fact, there is no redirection defined in the redirect_host directory (in fact, that directory is empty). No erros are generated when attempting to access the URL. In fact the error log for this URL (proxy-host-1_failure.log) remains empty. Nevertheless, when attempting to access the URL using http, the proxy manager appears to redirect my request to https. I simply cannot access my page. **Nginx Proxy Manager Version** V2.9.19 **To Reproduce** Steps to reproduce the behavior: 1. Go to the dashboard 2. Select Proxy Hosts 3. Click on "Add Proxy Host" 4. Enter the domain name (temp.soliannet.net in my case). 5. Turn on "Block Common Exploits" 6. Click "Save" 7. Attempt to access http://temp.soliannet.net (Using Firefox) 8. See the browser redirect to https://temp.soliannet.net **Expected behavior** The web page at temp.soliannet.net should come up **Screenshots** None. **Operating System** Almalinux V8.6
kerem 2026-02-26 07:32:31 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@Arkensor commented on GitHub (Feb 7, 2023):

Are you using a .dev .app or .page tld by any chance? We just had an issue where the tld is on a HSTS force list so any request made must be served via https. So the only way to access the NPM is through the direct IP

<!-- gh-comment-id:1421034282 --> @Arkensor commented on GitHub (Feb 7, 2023): Are you using a .dev .app or .page tld by any chance? We just had an issue where the tld is on a HSTS force list so any request made must be served via https. So the only way to access the NPM is through the direct IP
Author
Owner

@RobertBrown3 commented on GitHub (Feb 8, 2023):

Arkensor:

No, I am not using a .dev .app or any kind of tld. The target is a Java- based executable JAR that is running from within another Docker container.

I actually have both the proxy and the Java application running in two places: the first place is a DigitalOcean test droplet running Docker on Almalinux 8, and the second place is a machine running Docker on Almalinux 8 in my private cloud. The installation on DigitalOcean is running without redirect problems. The one on my private cloud is doing the redirects.

I am using the same version of Docker on both systems. Everything on both systems is the same except the name of the actual VM.

There is something in the configuration of my proxy on my cloud that is causing it to do the redirect. I do not know what it is, though. I actually removed the Nginx Proxy Manager's data and the image, and reinstalled it through docker-compose. The redirect continues. I even removed the volume I had for persistence, removed the data and image, reinstalled the image, and set up my proxy to my target application from scratch. The redirects continue!

I am certain that there is either some unknown volume within the container or some unknown configuration on my machine that the Nginx Proxy Manager uses in order to "decide" to forward to HTTPS. I just cannot figure out what is causing the redirect! All I know for sure is that something is causing the redirect -- some bug in the Manager.

<!-- gh-comment-id:1421854079 --> @RobertBrown3 commented on GitHub (Feb 8, 2023): Arkensor: No, I am not using a .dev .app or any kind of tld. The target is a Java- based executable JAR that is running from within another Docker container. I actually have both the proxy and the Java application running in two places: the first place is a DigitalOcean test droplet running Docker on Almalinux 8, and the second place is a machine running Docker on Almalinux 8 in my private cloud. The installation on DigitalOcean is running without redirect problems. The one on my private cloud is doing the redirects. I am using the same version of Docker on both systems. Everything on both systems is the same except the name of the actual VM. There is something in the configuration of my proxy on my cloud that is causing it to do the redirect. I do not know what it is, though. I actually removed the Nginx Proxy Manager's data and the image, and reinstalled it through docker-compose. The redirect continues. I even removed the volume I had for persistence, removed the data and image, reinstalled the image, and set up my proxy to my target application from scratch. The redirects continue! I am certain that there is either some unknown volume within the container or some unknown configuration on my machine that the Nginx Proxy Manager uses in order to "decide" to forward to HTTPS. I just cannot figure out what is causing the redirect! All I know for sure is that something is causing the redirect -- some bug in the Manager.
Author
Owner

@Arkensor commented on GitHub (Feb 13, 2023):

@RobertBrown3 so I assume you are accessing the web interface from an IP directly? If so indeed none of the secure space tld stuff would affect it.

<!-- gh-comment-id:1427605877 --> @Arkensor commented on GitHub (Feb 13, 2023): @RobertBrown3 so I assume you are accessing the web interface from an IP directly? If so indeed none of the secure space tld stuff would affect it.
Author
Owner

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

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

<!-- gh-comment-id:1913407562 --> @github-actions[bot] commented on GitHub (Jan 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

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

Issue was closed due to inactivity.

<!-- gh-comment-id:2723141362 --> @github-actions[bot] commented on GitHub (Mar 14, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
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#1803
No description provided.