Unable to connect to database

Dinesh Patturi 0 Reputation points
2025-12-02T08:22:33.5+00:00

Unable to connect the database-

Unavailable (Unplanned)

An unexpected problem is preventing restoring access to your Azure Database for PostgreSQL - Flexible server. We are working on resolving the problem.
User's image

Azure Database for PostgreSQL
{count} votes

1 answer

Sort by: Most helpful
  1. Manoj Kumar Boyini 1,250 Reputation points Microsoft External Staff Moderator
    2025-12-02T09:25:33.6666667+00:00

    Hi Dinesh Patturi,

    Thank you for reaching out to the Microsoft QA team. It looks like you're experiencing an unexpected issue preventing access to your Azure Database for PostgreSQL - Flexible server. Microsoft is already working on resolving this problem, but while you wait, there are a few troubleshooting steps you can take to diagnose the connectivity issue on your end.

    Here’s what you can try:

    1.Check Server Status: Go to the Azure portal and navigate to your PostgreSQL Flexible Server Overview page to confirm if the server status is "Ready". If it’s not, it may indicate an ongoing issue on Microsoft's side.

    2.Review Azure Service Health: Check the Azure Service Health dashboard for any regional outages or maintenance events that might be affecting your database.

    3.Validate Connection Information: Ensure your connection string is correct, including the Fully Qualified Domain Name (FQDN), database name, username, password, and SSL settings (e.g., sslmode=require).

    4.Perform Connectivity Tests:

    DNS Resolution: Use nslookup to check if your FQDN resolves correctly to a public or private IP as expected.

    Port Accessibility: Run a telnet <fqdn> 5432 command to see if the port is accessible from your network. If the connection is refused, check your firewall settings and network configurations.

    Network Considerations:

    If you're connecting from an Azure VM, verify the network security group (NSG) rules to ensure connections to port 5432 are allowed.

    For virtual network (VNet) integrated servers, ensure that DNS is correctly configured and that VNet peering is properly set up if applicable.

    Firewall Configuration:

    Make sure there are no firewall rules blocking traffic from your client’s public IP address to the PostgreSQL server. You may need to whitelist your public IP in the Azure portal.

    Outdated Records: If your server uses a private endpoint, ensure that DNS settings point to the private endpoint's IP and that no outdated records exist affecting connectivity.

    Use Diagnostics Tool: Azure offers a diagnostic tool that can help identify potential issues. You can access it within the Azure portal.

    Follow-Up Questions:

    • Have you checked the Azure portal to see the current status of the Azure Database for PostgreSQL Flexible Server?
    • Are you able to connect to any other databases, or is this issue isolated to a specific one?
    • Can you confirm if your firewall settings allow outbound connections on port 5432?
    • Are you using a client machine that’s within the same network as the PostgreSQL server if it's a VNet scenario?

    Hopefully, these steps will help provide some clarity while the Microsoft team works on resolving the issue. Let me know if you have any further questions or need assistance with the steps!

    Relevant Documentation:

    Hope this helps, Please let us know if you have any questions and concerns.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.