# Build against Let's Encrypt's Staging Environment **URL:** \ **Category:** Self-hosting\ **Tags:** unsupported-install\ **Created:** [July 12, 2022, 4:00pm UTC](https://meta.discourse.org/t/build-against-lets-encrypts-staging-environment/232645 "2022-07-12T16:00:14Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manuel/32/468169_2.png) [@manuel](https://meta.discourse.org/u/manuel)\ **Post date:** [July 12, 2022, 4:00pm UTC](https://meta.discourse.org/t/build-against-lets-encrypts-staging-environment/232645/1 "2022-07-12T16:00:15Z")
I recently hit the rate limit trying to spin up a multi-site setup on the stable branch. I found some suggestions on the forum how to work around that. Though I also found that Let’s Encrypt just recommends to build against their Staging Environment ([Staging Environment - Let's Encrypt](https://letsencrypt.org/docs/staging-environment/)). Could I do that by using a command flag or setting a different url? ---
**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\ **Post date:** [July 12, 2022, 4:41pm UTC](https://meta.discourse.org/t/build-against-lets-encrypts-staging-environment/232645/2 "2022-07-12T16:41:12Z")
There is no support for such configuration at the moment, as our launcher setup is tuned for standard installs. You can edit the LE template manually on your checked out version to point to staging though. ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [August 11, 2022, 4:41pm UTC](https://meta.discourse.org/t/build-against-lets-encrypts-staging-environment/232645/3 "2022-08-11T16:41:49Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.