{
  "is": "issue",
  "title": "Let's Encrypt rate limit for opalstacked.com subdomains",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - We\u0026rsquo;ve made some changes to the way Let\u0026rsquo;s Encrypt works with the shared opalstacked.com domain and as a result the domain is no longer rate-limited. We\u0026rsquo;ll be posting updated documentation with the details later this week. \n  \u003cspan class=\"faded\"\u003e(19:34 UTC — Nov 3)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - Looks like we\u0026rsquo;ve hit our new limit, we\u0026rsquo;ll get this corrected ASAP. \n  \u003cspan class=\"faded\"\u003e(20:56 UTC — Oct 27)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - We\u0026rsquo;ve confirmed that our increased rate limits are in effect, Calling this fixed, thanks for your patience :-) \n  \u003cspan class=\"faded\"\u003e(16:36 UTC — Oct 25)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - The LE service has increased our limit and at this time we are not seeing any rate-limiting for new LE certificates and renewals on any domains. We\u0026rsquo;ll continue to monitor. \n  \u003cspan class=\"faded\"\u003e(16:03 UTC — Oct 24)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eAt this time the Let\u0026rsquo;s Encrypt service is rate-limiting certificate issue and renewal requests for the entire *.opalstacked.com domain. This is the domain that we use to provide free subdomains to our hosting customers.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;re working with the LE team to get a higher limit. In the meantime if you are attempting to issue a LE cert for a site that uses your opalstacked.com subdomain then it may fail. If this happens you\u0026rsquo;ll receive a failure notice via email.\u003c/p\u003e\n\u003cp\u003eUntil the rate limit is raised then the alternative is to use one of your own registered domains on your site instead of your opalstacked.com subdomain. If you\u0026rsquo;re not ready to point your domain at Opalstack, then you can create a testing subdomain and A record via your NS provider to point that subdomain at your Opalstack server.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;ll update this issue as soon as the rate limit has been raised. \n  \u003cspan class=\"faded\"\u003e(17:40 UTC — Oct 21)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2020-10-21 17:40:00 +0000 UTC",
  "lastMod": "2020-10-21 17:40:00 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2020-10-21-lets-encrypt-rate-limit-for-opalstackedcom-subdomains/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2020-11-03 19:34:59",
  "affected": ["Shared: Dallas (USA)", "Shared: Frankfurt (DE)", "Shared: Hong Kong (HK)", "Shared: Phoenix (USA)", "Shared: San Francisco (USA)", "Shared: Singapore (SG)", "Shared: Washington D.C. (USA)"],
  "filename": "2020-10-21-lets-encrypt-rate-limit-for-opalstackedcom-subdomains.md"
}