Redirect HTTP to HTTPS feature with explicit port #1198

New issue

Open

opened 2026-02-20 18:03:47 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 18:03:47 -05:00

Owner

Originally created by @vincent-polite on GitHub (Feb 26, 2020).

Originally assigned to: @NGPixel on GitHub.

Describe the bug
Redirect HTTP to HTTPS doesn't use the ports defined in the configuration

To Reproduce
Steps to reproduce the behavior:

Turn on HTTP to HTTPS redirect in Administration > SSL section
Surf to http://:3000
Redirect goes to https:// without a specific port.

Expected behavior
In my use case, I'm already hosting IIS at ports 80 and 443 and running wikijs as a standalone on ports 3000 and 3443. I thought this feature would map my requests to :3000 to :3443 and change the protocol to https.

Host Info (please complete the following information):

OS: Windows 2019, running node server as windows service
Wiki.js version: 2.1.113
Database engine: MSSQL 2019

Originally created by @vincent-polite on GitHub (Feb 26, 2020). Originally assigned to: @NGPixel on GitHub. **Describe the bug** Redirect HTTP to HTTPS doesn't use the ports defined in the configuration **To Reproduce** Steps to reproduce the behavior: 1. Turn on HTTP to HTTPS redirect in Administration > SSL section 2. Surf to http://<path-to-wiki>:3000 3. Redirect goes to https://<path-to-wiki> without a specific port. **Expected behavior** In my use case, I'm already hosting IIS at ports 80 and 443 and running wikijs as a standalone on ports 3000 and 3443. I thought this feature would map my requests to :3000 to :3443 and change the protocol to https. **Host Info (please complete the following information):** - OS: Windows 2019, running node server as windows service - Wiki.js version: 2.1.113 - Database engine: MSSQL 2019

deekerman added the

enhancement

contrib-medium

labels

2026-02-20 18:03:47 -05:00

deekerman commented

2026-02-20 18:03:49 -05:00

Author

Owner

@NGPixel commented on GitHub (Feb 27, 2020):

The default ports (3000 and 3443) are meant to be remapped to 80 and 443 at some point in your network (either at docker level, reverse-proxy or firewall) as it's not ideal to ask your users to add :3000 / :3443 when loading your wiki.

However an option could be added to add the HTTPS port to the redirect URL, for this specific scenario.

@NGPixel commented on GitHub (Feb 27, 2020): The default ports (3000 and 3443) are meant to be remapped to 80 and 443 at some point in your network (either at docker level, reverse-proxy or firewall) as it's not ideal to ask your users to add :3000 / :3443 when loading your wiki. However an option could be added to add the HTTPS port to the redirect URL, for this specific scenario.

deekerman commented

2026-02-20 18:03:51 -05:00

Author

Owner

@vincent-polite commented on GitHub (Mar 2, 2020):

That would be more than enough for my use case.

@vincent-polite commented on GitHub (Mar 2, 2020): That would be more than enough for my use case.

deekerman commented

2026-02-20 18:03:51 -05:00

Author

Owner

@BPowell76 commented on GitHub (Nov 16, 2024):

The current option to redirect to HTTPS from HTTP in the admin SSL settings causes an excessive redirect error that can (only) can be fixed by modifying the settings value directly in the database.

@BPowell76 commented on GitHub (Nov 16, 2024): The current option to redirect to HTTPS from HTTP in the admin SSL settings causes an excessive redirect error that can (only) can be fixed by modifying the settings value directly in the database.