### Author:  [@etiennedi](https://forum.weaviate.io/u/etiennedi)
#### Post date: [August 22, 2024, 6:28am UTC](https://forum.weaviate.io/t/ssl-verification-failure/3428/2 "2024-08-22T06:28:02Z")
Hi @Khorppun_Sontipanya
Thanks for the report. Let me see what we can do to help you.
One question up front – since you mentioned the `connect_to_wcs` method – is this a paid cluster or a free sandbox? If it’s a paid cluster you’re also eligible to contact [support@weaviate.io](mailto:support@weaviate.io) – which may lead to faster responses. But also if it’s a free cluster, we’re happy to help you on a best effort basis right here.
Off the top of my head I can see potential causes:
1. There could be some sort of a global SSL issue with Weaviate Cloud. I have already pinged the correct folks to investigate if this is the cause.
2. It could be that something is off with your configuration and the error is an unfortunate error message obscuring the true error.
We’ll get back to you shortly!
-Etienne
---
### Author:  [@pauldegrijp](https://forum.weaviate.io/u/pauldegrijp)
#### Post date: [August 22, 2024, 7:33am UTC](https://forum.weaviate.io/t/ssl-verification-failure/3428/3 "2024-08-22T07:33:21Z")
Hi @Khorppun_Sontipanya
We have investigated Weaviate Cloud, but we do not see any SSL issues. We would like to help you resolve this as soon as possible. Could you please share the endpoint of the Weaviate Cluster you are using you are experiencing the issue with and send it to [support@weaviate.io](mailto:support@weaviate.io)? Thank you.
---
### Author:  [@Khorppun\_Sontipanya](https://forum.weaviate.io/u/Khorppun_Sontipanya)
#### Post date: [August 22, 2024, 9:58am UTC](https://forum.weaviate.io/t/ssl-verification-failure/3428/4 "2024-08-22T09:58:19Z")
This is my endpoint :
‘[https://s9qiyurarzso9rrjklwfda.c0.us-central1.gcp.weaviate.cloud](https://s9qiyurarzso9rrjklwfda.c0.us-central1.gcp.weaviate.cloud)’
Now, I try to use free sandbox.
This issue just recently occurred, I never had this issue before. it had never happened before. It only started happening the other day. Could it be related to a Windows update? Because after the Windows update, this problem started. However, some of my friends also have this problem, while others don’t when running the same code as I do.
Thank you for your support.
---
### Author:  [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [August 22, 2024, 1:45pm UTC](https://forum.weaviate.io/t/ssl-verification-failure/3428/5 "2024-08-22T13:45:03Z")
hi @Khorppun_Sontipanya !
What is the client version you are using?
you can get that information with:
```python
import weaviate
print(weaviate. __version__ )
```
Thanks!
---
### Author:  [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [August 23, 2024, 1:27pm UTC](https://forum.weaviate.io/t/ssl-verification-failure/3428/6 "2024-08-23T13:27:43Z")
hi @Khorppun_Sontipanya !!
Can you check if you have this library in your python environment?
`pip freeze | grep certifi`
if you don’t, please, install it:
`pip install -U certifi`
---
### Author:  [@Khorppun\_Sontipanya](https://forum.weaviate.io/u/Khorppun_Sontipanya)
#### Post date: [August 27, 2024, 4:18pm UTC](https://forum.weaviate.io/t/ssl-verification-failure/3428/7 "2024-08-27T16:18:01Z")
I checked the version of Weaviate; it is currently version 4.7.1.
And I also have ‘certifi’ in the Python environment, and I’ve already upgraded ‘certifi’.
Thank you very much for the effort to help.
---
### Author:  [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [August 27, 2024, 6:03pm UTC](https://forum.weaviate.io/t/ssl-verification-failure/3428/8 "2024-08-27T18:03:41Z")
hi @Khorppun_Sontipanya !!
Are you behind a corporate network by any chance?
We have identified some situations where, under this condition, it can affect the client connection.
We are working on a PR to with a workaround here:
>
>
> Initial work.
> Still need to figure:
> \- a way to pass disable\_ssl\_verification… to aopen in \_\_batch\_send method of \_BatchBase class.
> \- Write some tests or at least check if the httpx client was initiated with the correct verify parameter
>
> The idea is to print this message on exception with CERTIFICATE\_VERIFY\_FAILED
>
> We have identified a SSL CERTIFICATE\_VERIFY\_FAILED error.
>
> This error could be due to one of several reasons:
> - Weaviate client is under a corporate network that terminates ssl and issues it's own certificates.
> - You have a self signed certificate
>
> Weaviate python client uses certifi, and because of that, it will not be able to trust
> Potential fixes:
> - disable ssl verification by setting using \`disable\_ssl\_verification=True\` in client initialization
> - note that Weaviate will trust any certificate
> - Replace certifi cacert with the same cacert that is issued by your corporate network.
> - for example: cat MyCompanyRootCA.pem \>\> $(python -m certifi)
>
> To test this, you can rename the cacert.pem inside certifi package, like so:
>
> \`\`\`python
> import certifi
> right\_path = certifi.where()
> wrong\_path = right\_path + "renamed"
>
> import os
> os.rename(right\_path, wrong\_path)
> \`\`\`
To check if this is your situation, you access your cluster url with chrome, and do the following:
click the button at the left side of the url. click at `Connection is secure`:
and finally at `Certificate is valid`
this is the information you should see (of course, some details may change due to the AZ your cluster is at):
If you see anything other than **Issued By “Google Trust Services”** , you probably have a networking configuration that is terminating your SSL in between the client and server.
In this scenario, the CA CERT provided by certifi will not trust that issuer.
As a workaround you can replace certifi’s cacert.pm with the one you have.
you can find where this file is located issuing the following command:
```shell
python -m certifi
```
Let me know if this helps!
Thanks