Every few weeks, Looker Studio loses access to our Microsoft Azure PostrgreSQL database with the following error:
This alone is pretty concerning, but today I cannot reconnect the PostgreSQL connection at all.
Last time I solved the SSL issue by going to the link provided in Microsoft Azure to download certificates. Specifically linking to the article titled: “Secure connectivity with TLS and SSL in Azure Database for PostgreSQL - Flexible Server”
That time I converted the “Microsoft RSA Root Certificate Authority 2017.crt” to a pem using the instruction on that article, and used the pem as a “PostrgreSQL SSL Configuration File” after enabling SSL.
Today, I have tried that again, even with a redownloaded file to ensure that the certification hasn’t changed, and it does not work. I have tried the other certificates as well and they do not work. A similar issue can be seen in this conversation: https://www.googlecloudcommunity.com/gc/Looker-Studio/Azure-Postgres-connection-issue-from-Looker-Studio/m-p/798345 None of the solutions there work. I have even tried downloading the “DigiCertGlobalRootCA.crt.pem” directly from DigiCert, even though the cert should not have changed.
As a result, I have 3 main questions:
- How can I properly connect Looker Studio to a Microsoft Azure PostgreSQL instance, which only allows SSL connections?
- How can I avoid having to reconnect every few weeks?
- Is this a known bug?