Fatal on ACME Client creation failure (#133) All checks were successful ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
- For production(*cough* Codeberg *cough*), it's important to not use mock certs. So fail right from the start if this is the case and not try to "handle it gracefully", as it would break production. - Resolves #131 CC @6543 Co-authored-by: Gusted <williamzijl7@hotmail.com> Reviewed-on: #133 Reviewed-by: 6543 <6543@obermui.de> Co-authored-by: Gusted <gusted@noreply.codeberg.org> Co-committed-by: Gusted <gusted@noreply.codeberg.org>
This commit is contained in:
parent b9e9f14209
commit bf9a08e1fd
1 changed files with 1 additions and 1 deletions
| @ -414,7 +414,7 @@ func SetupCertificates(mainDomainSuffix []byte, dnsProvider string, acmeConfig * | |||
| ||||
acmeClient, err = lego.NewClient(acmeConfig) | ||||
if err != nil { | ||||
log.Error().Err(err).Msg("Can't create ACME client, continuing with mock certs only") | ||||
log.Fatal().Err(err).Msg("Can't create ACME client, continuing with mock certs only") | ||||
} else { | ||||
err = acmeClient.Challenge.SetTLSALPN01Provider(AcmeTLSChallengeProvider{challengeCache}) | ||||
if err != nil { | ||||
| |
Loading…
Add table
Add a link
Reference in a new issue