# Creating cert is failing

**URL:** <https://community.letsencrypt.org/t/creating-cert-is-failing/67618>\
**Category:** Help\
**Created:** [July 25, 2018, 11:54am UTC](https://community.letsencrypt.org/t/creating-cert-is-failing/67618 "2018-07-25T11:54:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [July 25, 2018, 11:04pm UTC](https://community.letsencrypt.org/t/creating-cert-is-failing/67618/4 "2018-07-25T23:04:37Z")

</div>

Thanks. As an experiment, could you trying the same with this `/etc/hosts` entry?

```
104.92.230.170 acme-v01.api.letsencrypt.org

```

The thinking is that there is a history of some clients having problems with some Akamai edges when POSTing a large request body, which can be avoided by using an edge in a different region.

The following may also help diagnostically:

```
mtr -c 20 --no-dns acme-v01.api.letsencrypt.org --report
curl -v --data "$(dd if=/dev/urandom bs=32767 count=1 | base64)" -m 10 -H "Pragma: akamai-x-get-cache-key, akamai-x-get-true-cache-key, akamai-x-get-request-id, akamai-x--meta-trace, akamai-x-get-nonces, akamai-x-get-ssl-client-session-id" https://acme-v01.api.letsencrypt.org/acme/new-authz
```

---

_[View the full topic](https://community.letsencrypt.org/t/creating-cert-is-failing/67618)._