Telemetry Connection to PostgreSQL may be requiring SSL connection by default

So I’ve got telemetry setup to point to a telemetry server with a PostgreSQL database but whenever telemetry information is sent, I get an error that looks like a PostgresSQL error stating “SSL is not enabled on the server”. According to some information I read, it seems this occurs when the connection string in the code does not specify SSL requirement, that it defaults to requiring it.

So I found that it actually can be configured via the connection string, by reading the article I referenced more thoroughly, i found that by amending the server execution string to include ?sslmode=disable at the end after the database name, you can bypass the aforementioned error.

1 Like