starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #504] Redirection target formatted incorrectly thus no redirect possible #431

New issue

Closed

opened 2026-02-26 06:32:49 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:32:49 +03:00

Owner

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

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
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? N/A

Describe the bug

Using v2.3.1, ~~I previously used v2.0.12 that didn't have the issue for sure~~ issue was in v2.0.12 as well
When adding a redirection host, the forward domain gets obfuscated which causes all redirects to fail

Forwarding destination https://www.google.com gets obfuscated to https//www.google.com/.

it allways add / at the end
it will remove the colon after https

I tried whether or not it makes a difference when setting up SSL or not, or changing some other settings.
But in all cases it gets the wrong format.

Originally created by @markverg on GitHub (Jul 14, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/504 **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** - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? **N/A** **Describe the bug** - Using v2.3.1, ~I previously used v2.0.12 that didn't have the issue for sure~ issue was in v2.0.12 as well - When adding a redirection host, the forward domain gets obfuscated which causes all redirects to fail Forwarding destination ``https://www.google.com`` gets obfuscated to ``https//www.google.com/``. - it allways add ```/``` at the end - it will remove the colon after ```https``` ![image](https://user-images.githubusercontent.com/21355013/87401690-c3ee8880-c5ba-11ea-962a-ba0f35815115.png) ![image](https://user-images.githubusercontent.com/21355013/87401731-d23ca480-c5ba-11ea-9967-f1f279b47ae1.png) I tried whether or not it makes a difference when setting up SSL or not, or changing some other settings. But in all cases it gets the wrong format.

kerem

2026-02-26 06:32:49 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:32:50 +03:00

Author

Owner

@BoxedBrain commented on GitHub (Oct 1, 2020):

The bug is still persistent in v2.5.0

@BoxedBrain commented on GitHub (Oct 1, 2020): The bug is still persistent in v2.5.0

kerem commented

2026-02-26 06:32:50 +03:00

Author

Owner

@chaptergy commented on GitHub (May 12, 2021):

This should be fixed by now, as it is working as expected.

@chaptergy commented on GitHub (May 12, 2021): This should be fixed by now, as it is working as expected.

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

No description provided.

Rows
Columns