SSL Certificate is failing to update

[ptaylor2]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: sbbs.dynu.net

I ran this command: ./jsexec letsyncrypt.js --force

It produced this output: Linux Unknown

My web server is (include version): Synchronet V4

The operating system my web server runs on is (include version): Linux

My hosting provider, if applicable, is: Cox.net

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

The script is not causing the issue ad several dozen Synchronet bbs round he world are using the same java script and its working fine.

./updatecert

JSexec v3.19a-Linux master/46b1f86f5 Debug - Execute Synchronet JavaScript Module
Compiled Nov 3 2021 19:35:59 with GCC 9.3.0

Loading configuration files from /sbbs/ctrl
JavaScript-C 1.8.5 2011-03-31
JavaScript: Creating runtime: 16777216 bytes

Reading script from /sbbs/repo/exec/letsyncrypt.js
/sbbs/repo/exec/letsyncrypt.js compiled in 0.00 seconds
!JavaScript /sbbs/exec/load/acmev2.js line 139: Error: newOrder responded with 429 not 201
/sbbs/repo/exec/letsyncrypt.js executed in 1.26 seconds
!Module (letsyncrypt.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

Returning error code: 1

[rg305]

Hi @ptaylor2 and welcome to the LE community forum

Please confirm the Internet IP used by your system, with:
curl -4 ifconfig.co

It should match the output of:
nslookup sbbs.dynu.net

If that is a match, why are you using "the --force" ?

[ptaylor2]

The nslookup on my domain is set and resolves with no issues. What limit are you setting on the server because if your using 3 then it needs to be iincreased to like 8. The letsencrupt script has few options to use.

[_az]

@ptaylor2

newOrder responded with 429 not 201

It looks like you are currently rate-limited from creating new certificate orders.

One of the ways this can happen is by repeatedly failing to request a certificate. If you ran this script 5 times in one hour and it failed each time, you will need to wait an hour before you can try again. Read more at Rate Limits - Let's Encrypt.

Hopefully if you try again later, you will get a different error message, which you can post.