-
-
Notifications
You must be signed in to change notification settings - Fork 304
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update: make letsencrypt update more resiliant (2)
- Loading branch information
1 parent
55121d4
commit 6331ce5
Showing
2 changed files
with
11 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6331ce5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a quick question, why use the master from Github and not certbot, any special reason except having "the latest and the greatest"?
6331ce5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @enoch85 !
Well, this is the reason
https://help.nextcloud.com/t/ncp-raspbian-letsencrypt-support/45741
Needed to go back to the github version, which sucks :|
6331ce5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm yeah. Both the Nextcloud Snap and the Nextcloud VM runs Certbot and are also affected since they don't proved TLS-ALPN (yet), but at least the VM uses standalone as a first option. :-]