PostgreSQL remote database not reached after publishing report

[Kenmare]

Hello there,

I have a problem with my report and the postgresql database (hosted on Kinsta). 
With Power BI Desktop no problem, the remote database is correctly reached, and all the indicators are displayed. 

After publishing it I'm not able to reach the database with the error :The PostgreSQL source doesn't support encrypted connections.

There are a lot of solutions available (gateways or others) but everythins seems to be OK in my report:

Connexion succesfull:

Database used in the report:

Connexion visible and available:

Authentification not crypted (this might be a problem and will be fixed later)

But the error is still present. 

Any idea?

Have a good day!

[Anonymous]

Hi @Kenmare ,

If you encounter the error “The PostgreSQL source doesn't support encrypted connections” for the PostgreSQL database in Power BI Service, but everything is fine in Power BI Desktop.
Please follow the steps below to troubleshoot:
1. Check the encryption settings of the PostgreSQL server.
Verify that the PostgreSQL server requires SSL (Secure Socket Layer) encrypted connections. If the server requires SSL, ensure that the connection configuration of Power BI matches the encryption settings of the PostgreSQL server.
If the server does not have encryption enabled, but the Power BI Service requires encryption by default, this will result in an error. 
2. Enable SSL settings in Power BI Desktop
Update the data source settings in Power BI Desktop to enable SSL:
Open Power BI Desktop and go to Data Source Settings.
Locate the PostgreSQL connection and click Edit Permissions.
Ensure that the SSL/TLS encryption settings are configured in the connection string (e.g. add Encrypt=True or Ssl Mode=Require).
After confirming that there are no errors, republish the report to the Power BI Service.
3. Modify the PostgreSQL Configuration (if allowed to disable SSL)
If you have access to the server configuration file for PostgreSQL and do not need to enforce encryption in the short term, you can temporarily disable SSL connections:
4. Check Firewall or Hosting Restrictions
Verify that the hosting provider enforces SSL encrypted connections.
If required, ensure that the IP address of the Power BI Service is allowed to access the PostgreSQL database by configuring firewall rules.

Hope it helps!

Best regards,
Community Support Team_ Tom Shen

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[Kenmare]

Thank you so much for these info. 

1. After a show ssl with psql on the PostgreSQL server the result is: off
2. I checked SSL settings in PBI Desktop the encryption is set to false:

If I set to true in PBI Desktop I have an error that the datasource can't connect with an encrypted connexion (which is relevant if ssl is set to false on the server)

What looks strange is that ssl is off, data source not encrypted on PBI Desktop (and works well) but PBI service try an encrypted connexion after the rapport been published.

Maybe should I try to add Encrypt=False in the connection string but I don't know where to put it. 

[Kenmare · Accepted solution]

Well I finally found a solution:

1. Host the database with a new provider and, the most important, ssl on
2. Keep crypted connection in the data source in PBI Desktop
3. Create ODBC connection like in this article (https://dataintoresults.com/post/powerbi-and-postgresql-ssl-lets-encrypt-and-gateway/ ) but no need to install npgsql or download ODBC (windows 11 has now ODBC manager)
4. Use this connection with odbc connector in PBI (PostgreSQL connector still not working with this remote database)
5. Both tests in PBI Desktop and PBI service are OK!