Hey there! We're running a dry run to check to ensure success: 021-01-26 01:24:37,931:DEBUG:acme.client:Storing nonce: 0004hkOOGUgEz6LtWjcc6H_CErBtC8t8TM_W02nzNN9uEOk 2021-01-26 01:24:37,931:DEBUG:acme.client:JWS payload: b'{\n "identifiers": [\n {\n "type": "dns",\n "value": " spud…

This might be related to the recent database maintenance on the staging server (but maybe not). if you get this error consistently, it might be worth ditching your staging account: certbot unregister --staging and try the dry-run again.

Staging API returning 500 errors

Help

system Closed February 25, 2021, 5:52am 4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Staging API responds with 500 internal server error Help	4	1011	August 8, 2019
Is the ACME v2 server working? Help	12	3508	January 4, 2020
400 Responses from /acme/new-order endpoint in staging Help	7	1024	April 11, 2020
Staging Env Down? Help	4	1237	July 18, 2019
Is the ACME v2 staging server working? Help	8	2329	March 12, 2018

Staging API returning 500 errors

Related topics