-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Redirect Issue #63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
update:
This might cause this issue! If I delete the scheme "https://" within my redirect, all desired things work. Perhaps it will be good to specify this somewhere in the GUI for other noobs like me ;) |
Regarding the location TL;DR for below: please try again with the latest docker image. To simplify the setup required, you just want to
When it comes to redirecting and SSL, when the destination http server supports both HTTP and HTTPS connections (as a Proxy Host does), your Redirection Host doesn't need to Force SSL because you'll want to leave that determination up to the destination. However if the destination server only supported HTTPS then you'd want to force SSL before it even got to the destination. A redirection host will forward to the destination on the same protocol scheme requested, and if force SSL is on then it will redirect to that first. Btw, when I say that the server supports HTTP and HTTPS I mean from an open port point of view, not from a Proxy Host configured to forward both point of view. |
I am having this issue as well. I want to redirect to an https but I get https://http//url. The URL is an IP address that requires https. |
I'm going to need to see the configuration for these hosts.
|
Shortly after your comment PR #883 was merged. I'm assuming this fixed the issue. If it did not, let me know and I can reopen the issue. |
I am also having this issue with redirection hosts. Attached are some screenshots, I hope that it's useful. |
I know this is a zombie issue but I am also running into this with the same exact result as the poster above me. |
Issue still persist in v2.11.3 using 308 still getting double https:// on a redirection host. |
I found a solution. It's not an Issue with nginx-proxy-manager. The problem is, that a permanent redirect is cached a Webbrowser. You can test it using curl and check the I recommend changing HTTP Code to 307 Temporary Redirect to prevent this.
|
As discussed in this issue, I think this is not possible with Nginx Proxy Manager. See this reddit post |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
the following szenario I would like to achive:
All of the following should point to the same URL https://www.subdomain.domain.tld:
1) Szenarios for Proxy Host:
1a) Szenario: https://www.subdomain.domain.tld --> create Reverse Proxy Host inkl. SSL
1b) Szenario: http://www.subdomain.domain.tld --> without ssl --> Update Reverse Proxy from 1a) to Force SSL
2) Szenario for Redirect Host
2a) Szenario: http://subdomain.domain.tld -->create Redirect Host (point to URL from 1a)
2b) Szenario: https://subdomain.domain.tld --> update Redirect Host from 2a) to SSL + Force SSL
Testing:
1a) works as specified
1b) works as specified
2a) does not work: url is redirected to https://http//subdomain.domain.tld
2b) does not work - like 2a)
If if I try to disable "Force SSL" within the Redirect Host but it does not save this new setting. (the same as specifed for http/2 in #61 --> perhaps there should be a new issue opened?!)
I deleted the Redirect Host from 2) and created the a new one with SSL settings, but without "Forced SSL". Same picture.
Can some verify my observation? Or do I missunderstand something how to use this manager?
Thanks a lot!
The text was updated successfully, but these errors were encountered: