# Validation error **URL:** \ **Category:** Help\ **Created:** [May 19, 2017, 6:48am UTC](https://community.letsencrypt.org/t/validation-error/34339 "2017-05-19T06:48:48Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![dsidata](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@dsidata](https://community.letsencrypt.org/u/dsidata)\ **Post date:** [May 19, 2017, 6:48am UTC](https://community.letsencrypt.org/t/validation-error/34339/1 "2017-05-19T06:48:48Z")
Hello, I have tested few domains with Let’s encrypt configured on [www.ssllabs.com/ssltest](http://www.ssllabs.com/ssltest). All of them report error: _Revocation status:_ \_Validation error \_ _OCSP ERROR: Exception: Read timed out [[http://ocsp.int-x3.letsencrypt.org/](http://ocsp.int-x3.letsencrypt.org/)]_ Is there some problem with OCSP server? ---
**Author:** ![fskale](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fskale/32/11003_2.png) [@fskale](https://community.letsencrypt.org/u/fskale)\ **Post date:** [May 19, 2017, 6:55am UTC](https://community.letsencrypt.org/t/validation-error/34339/2 "2017-05-19T06:55:23Z")
Hi, check the index site here. > **[Let's Encrypt Community Support](https://community.letsencrypt.org/)** > > Let's Encrypt Community Support Service disruption ! Rgds. ---
**Author:** ![abc](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/abc/32/13561_2.png) [@abc](https://community.letsencrypt.org/u/abc)\ **Post date:** [May 19, 2017, 6:55am UTC](https://community.letsencrypt.org/t/validation-error/34339/3 "2017-05-19T06:55:28Z")
Hello, I am having problems with cert generation too, see [https://letsencrypt.status.io](https://letsencrypt.status.io) - it seems they’re occasionally online and then down again… my issue will be different to yours but it looks like a LetsEncrypt problem opposed to a client side one. Andrew ---
**Author:** ![lcv](https://avatars.discourse-cdn.com/v4/letter/l/a5b964/32.png) [@lcv](https://community.letsencrypt.org/u/lcv)\ **Post date:** [May 19, 2017, 6:57am UTC](https://community.letsencrypt.org/t/validation-error/34339/4 "2017-05-19T06:57:56Z")
Similar problem here. I can’t get [https://acme-v01.api.letsencrypt.org/directory](https://acme-v01.api.letsencrypt.org/directory) I receive this as a response: An error occurred while processing your request. Reference #97.5df01202.1495177010.29048906 ---
**Author:** ![nolimitdev](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@nolimitdev](https://community.letsencrypt.org/u/nolimitdev)\ **Post date:** [May 19, 2017, 8:52am UTC](https://community.letsencrypt.org/t/validation-error/34339/5 "2017-05-19T08:52:55Z")
On index site is just info about disruption of [acme-v01.api.letsencrypt.org](http://acme-v01.api.letsencrypt.org) for certificatie issuing. Status website [http://letsencrypt.status.io/](http://letsencrypt.status.io/) says that all ocsp servers are runing byt they are not - we also encounter errors: > Revocation information OCSP > OCSP: [http://ocsp.int-x3.letsencrypt.org/](http://ocsp.int-x3.letsencrypt.org/) > Revocation status Validation error > OCSP ERROR: Exception: Read timed out [[http://ocsp.int-x3.letsencrypt.org/](http://ocsp.int-x3.letsencrypt.org/)] Some browsers reports websites with lets encrypt certificates as unsecure with this error: > **Site not secure** > The following problem(s) were found: > (1) Unable to verify the website's identity (OCSP error) > (2) Online certificate validation (OCSP) for an element in the page failed ---
**Author:** ![fskale](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fskale/32/11003_2.png) [@fskale](https://community.letsencrypt.org/u/fskale)\ **Post date:** [May 19, 2017, 9:11am UTC](https://community.letsencrypt.org/t/validation-error/34339/6 "2017-05-19T09:11:53Z")
All working for me. Tested all OSCPs. Perhaps a browser problem ? What browser did you use to test ? Rgds. ---
**Author:** ![nolimitdev](https://avatars.discourse-cdn.com/v4/letter/n/dfb087/32.png) [@nolimitdev](https://community.letsencrypt.org/u/nolimitdev)\ **Post date:** [May 19, 2017, 9:30am UTC](https://community.letsencrypt.org/t/validation-error/34339/7 "2017-05-19T09:30:22Z")
I saw that error in older Opera 12.18. It seems to be strange that older browser is more sensitive than e.g. Chrome which does not report anything about unavailable OSCPs. Error still persists in Opera and also in SSL LAB - check the latest result (I clicked to clear cache) [SSL Server Test: community.letsencrypt.org (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html?d=community.letsencrypt.org&s=64.71.168.201&hideResults=on&latest) > **SSL Report: [community.letsencrypt.org](http://community.letsencrypt.org) (64.71.168.201)** > Revocation status Validation error > OCSP ERROR: Exception: Read timed out [[http://ocsp.int-x3.letsencrypt.org/](http://ocsp.int-x3.letsencrypt.org/)] ---
**Author:** ![Netsons](https://avatars.discourse-cdn.com/v4/letter/n/ecd19e/32.png) [@Netsons](https://community.letsencrypt.org/u/Netsons)\ **Post date:** [May 19, 2017, 9:58am UTC](https://community.letsencrypt.org/t/validation-error/34339/8 "2017-05-19T09:58:28Z")
Yes we received same issue. There are any news about ? ---
**Author:** ![fskale](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fskale/32/11003_2.png) [@fskale](https://community.letsencrypt.org/u/fskale)\ **Post date:** [May 19, 2017, 9:59am UTC](https://community.letsencrypt.org/t/validation-error/34339/9 "2017-05-19T09:59:36Z")
I see that, but using firefox latest with active OSCP validation it works. I’m located in europe. Perhaps a routing (BGP) issue ? ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [May 19, 2017, 2:16pm UTC](https://community.letsencrypt.org/t/validation-error/34339/10 "2017-05-19T14:16:17Z")
This error is a result of an ongoing service disruption. Please follow [status.letsencrypt.org](http://status.letsencrypt.org) for more information. We should have all of the remaining issues resolved shortly. In the meantime I’m going to lock this thread since there isn’t a need for further discussion on this particular error. Please open a new thread if you need to resume discussion. Thanks for your patience, we apologize for the disruption and I expect more detailed root cause information will be shared in the near future. ---
**Author:** ![cpu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cpu/32/84514_2.png) [@cpu](https://community.letsencrypt.org/u/cpu)\ **Post date:** [May 19, 2017, 2:16pm UTC](https://community.letsencrypt.org/t/validation-error/34339/11 "2017-05-19T14:16:20Z")
Closed on May 19, 2017, 2:16pm UTC