-
Notifications
You must be signed in to change notification settings - Fork 62
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
Use Let’s Encrypt dns-01 challenge during self-hosted installation #74
Comments
I've been searching for the right command structure to modify the certbot section of run.sh. I'm trying various experiments using docker installed certbot but have not been successful. |
Hi there, it is possible to make it working with Cloudflare and DNS Challenge, I implemented this in my local network at home. I am thinking of a mechanism to include custom code in a separate file. I hope the Bitwarden developers consider this suggestion. Cheers! Alex |
Hi @Alextocode, maybe you could push your current code into a branch and we could work together on it. I need this feature, too, so as many others would benefit from this feature. If we can do this by calling an external script, the change to the run.sh would be minor and doesn't need further developement in the future. Plus, many other certbot plugins can be added as well. Hope this work will be appreciated and get merged sometime. So long! |
Hi @rawsmr Happy new year! Alex |
I may have missed it. But I can’t see in the code where one can specify dns-01 with a wait time for a Let’s Encrypt challenge on ./bitwarden install.
Self-hosters running in VMs behind proxies will have real issues using other, non pause-able LE challenges.
Without this capability one has to run certbot on the VM and arrange to have certs renewed, copied to ./bwdata/ssl and restart the nginx container on a cron schedule.
Not hard but not convenient.
The text was updated successfully, but these errors were encountered: