is there a test server without rate limits we can use to test our implementation?
acme-staging.api.letsencrypt.org imposes no rate limits.
We received the following message:
Max retries exceeded with url: /directory
Is that not a rate limit error?
Seems it was a fluke, we retried and it worked. Thanks!
I guess there still are rate limits, but they’re so high that I didn’t run into any yet.
@jhass I am running into similar issue. wonder how to overcome this. any thoughts?
nginx_1 | Waiting for folder /etc/letsencrypt/live/bo.caminofinancial.net to exist
letsencrypt_1 | 2016-03-22 21:58:29,441:INFO:letsencrypt.cli:Saving debug log to /var/log/letsencrypt/letsencrypt.log
letsencrypt_1 | 2016-03-22 21:58:29,756:INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
letsencrypt_1 | An unexpected error occurred:
letsencrypt_1 | ConnectionError: HTTPSConnectionPool(host=‘acme-staging.api.letsencrypt.org’, port=443): Max retries exceeded with url: /directory (Caused by NewConnectionError(’<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f37a5fd02d0>: Failed to establish a new connection: [Errno -2] Name or service not known’,))