2 回答
- 最新
- 投票最多
- 评论最多
0
It could be that the version of the RDS Postgres database was upgraded recently and that has rendered the pgadmin version incompatible. Or else your pgadmin may have gotten corrupted for whatever reason. If you haven't tried it already, I would try reinstalling pgadmin and see if that helps.
We also have a Premium Support article that may help debug - https://aws.amazon.com/premiumsupport/knowledge-center/rds-cannot-connect/
0
I was resolve this choosing the last version of Postgres engine when creating my RDS Postgres.
已回答 1 个月前
相关内容
AWS 官方已更新 3 年前- AWS 官方已更新 2 年前
Thanks for the reply. I downloaded the latest version of pgAdmin 4 and still getting the same timeout expired error.
Is the application that is working using the same username/password to connect to the database, as pgadmin? If not, make sure the password of the user was not modified. If the Security Group inbound rules are fine, I would also take a look at the security group outbound rules and also NACLs on the subnet to ensure nothing has changed recently. Can't think of any other reason why pgadmin would suddenly stop connecting to the database.