-
Notifications
You must be signed in to change notification settings - Fork 9
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
Certificate issue when using reverse proxy (traefik) with let's encrypt #9
Comments
Per default there is a self-signed certificate generated and used in the container. Self-signed certificates are usually not accepted automatically by other components (e.g. Traefik, Apache or even browsers (you have to explicitly accept them). I use Apache as reverse proxy and have to set explicitly From my point of view you have 3 options to solve your problem:
|
Yes, I've got it running on port 80. I was hoping it would be possible to make the certificate configuration section more modular, so that certificate paths are not hard-coded you could still activate ssl for people using other proxy solutions. I'm guessing if apache just had mod_ssl but everything else could remain open, maybe that would work? |
Sorry but I am unsure if I got your proposal right. I did investigate a bit about possible Traefik settings. Currently traefik is not possible to handle self-signed certificates of backends. Currently there is an open issue concerning this topic TLS client auth to backends #3038. There might be an option to use The 3rd proposal works with traefik as you stated. Fine. Now about making certificate section more configurable: That is why I do not exactly understand what you mean with a more modular configuration section.
Please be so kind to be more precise what should be changed. |
Since there have to be no further discussions and no actions could be derived the issue will be closed. |
Hi there.
Thank you for this docker image. I'm having ssl certificate issues when trying to launch behind traefik proxy with autogenerated certificate from let's encrypt. I suspect this has something to do with ssl certificate being specified in your build. Any ideas?
The text was updated successfully, but these errors were encountered: