certbot
Here are 321 public repositories matching this topic...
-
Updated
May 4, 2020 - Shell
As #103 showed, we should have clear instructions as to how to add a frontend application inside our NoDock environment.
-
Updated
May 2, 2020 - Python
-
Updated
Apr 28, 2020 - Shell
-
Updated
Apr 27, 2020
-
Updated
May 5, 2020 - Python
-
Updated
Apr 2, 2020 - Shell
-
Updated
Mar 23, 2020 - Shell
-
Updated
May 5, 2020 - Python
-
Updated
Apr 22, 2020 - Shell
-
Updated
Jul 12, 2019 - Dockerfile
-
Updated
Mar 9, 2020 - Python
-
Updated
Apr 12, 2020 - Shell
-
Updated
Jan 6, 2018 - Shell
-
Updated
Jan 20, 2019
-
Updated
Dec 12, 2019 - Python
May I suggest to add inn the documentation the exact command required for the renewal and also where "critical" information is stored to avoid deleting a required file. Even after RTFM, oe figures out how to proceed but it would nice to have explicit instructions in the README.
On a different topic, in instances were there is a complex configuration of name servers, the propagation of the CNAME
-
Updated
Jan 2, 2020 - Python
-
Updated
Jan 5, 2018 - Shell
-
Updated
Apr 1, 2019 - Dockerfile
-
Updated
Mar 20, 2020 - Go
-
Updated
Apr 2, 2020 - Python
-
Updated
Feb 9, 2018 - Shell
-
Updated
Sep 29, 2019 - Python
-
Updated
Mar 29, 2019 - Shell
-
Updated
May 4, 2020 - PHP
As originally reported by jsha, our current instructions for DNS plugins sends you in a bit of a loop:
- Visit https://certbot.eff.org/
- Select nginx, ubuntu 19.10 from the drop-downs.
- Click on "wildcard" tab
- Click on check if your DNS provider supports Certbot -> https://certbot.eff.org/docs/using.html#dns-plugins
- Click on Visit https://certbot.eff.org to learn the best w
Improve this page
Add a description, image, and links to the certbot topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the certbot topic, visit your repo's landing page and select "manage topics."
In the past we've talked about trying to keep the list of systems we test on relatively current I still think there's some value in that.
If the tests don't immediately work, especially due to failures in certbot-auto, I think it probably makes sense to close/kick this issue until we've done some combination of deprecate certbot-auto and rewrite the test farm tests.