Skip to main content
Question

Unable to connect Postgres on Azure to Zap due to authentication error

  • March 6, 2025
  • 4 replies
  • 74 views

Hello….  I have PostgresSQL Database running on Azure.    I call myself following the steps to add the IP address to the firewall as the instructions state 54.86.9.50.   I’m getting the error authentication file:AppVersion using SQL Zero require static-ip pool types.   1. Make sure you click “Allow” or “Accept” on the permission group 2) double check your account has the correct permissions. 3. check out our help docs for information.

 

So I have no problem connecting from pgadmin 4.   I’m providing the Azure connection name,  Port 5432, I provided the correct database name, left the default schema, provided the same username I am using for pgadmin4, and same password.  I don’t include any other settings for the SSL blocks.  All help would be greatly appreciated, I cannot figure it out unfortunately. 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 9751 replies
  • March 7, 2025

Hi ​@Billy-SOR. Welcome to the Community! 🎉

I did some digging and found a note on our Can't connect to my database guide which mentions that for PostgreSQL you’ll also need to configure the server the accept logins from remote IP addresses AND create a user just for Zapier’s use:

40f43b450252067b6f1c609714c78964.png

Can you give that a try and let me know if that then allows you to connect successfully?


  • Author
  • Beginner
  • 2 replies
  • March 8, 2025

No this doesn’t work with Azure...


  • Author
  • Beginner
  • 2 replies
  • March 9, 2025

That doesn’t work


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 9751 replies
  • March 14, 2025

Sorry to hear that, ​@Billy-SOR—appreciate you giving that a try! In that case I’d suggest reaching out to our Support team to investigate further. They’ll be able to dig into the logs to get a better idea of what might be causing the trouble here.

Keen to ensure this gets sorted so please keep us in the loop on how you get on with them!