Azure
az postgres flexible-server execute ssl
I'm running the az postgres flexible-server execute command, but it won't connect:
ERROR: Unable to connect to flexible server: connection to server at "<name>.postgres.database.azure.com" (10.194.1.4), port 5432 failed: FATAL: password authentication failed for user "admin_sutin" connection to server at "<name>.postgres.database.azure.com" (10.194.1.4), port 5432 failed: FATAL: no pg_hba.conf entry for host "10.192.253.4", user "admin_sutin", database "postgres", no encryption
It says no encryption, but Azure postgres flexible-server has ssl by default. The command doesn't allow to enable ssl.
This is strange right?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 065fdfa8-5ed2-e032-6ea7-99a1f5dc28b6
- Version Independent ID: 71881d7f-c4b3-ce3c-1a1a-6c17dc533852
- Content: az postgres flexible-server
- Content Source: latest/docs-ref-autogen/postgres/flexible-server.yml
- Service: postgresql
- GitHub Login: @rloutlaw
- Microsoft Alias: routlaw
@ferronsw I am able to connect to postgres flexible server without any issues. Have you added the correct ip address of your machine to postgres flexible server ? Also, please try updating rdms-connect extension using az extension update --name "rdbms-connect" and try again.
@ferronsw Please let me know if you still have any questions else, we will be proceeding with the closure of this issue.
I think it's because I use VNET integration for the postgres instance. The machine I run the PowerShell command from can connect to the server. But maybe the command isn't executed from this machine?
I already have the latest version of rdms-connect.
@ferronsw ok.. let me check with a server having vnet integrations.
@ferronsw Are you able to connect to your flexible server using psql ?
@ferronsw I suggest you to please open a Azure Support Ticket so that an engineer can check further investigate this issue. In case you have any limitations in your support plan to open support ticket please let me know.
@ferronsw We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.