# Staging Env Down? **URL:** \ **Category:** Help\ **Created:** [June 18, 2019, 6:32pm UTC](https://community.letsencrypt.org/t/staging-env-down/96105 "2019-06-18T18:32:12Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![afagund](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@afagund](https://community.letsencrypt.org/u/afagund)\ **Post date:** [June 18, 2019, 6:32pm UTC](https://community.letsencrypt.org/t/staging-env-down/96105/1 "2019-06-18T18:32:12Z")
Hello, Is the staging env down right now? I am getting the following error while creating a new order. 2019-06-18 15:28:01,932:ERROR:certbot.log:The server experienced an internal error :: Error creating new order ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [June 18, 2019, 6:43pm UTC](https://community.letsencrypt.org/t/staging-env-down/96105/2 "2019-06-18T18:43:06Z")
Yes, it seems to be having an outage right now. A few hours ago there was some instability, so maybe it’s related. There’s some comment on it in [this thread](https://community.letsencrypt.org/t/dns-01-challgen-has-been-circulating-for-a-long-time-but-i-still-havent-been-able-to-achieve-it/96049/22) and [on the status site](https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/5d08f73f81cc0917c025b345). ---
**Author:** ![afagund](https://avatars.discourse-cdn.com/v4/letter/a/9d8465/32.png) [@afagund](https://community.letsencrypt.org/u/afagund)\ **Post date:** [June 18, 2019, 6:43pm UTC](https://community.letsencrypt.org/t/staging-env-down/96105/3 "2019-06-18T18:43:50Z")
Thanks for sharing that. The issue is still going on. Unfortunately status site is saying its operational, but in fact its not. Still error 500 while creating a new order at [https://acme-staging-v02.api.letsencrypt.org/acme/new-order](https://acme-staging-v02.api.letsencrypt.org/acme/new-order). Here is more details from logs: 2019-06-18 15:28:01,928:DEBUG:requests.packages.urllib3.connectionpool:“POST /acme/new-order HTTP/1.1” 500 114 2019-06-18 15:28:01,930:DEBUG:acme.client:Received response: HTTP 500 content-length: 114 cache-control: max-age=0, no-cache, no-store expires: Tue, 18 Jun 2019 18:28:50 GMT server: nginx connection: close link: [https://acme-staging-v02.api.letsencrypt.org/directory](https://acme-staging-v02.api.letsencrypt.org/directory);rel=“index” pragma: no-cache boulder-requester: 6392885 date: Tue, 18 Jun 2019 18:28:50 GMT content-type: application/problem+json replay-nonce: VsjpsjH489ZLOMYpm-qZa2di3VcWIq2gFGt52bEr3Ko { “type”: “urn:ietf:params:acme:error:serverInternal”, “detail”: “Error creating new order”, “status”: 500 } 2019-06-18 15:28:01,931:DEBUG:acme.client:Storing nonce: VsjpsjH489ZLOMYpm-qZa2di3VcWIq2gFGt52bEr3Ko 2019-06-18 15:28:01,931:DEBUG:certbot.log:Exiting abnormally: Traceback (most recent call last): File “/usr/bin/certbot”, line 9, in load\_entry\_point(‘certbot==0.25.1’, ‘console\_scripts’, ‘certbot’)() File “/usr/lib/python2.7/site-packages/certbot/main.py”, line 1323, in main return config.func(config, plugins) File “/usr/lib/python2.7/site-packages/certbot/main.py”, line 1213, in certonly lineage = \_get\_and\_save\_cert(le\_client, config, domains, certname, lineage) File “/usr/lib/python2.7/site-packages/certbot/main.py”, line 120, in \_get\_and\_save\_cert lineage = le\_client.obtain\_and\_enroll\_certificate(domains, certname) File “/usr/lib/python2.7/site-packages/certbot/client.py”, line 383, in obtain\_and\_enroll\_certificate cert, chain, key, \_ = self.obtain\_certificate(domains) File “/usr/lib/python2.7/site-packages/certbot/client.py”, line 326, in obtain\_certificate orderr = self.\_get\_order\_and\_authorizations(csr.data, self.config.allow\_subset\_of\_names) File “/usr/lib/python2.7/site-packages/certbot/client.py”, line 358, in \_get\_order\_and\_authorizations orderr = self.acme.new\_order(csr\_pem) File “/usr/lib/python2.7/site-packages/acme/client.py”, line 782, in new\_order return self.client.new\_order(csr\_pem) File “/usr/lib/python2.7/site-packages/acme/client.py”, line 608, in new\_order response = self.\_post(self.directory[‘newOrder’], order) File “/usr/lib/python2.7/site-packages/acme/client.py”, line 93, in \_post return self.net.post(\*args, \*\*kwargs) File “/usr/lib/python2.7/site-packages/acme/client.py”, line 1082, in post return self.\_post\_once(\*args, \*\*kwargs) File “/usr/lib/python2.7/site-packages/acme/client.py”, line 1096, in \_post\_once return self.\_check\_response(response, content\_type=content\_type) File “/usr/lib/python2.7/site-packages/acme/client.py”, line 956, in \_check\_response raise messages.Error.from\_json(jobj) Error: urn:ietf:params:acme:error:serverInternal :: The server experienced an internal error :: Error creating new order 2019-06-18 15:28:01,932:ERROR:certbot.log:An unexpected error occurred: 2019-06-18 15:28:01,932:ERROR:certbot.log:The server experienced an internal error :: Error creating new order ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [June 18, 2019, 6:53pm UTC](https://community.letsencrypt.org/t/staging-env-down/96105/4 "2019-06-18T18:53:44Z")
For what it's worth, I can create new orders. But note this comment from the other thread: > [@Dns-01 challenge has been circulating for a long time, but I still haven't been able to achieve it](https://community.letsencrypt.org/t/dns-01-challenge-has-been-circulating-for-a-long-time-but-i-still-havent-been-able-to-achieve-it/96049/22): > > accounts that created buggy orders during the outage period will continue to see some 500’s if they submit new order requests for matching names with the same ACME account. I recommend rotating the staging ACME account or waiting 7d for the pending orders to expire You could try: ``` certbot unregister --staging ``` and seeing whether a new ACME account suffers from the same issue. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [July 18, 2019, 6:53pm UTC](https://community.letsencrypt.org/t/staging-env-down/96105/5 "2019-07-18T18:53:44Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.