# Cannot get new certificate, readtimeout error **URL:** \ **Category:** Help\ **Created:** [May 27, 2019, 7:01pm UTC](https://community.letsencrypt.org/t/cannot-get-new-certificate-readtimeout-error/94586 "2019-05-27T19:01:53Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [May 28, 2019, 9:06am UTC](https://community.letsencrypt.org/t/cannot-get-new-certificate-readtimeout-error/94586/10 "2019-05-28T09:06:50Z")
Your situation looks like one that I’ve seen occasionally from other users for a couple of years, where large POST requests (such as those containing a CSR) to the Akamai CDN in front of the Let’s Encrypt service, just time out. Unfortunately I don’t know of a permanent solution, but you can try verify whether it’s the case by trying a different IP address to access the API server. This can be done by modifying `/etc/hosts` with e.g.: ``` 104.99.248.78 acme-v02.api.letsencrypt.org ``` You can also try `104.107.50.145`. Keep in mind this isn’t a workable long-term workaround, since the IP addresses will change eventually. If neither of those work, you can also try lowering your network interface MTU. That worked for one person who suffered from this problem. ``` ifconfig eth0 mtu 1300 ``` --- _[View the full topic](https://community.letsencrypt.org/t/cannot-get-new-certificate-readtimeout-error/94586)._