Dhiraj
09/21/2023, 9:20 AMFailed to submit flow run '***' to infrastructure.
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/urllib3/util/ssl_.py", line 402, in ssl_wrap_socket
context.load_verify_locations(ca_certs, ca_cert_dir, ca_cert_data)
ssl.SSLError: [X509: NO_CERTIFICATE_OR_CRL_FOUND] no certificate or crl found (_ssl.c:4154)
Marvin
09/21/2023, 9:20 AMPYTHONHTTPSVERIFY=0
to disable SSL verification. However, this isn't a recommended practice for production environments.
2. Providing the certificate in higher environments via Prefect YAML: You can provide the path to your certificate file in the Prefect configuration. Here's an example of how you might do it:
yaml
context:
secrets:
SSL_CERT_FILE: /path/to/your/certificate.pem
Remember to replace /path/to/your/certificate.pem
with the actual path to your certificate file. This will set the SSL_CERT_FILE
environment variable for your Prefect environment, which Python uses to find the SSL certificate.
However, these are just educated guesses. Without more information, it's hard to provide a definitive solution. You might want to check if all necessary packages are installed in your container, as missing packages can sometimes cause this error. If you're using Prefect with AWS, for example, you might need to install the prefect-aws
package.
I hope this helps, or at least makes your day a little less bright.