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
[Feature request] Custom SSL local path / file #87
Comments
This would be very helpful. I use a .net for my local network, so being able to use something such as acme.sh to generate a wildcard using a txt dns entry would be great and not have to copy the cert over manually. For reference: https://github.com/Neilpang/acme.sh |
I would also like this. Would be useful for wildcard certs i'm generating via a different container. |
I would also love this feature as this is the only thing preventing me from using this. I also use a different container to generate my certs (via DNS, not HTTP), which also handles automatically restarting any required containers when the certificate updates. |
Apologies for the ping, but can we get a comment on this, @jc21 ? |
There is a way to do this using the web interface. You can just turn off the SSL setting in the "proxy host" settings (set to none) and in the "Advanced"-tab you can set the ssl nginx manually using "Custom Nginx Configuration".
just copy and paste this for every "proxy host" you want to add. Not perfect or elegant, but it seems to work. P.S: to force ssl redirect add the line |
Damn this feature would be nice |
This feature would be amazing. Specially for non proxy host certificates since there is no advanced tab and therefore @christian-skjetne workaround does not work. |
Any updates on this one? I'm managing certbot separately and I'm provisioning all my services with certs via hooks. I'd like to see a "load cert from this path" option in npm... |
Does @christian-skjetne comment not help you? Should be ok for any http proxy route. Haven't tried this out yet, though. Really want to use NPM, but this is a feature I would like to have. But, I think this should work for now. |
Yes, it does solve the issue, but I do not like to have such workarounds. If I have to manage configuration manually, I prefer to keep it all manually and not use NPM at all. |
I see. I am in the same boat as well. I am just manually editing my conf files at this point. Really easy to use nginxconfig.io to provide for the base files. |
Apologies if this is an idiot question, but why does it not seem to work to stop the container, replace the |
Can anyone advise what Im doing wrong here? I add the config as specified and it gives me an offline error? Essentially breaks it |
@1liminal1
|
There's a simpler way to do this if all your Proxy Host need the same SSL config.
|
Great, thanks! I have also tested this with a single proxy host and it works - now I can update the SSL settings for the 40+ others for the last time! |
Is there any progress on this issue except the mentioned workaround? |
I had to declare absolute paths within the include lines. Otherwise the proxy hosts went offline: |
full path also fixed mine! Good find Thanks! |
Hi, I have my certificates accessible from the file system on the docker host so it would be great when adding a custom certificate that you could specify a local path instead of manually uploading the required files,
That way I could setup the container with e.g.:
And when adding a custom certificate I could enter e.g.
/ssl/my.cert
The text was updated successfully, but these errors were encountered: