Unable to Connect to Neon Database Hosted on AWS Singapore Region
I recently created a database on Neon, selecting AWS as the cloud service provider and Singapore as the region. The database endpoint is:
ep-rapid-bread-a1d0j61k.ap-southeast-1.aws.neon.tech
However, I am currently unable to connect to this database. I have also tested the connectivity using https://ping.pe/, and observed a 100% packet loss when trying to ping the endpoint.
Could you please advise on how to resolve this issue? Is there any additional configuration required to enable external access, or could there be a network restriction on the Neon or AWS side?
Ping, mtr, dig, TCP port check and real time BGP looking glass from...
The Best Ping+MTR combination Ever, plus TCP port checker and DNS diagnostics with dig, plus real time BGP looking glass from multiple locations.
5 Replies
correct-apricot•3mo ago
In ping.pe it seems you have to specify a port - either 443 or 5432 work
There's no restrictions in place. What errors do you get when connecting?
other-emeraldOP•3mo ago
Thank you for your feedback.
I deployed my service on a VPS last year, and recently I have been unable to connect to the database. The error message I receive is as follows:
File "/usr/local/lib/python3.11/site-packages/psycopg2/init.py", line 122, in connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name "ep-rapid-bread-a1d0j61k.ap-southeast-1.aws.neon.tech" to address: Temporary failure in name resolution
(Background on this error at: https://sqlalche.me/e/20/e3q8)
Deploy command failed, retrying in 10 secs...
I reported this issue to my VPS provider, and they pointed out that they also could not ping the database endpoint using https://ping.pe/.
Is there something wrong with the way I am connecting to the database? Or could this be a DNS or network issue on the VPS side?
Ping, mtr, dig, TCP port check and real time BGP looking glass from...
The Best Ping+MTR combination Ever, plus TCP port checker and DNS diagnostics with dig, plus real time BGP looking glass from multiple locations.
correct-apricot•3mo ago
It does look like a DNS issue on the VPS
In your screenshot you do see the IP address that resolved for your endpoint (52.220.170.93)
If you have shell access on your VPS, you could try use the
dig ep-rapid-bread-a1d0j61k.ap-southeast-1.aws.neon.tech command to see if it's specific to python or notcorrect-apricot•3mo ago
Here's the correct ping.pe page https://tcp.ping.pe/ep-rapid-bread-a1d0j61k.ap-southeast-1.aws.neon.tech:5432
Ping, mtr, dig, TCP port check and real time BGP looking glass from...
The Best Ping+MTR combination Ever, plus TCP port checker and DNS diagnostics with dig, plus real time BGP looking glass from multiple locations.
other-emeraldOP•3mo ago
Thank you very much for your quick response and helpful suggestions!
I will follow your advice and check with my VPS provider to further investigate the DNS issue.