When logging into serverless, you must configure TLS. Refer to the official documentation to download the root certificate, and then add the ssl-ca parameter in the URI to specify the root certificate directory when creating the changefeed.
Yesterday there were no errors, but now it keeps reporting that it can’t find the directory or file after downloading the CA. It’s strange because it was working fine yesterday, and the directory and file do exist. I even gave it 777 permissions and configured the parameter ?ssl-ca=/data/app/tidb/ca-bundle.pem. It’s really weird.
This topic is about access permission issues, specifically not having sufficient permissions to access the specified database. To resolve the TLS handshake failure, the client lacks the root certificate and cannot verify the integrity and authenticity of the certificate chain. In this case, the certificate chain cannot be trusted, even if the client has the intermediate certificate. To establish a trusted TLS connection, the client needs to have the complete certificate chain, including the root certificate, intermediate certificates, and leaf certificates.
You checked the file on machine 02, but the error should be on machine 10.4. It seems like you checked the wrong machine. Check if the file exists on machine 10.4.
Thank you very much, it indeed works by copying it over. After exporting with dumpling and importing into the serverless TiDB cluster with loader, it asks to add a certificate. However, there is no parameter for adding a certificate in the loader’s parameters.
|
username: 天下无贼
|
username: 
|
username: 
|
username: 
|
username: 
|
username: