bonus weirdness:
in my start up script I run psql "host=<hostname>.database.azure.com port=5432 dbname=postgres user=admin password=$PGPASSWORD" -c "SELECT * FROM users;"
and I can connect to the db even from deployed app
the database’s authentication method is PostgreSQL user and password only
Is the hostname you have configured vitvio-staging.postgres.database.azure.com:5432? Like with the port number? When it says vitvio-staging.postgres.database.azure.com:5432: non-existing domain, that certainly makes sense, because the domain would just be vitvio-staging.postgres.database.azure.com. Maybe you should do
that’s not it, and I can connect to it using the same credentials and the same db name from an image running on my machine. I had to configure the ssl certificates for that too.
I initially thought you might have a problem that there’s a VNET that has another PostgreSQL included via private endpoint, but that seems not to be the case.
I see you’re already having a support ticket open from Friday, I’d say let’s give them a change to dig deeper. Feel free to include me in your mails with support (mailto:chgeuer@…)
One question: You say in your “start up script” you can run psql and connect to the host, but then your Elixir app can’t, do I understand this right? Are both the startup script and the BEAM instance run in the same docker container?
BTW, I see you redacted the hostname in your original post, after I cited it in my reply above. Let me know whether I should delete my reply.
Hey @agata-anastazja , one more question: That IPv6 setting, was that on the Elixir application code side, or an app service plan setting in the Azure Portal? Or on Postgres? If you have a screenshot of the setting that led to the problem, would love to see.