SSL on default site

[dam57950]

trafficstars

Hello, I would like tu use ssl certificate when trying to access unknow host.

I'm using safari so after getting the https one time, it always want to redirect http to https and when trying to access to unknown host error page, it can't connect because of the lack of certificate.

Thanks for all you work!

[ItsEcholot]

This would be especially useful, since nginx-proxy-manager supports (yay) letsencrypt wildcard certificates.

[mriksman]

+1. Very strange that we can't set the default page up like we set up a Proxy Host (Force SSL, set certificates etc).

[benjaminchodroff]

Hitting this too, +1. Would love a feature to support a default site for https that allows a wildcard SSL certificate to be used to show a generic error page/redirect.

[user01010111]

+1 here -- I think this should be an option.

[inthebrilliantblue]

+1 here. SSL on default anything in the default site settings is horribly broken.

[alakhpc]

+1 again, would be really useful

[manfred-warta]

Hello, in fact the default site is not able to answer with different certificates anyway you can use a nice workaround:

Just configure a Redirection Host with a wildcard domain name eg. *.mydomain.xy and do a 307 temporary redirect to you forward domain. On the SSL tab you can specify your prefered certificate.

If you host multiple domains with your NPM just do this for each domain and you are done.

Hope that helped a bit.

[github-actions[bot]]

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

[gausie]

Please keep it open!

On Thu, 23 May 2024 at 02:50, github-actions[bot] @.***> wrote:

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

— Reply to this email directly, view it on GitHub https://github.com/NginxProxyManager/nginx-proxy-manager/issues/422#issuecomment-2126046363, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABL4LTUBPLMYXWTYSM4WHTZDVDOVAVCNFSM4NJENUY2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJSGYYDINRTGYZQ . You are receiving this because you are subscribed to this thread.Message ID: @.*** com>

[BrammyS]

+1

[mrbaloghakos]

Set up a 404 Host for *.yourdomain.com, then set the SSL certs as you like (I'm using my cert wildcard, and force SSL). Now if I hit a non existent subdomain, then it will show the ususal 404 page with SSL. All the existing subdomains (eg nas.mydomain.com) will still work as before, this only affects non existing subdomains.

You can't set a nice custom 404 page this way, but at least you can have SSL on your 404 page.