This message was deleted.
# marvin-in-the-wild
s
This message was deleted.
m
To resolve the SSL error you're encountering when connecting an external PostgreSQL database with Prefect Server deployed via Helm, it appears you're facing a certificate verification issue. The Prefect documentation provides some information regarding TLS/SSL configuration that might help you: 1. Ensure that your PostgreSQL is properly configured to accept SSL connections and that you have the correct certificate file specified in your connection URL. 2. If the certificate is not part of your system bundle and you are in a secure environment where you can bypass certificate verification (for testing purposes only), you can set the
PREFECT_API_TLS_INSECURE_SKIP_VERIFY
to
True
to disable certificate verification. However, please be aware that disabling certificate validation is insecure and not recommended for production environments. For the connection string, you would typically use something like this (adapt with your credentials and host):
Copy code
DATABASE_CONNECTION_URL="<postgresql+asyncpg://postgres:yourPasswordHere@yourHostHere:5432/prefect>"
Link to relevant Prefect documentation for TLS settings Unfortunately, my search results did not bring specific guidance for configuring SSL for PostgreSQL when using the Prefect Server Helm chart, nor could I find any open issues on GitHub related to this specific SSL error with Prefect Server Helm. If none of the above helps and the issue persists, you may want to consider connecting with the Prefect community or opening a new GitHub issue to get further assistance tailored to your unique setup. Remember, always handle database credentials and connection strings with care to prevent unauthorized access.