Not able to issue certificates from roipost.com. Certificates working for roipost.org

We are setting up a docker machine in AWS with an nginx reverse proxy and let’s encrypt for the https.
After a few trial-error, we finally achieved the certs for our testing domain roipost.org (app.roipost.org, api.roipost.org, test.roipost.org & stageapi.roipost.org).
Now we are trying to implement the same in roipost.com, but apparently, as we already did some tests on this domain some days before, we already reached the rate limit (we actually don’t know for sure).

We followed the exact same steps with both domains, working for roipost.org but not for roipost.com. Are we in some blacklist/rate limit list or something? Can we try again now that the system is working as it should (theoretically)?

Thank you!

Hi @alomsimoy,

There are several different rate limits. Depending on what client software you used, it should have told you which rate limit you encountered.

https://letsencrypt.org/docs/rate-limits/

If you’re not sure, please let us know what the error message from the client is.

Hi @schoen,

I’m using jrcs/letsencrypt-nginx-proxy-companion docker image. The error given is:

Creating/renewal api.roipost.com certificates... (api.roipost.com)
2017-07-10 08:33:15,787:INFO:simp_le:1213: Generating new account key
/app/letsencrypt_service: line 51: 70 Killed /usr/bin/simp_le -f account_key.json -f key.pem -f chain.pem -f fullchain.pem -f cert.pem --tos_sha256 $ACME_TOS_HASH $params_d_str --cert_key_size=$cert_keysize --email "${!email_varname}" --server=$acme_ca_uri --default_root /usr/share/nginx/html/

(In every domain)

I think it's linked to that bug: SEGFAULT making HTTPS connection on seccomp docker · Issue #228 · nginx-proxy/acme-companion · GitHub

There is probably no problem on the Let's Encrypt side, and if there is, that program should have display it, not crash :slight_smile:

Hi @tdelmas,
Solved this part using another docker image. Now we have a rate limit error:

Creating/renewal test.roipost.com certificates... (test.roipost.com)
2017-07-10 10:42:20,863:INFO:simp_le:1211: Generating new account key
2017-07-10 10:42:27,102:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1):     acme-v01.api.letsencrypt.org
ACME server returned an error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new registration :: too many registrations for this IP
Debugging tips: -v improves output verbosity. Help is available under --help.

Maybe the previous bug did create more that 10 auth. If you wait one day it should be fine...

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