Connectivity to Azure PostgreSQL

[hildebolt]

Abruptly yesterday afternoon, my connections to PostgreSQL stopped working. It now says "We couldn't authenticate with the credentials provided. Please try again". No issue with the details that I provided though as they continue to work in pgAdmin.  When I re-enter the credentials, I get the message:

"Encryption Support
We were unable to connect to the data source using an encrypted connection. To access this data source using an unencrypted connection, click OK". 

If I click OK, it just takes me back to the "We couldn't authenticate with the credentials provided" screen.

[Anonymous]

Hi  @hildebolt 

We have seen on the internal platform that other engineers have reported this issue and submitted it. 

The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient!

The current solution is to roll back PBI Desktop to a previous version, first ensuring proper connection and use of Azure PostgreSQL .

Best Regards,
Community Support Team _ Ailsa Tao

[JHSh]

I have got the same problem since last week. Looking forward to the solution. Connection through gateway and automatic updates are OK so far, so I have a workaround by downloading actual data in pbix file from PowerBI service. Anyway this issue complicates my reporting workflow.

[hildebolt]

Hi @Anonymous ,

thanks a lot for the response. 

Unfortunately my company won't revert to an older version for security reasons. Do you know if there is any update on this issue as it has been a week and I am currently not able to update any of my reports or connect to any of our key databases. 

[testtest12]

 Hi @Anonymous  Do you know if there is any update on this issue?

[HollyA]

@testtest12  I've managed to get mine running today, so I think they've pushed a fix. Worth checking!

[hildebolt]

@HollyA yep, looks like its back up and running!

[aharms26295]

@Anonymous I am still seeing this issue in the Oct desktop version but not when I downgrade to the September version. The more concerning issue is I get the issue in the online service regardless of which desktop version I am in. We are also in a GCC enviroment so this may cause an additional layer of when/how these patches are pushed out.