https://bugs.contribs.org/show_bug.cgi?id=10595
Terry Fage <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--- Comment #51 from Terry Fage <[email protected]> ---
# config setprop letsencrypt API 1
and dont forget the
signal-event console-save
now goes to "https://acme-staging.api.letsencrypt.org/acme/challenge/
# config setprop letsencrypt API 2
"2 or none" none defaults to 2
https://acme-staging-v02.api.letsencrypt.org/acme/challenge
Seems OK..moving back to verified, just need another user to confirm behaviour
May just be my system and perhaps more locality DNS baulks, but an initial
dehydrated -c
[root@sme92x64 ~]# dehydrated -c
# INFO: Using main config file /etc/dehydrated/config
ERROR: Problem connecting to server (get for
https://acme-staging-v02.api.letsencrypt.org/directory; curl returned with 6)
run it again and away we go
[root@sme92x64 ~]# dehydrated -c
# INFO: Using main config file /etc/dehydrated/config
Processing sme92.vm.org
+ Signing domains...
+ Generating private key...
+ Generating signing request...
+ Requesting new certificate order from CA...
+ Received 1 authorizations URLs from the CA
+ Handling authorization for sme92.vm.org
+ 1 pending challenge(s)
+ Deploying challenge tokens...
+ Responding to challenge for sme92.vm.org authorization...
+ Cleaning challenge tokens...
---snip----
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
