Can't see or access database server after automatic migration

Question

After automatic migration of our Postgres single database servers to flexible servers that started 14.09. and lasted until 20.09. i can't see new database servers in my resource group.
I can access database through power shell but not from the outside.

Answer 1

It sounds like after the migration from a single Postgres server to a flexible server in Azure, you are unable to view or access the new database servers in your resource group, though you can still access them through PowerShell. This issue could stem from a few potential causes, which I’ll outline below with some troubleshooting steps:

Possible Causes:

1. The new servers may not be appearing in the Azure Portal's Resource Group view due to a refresh delay or a change in how resources are listed.
2. Flexible servers use a different network model, and firewall rules or VNet settings may need to be updated to allow external access.
3. Migration processes might alter connection settings or credentials that could block access from outside the PowerShell environment.
4. Your permissions in the resource group may not have migrated properly, affecting visibility or access from outside tools.
5. Changes in the server name or IP addresses during migration could cause DNS issues, especially if cached configurations are outdated.

Troubleshooting Steps:

1. Check Azure Portal:
   • Try refreshing the Resource Group page in the Azure Portal or logging out and back in.
   • Go to Azure Database for PostgreSQL under "All Services" and see if the flexible server shows up there.
   • Use the Azure Resource Explorer to search for the database and ensure it's listed.
2. Review Network and Firewall Settings:
   • In the Azure Portal, navigate to your flexible server and check the Networking tab.
   • Make sure the Public Access is enabled, or if using Private Access, ensure the VNet is correctly configured.
   • Review the firewall rules and ensure that the IP range you are trying to connect from is allowed.
3. Connection Strings:
   • In PowerShell, verify the connection string being used and compare it to the one configured in your external tools.
   • Check if the hostname or port has changed after migration, and ensure you’re using the new flexible server connection details.
4. Access Roles:
   • Check your Azure RBAC roles to ensure you have the necessary permissions on the resource group and the new flexible server.
   • You can try assigning the Contributor or PostgreSQL Server Administrator roles if needed.
5. DNS and Caching:
   • If using the old connection strings, they might have cached the DNS or IP of the previous server. Flush your DNS cache or try connecting using the new server's IP address.
   • Run nslookup <server-name> to confirm the new server resolves correctly.

If the issue persists, you might need to contact Azure Support, especially if there are issues related to the automatic migration.

Let me know if you need further assistance with any of these steps!

Answer 2

I'm having the exact same issue.

Migration was started 18.09, the old single server instance was deleted today and I can't see the new flexible instance.

I can't find it in the Resources list, nor the Azure Database for PostgreSQL flexible servers, powershell or any place. The only good thing is, I can connect from an app hosted in azure to a postgresql database and I have some recent data in it.