starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-28 10:55:54 +03:00

[GH-ISSUE #1214] wildcard redirect http to https #990

New issue

Closed

opened 2026-02-26 06:35:20 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 06:35:20 +03:00

Owner

Originally created by @AznRaven on GitHub (Jul 1, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1214

Feature Request

I have a synology nas that will handle all the ssl certs. but it's not redirecting http to https

Is NPM able to redirect all http traffic to https? Right now, I'm redirecting 1 source to 1 destination in the Redirection Hosts and it works.

http --> a.domain.com --> 301 --> https --> a.domain.com
http --> b.domain.com --> 301 --> https --> b.domain.com

But what I want is a single redirect command that will redirect all
http --> *.domain.com --> 301 --> https --> *.domain

Is your feature request related to a problem? Please describe.
When you have 10-20 dockers that need http to https redirection. it can be a pain doing it 1 by 1 for each redirect.

Describe the solution you'd like
A wildcard redirect would be awesome. 1 redirect command to redirect all http traffic to https.

Describe alternatives you've considered
I've thought about using the regular nginx and changing the block code.

server {
	listen 80 default_server;
	listen [::]:80 default_server;
	server_name _;
	return 301 https://$host$request_uri;
}

But I prefer the Nginx Proxy Manager GUI.

Additional context
Maybe if you allow block code in Nginx Proxy Manager for advanced users. That would solve a lot of problems.
Being able to edit server blocks will help more advanced users to fine tune their setup.

Originally created by @AznRaven on GitHub (Jul 1, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1214 Feature Request I have a synology nas that will handle all the ssl certs. but it's not redirecting http to https Is NPM able to redirect all http traffic to https? Right now, I'm redirecting 1 source to 1 destination in the Redirection Hosts and it works. ``` http --> a.domain.com --> 301 --> https --> a.domain.com http --> b.domain.com --> 301 --> https --> b.domain.com ``` But what I want is a single redirect command that will redirect all `http --> *.domain.com --> 301 --> https --> *.domain` **Is your feature request related to a problem? Please describe.** When you have 10-20 dockers that need http to https redirection. it can be a pain doing it 1 by 1 for each redirect. **Describe the solution you'd like** A wildcard redirect would be awesome. 1 redirect command to redirect all http traffic to https. **Describe alternatives you've considered** I've thought about using the regular nginx and changing the block code. ``` server { listen 80 default_server; listen [::]:80 default_server; server_name _; return 301 https://$host$request_uri; } ``` But I prefer the Nginx Proxy Manager GUI. **Additional context** Maybe if you allow block code in Nginx Proxy Manager for advanced users. That would solve a lot of problems. Being able to edit server blocks will help more advanced users to fine tune their setup.

kerem

2026-02-26 06:35:20 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@mrfy commented on GitHub (Jan 14, 2022):

Hi @AznRaven , how did you redirect it from NPM?
Thanks

@mrfy commented on GitHub (Jan 14, 2022): Hi @AznRaven , how did you redirect it from NPM? ![image](https://user-images.githubusercontent.com/22953614/149535825-8514d39c-2009-4b13-b8e6-c373fbb64238.png) Thanks

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@zierbeek commented on GitHub (Mar 4, 2022):

how should this be used? I'm having this issue with all of my services not getting automatically redirect to https

@zierbeek commented on GitHub (Mar 4, 2022): how should this be used? I'm having this issue with all of my services not getting automatically redirect to https

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@srvoets commented on GitHub (Mar 11, 2022):

how should this be used? I'm having this issue with all of my services not getting automatically redirect to https

same

@srvoets commented on GitHub (Mar 11, 2022): > how should this be used? I'm having this issue with all of my services not getting automatically redirect to https same

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@tingjie02 commented on GitHub (Apr 5, 2022):

just tick Force SSL

@tingjie02 commented on GitHub (Apr 5, 2022): just tick Force SSL

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@plusdove commented on GitHub (Oct 31, 2022):

tick Force SSL not work, how should this be used? I'm having this issue with all of my services not getting automatically redirect to https, always show 400 bad request

@plusdove commented on GitHub (Oct 31, 2022): tick Force SSL not work, how should this be used? I'm having this issue with all of my services not getting automatically redirect to https, always show 400 bad request

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@tomlawesome commented on GitHub (Nov 7, 2022):

just tick Force SSL

This doesn't work. SSL is not in fact forced.

@tomlawesome commented on GitHub (Nov 7, 2022): > just tick Force SSL This doesn't work. SSL is not in fact forced.

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@Qifcn commented on GitHub (Feb 10, 2023):

error_page 497 301 =307 https://$host:4443$request_uri;
注意空格 4443改成你自己的端口

@Qifcn commented on GitHub (Feb 10, 2023): ![image](https://user-images.githubusercontent.com/34029055/218045013-018e4d0b-b0c1-4a3f-8fcc-19a681e42717.png) ` error_page 497 301 =307 https://$host:4443$request_uri; ` 注意空格 4443改成你自己的端口 ![image](https://user-images.githubusercontent.com/34029055/218045348-1bbda1de-5ef7-4035-82d8-2506d3540b66.png)

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

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

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

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

kerem commented

2026-02-26 06:35:20 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 21, 2025):

Issue was closed due to inactivity.

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

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

No description provided.

Rows
Columns