-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Any way to add ssl on this? #68
Comments
traefik with mkcert could work. |
I'm going to try to adapt the method described here using certbot: |
And it works! Here are some particular changes I made: wp: You will notice that I made separate "certs" and a "private" folder in config The other issue where it shows what you need to add to docker-entrypoint.sh, you need to add ALL OF THE LINE, and not just the last one. Other than that, if you just follow the instructions on the page, you should have SSL working! |
thanks for this @palomnik this helpful. i am still struggling mightily, when i add this to my stack --edit-- |
ok, it get stranger... https://www.mydomain.com/wp-login.php now gives me access to the control panel (this is the external address that is a proxypass to http://docker01.myintdomain.com:8080) however when i try just https://www.mydomain.com to see my web site it thinks about it for a while and then i get a redirect to https://docker01.mydomain.com/ in the browser (which is a)an internal address and b) it missed the port so wont work). i am very confused, been at this for hours, all i want to do is publish a wordpress site behind an nginx reverse proxy this is what i changed, why would it ever be trying to connect to the internal DNS name? |
Would you be able to share the contents of the docker-entrypoint.sh? I haven't been able to copy it from the container.. |
Here it is:
|
@palomnik Thank you! |
There is a nice example with the use of certbot docker image, letsencrypt one |
Maybe you can test the https branch and provide some feedback 😉 |
hello, is there any way to ssl this on 443 port?
The text was updated successfully, but these errors were encountered: