Archivovaná správa #1085 diskusnej skupiny ecs-isp@2rosenthals.com

Od:	"Steven Levine" <ecs-isp@2rosenthals.com>	Celá hlavi?ka Nedekódovaná správa
Hlavi?ka:	Re: [eCS-ISP] Getting started with Let's Encrypt
Dátum:	Tue, 10 Dec 2024 22:13:08 -0800
Komu:	"eCS ISP Mailing List" <ecs-isp@2rosenthals.com>

In <list-11332565@2rosenthals.com>, on 12/10/24 at 02:33 PM, "Peter Moylan" <ecs-isp@2rosenthals.com> said: Hi Peter, >Now the symptoms have changed: >{14}[c:\uacme] issue_pmoylan.org >uacme -v -h uacme-hook.cmd issue pmoylan.org www.pmoylan.org >mail.pmoylan.org >uacme.exe: version 1.2.4 starting on Tue, 10 Dec 2024 14:11:04 uacme.exe: >loading key from /@unixroot/etc/ssl/uacme/private/key.pem uacme.exe: >loading key from >/@unixroot/etc/ssl/uacme/private/pmoylan.org/key.pem >uacme.exe: checking existence and expiration of >/@unixroot/etc/ssl/uacme/pmoylan >.org/cert.pem >uacme.exe: /@unixroot/etc/ssl/uacme/pmoylan.org/cert.pem does not exist >uacme.exe: fetching directory at >https://acme-v02.api.letsencrypt.org/directory And what happens next? Do uacme.exe return to the command line or just hang waiting for something to happen? I don't have access to the full logs of a current certficate run, but perhaps the following will help you know what to expect. uacme.exe: version 1.2.4 starting on Tue, 22 Oct 2024 15:03:34 uacme.exe: loading key from f:\MPTN\ETC\ssl\uacme/private/key.pem uacme.exe: loading key from f:\MPTN\ETC\ssl\uacme/private/warpcave.com/key.pem uacme.exe: checking existence and expiration of f:\MPTN\ETC\ssl\uacme/warpcave.com/cert.pem One this system, uacme is looking in f:\mptn\etc because the libc pathrewriter is configured to /etc to %ETC. uacme.exe: f:\MPTN\ETC\ssl\uacme/warpcave.com/cert.pem does not exist Since the cert does not exist, uacme is going to attempt to create a new certificate. uacme.exe: fetching directory at https://acme-staging-v02.api.letsencrypt.org/directory So far we match. Since I was testing at the time, I chose to using a staging account. It has no effect on the overall process flow. However, since I mentioned it, you probably should review https://letsencrypt.org/docs/staging-environment/ Basically since a staging account is for testing and failure are expected, most of the Rate Limits are removed. uacme.exe: retrieving account at https://acme-staging-v02.api.letsencrypt.org/acme/new-acct Based on what you posted, it appears you hung before uacme logged this message. Is this true. The following log messages are typical. uacme.exe: account location: https://acme-staging-v02.api.letsencrypt.org/acme/acct/168253203 uacme.exe: creating new order for warpcave.com at https://acme-staging-v02.api.letsencrypt.org/acme/new-order uacme.exe: order URL: https://acme-staging-v02.api.letsencrypt.org/acme/order/168253203/19918221883 uacme.exe: retrieving authorization at https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/14546972603 uacme.exe: running uacme-hook.cmd begin dns-01 warpcave.com w_Rn_eenmWzh_J6-7y67gje0AuMMVwTKR8kLsE1zmag js-nPVQVZubIjZeC-AIEwSO12uE7768aft_B18dnWRg And here is the hook logging away... 2024/10/22-15:03:35 2024/10/22-15:03:35 uacme-hook started at 2024/10/22-15:03:35 2024/10/22-15:03:35 method is begin 2024/10/22-15:03:35 type is dns-01 2024/10/22-15:03:35 ident is warpcave.com 2024/10/22-15:03:35 token is w_Rn_eenmWzh_J6-7y67gje0AuMMVwTKR8kLsE1zmag 2024/10/22-15:03:35 auth is js-nPVQVZubIjZeC-AIEwSO12uE7768aft_B18dnWRg 2024/10/22-15:03:35 2024/10/22-15:03:35 Running on slamain in test mode Hope this helps, Steven -- ---------------------------------------------------------------------- "Steven Levine" <steve53@earthlink.net> Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------

Prihlási?: Nap??a?, Súhrn, Index.
Odhlási?
Mail na ListMastera