It turns out RDS by default forces ssl connections for pg15 instances. I
have turned this off for now while I work out how that impacts my code and
I can now connect to the pg15 instance.
Thanks,
Steve
On Sun, Jun 4, 2023 at 3:10 PM Steve Baldwin
wrote:
> I suspect it may have something to do
I suspect it may have something to do with ssl. The FATAL error in the log
said "no encryption". I'm not sure what that means. When I look at a
connection to one of our pg14 instances from the same API server, I see
this in the logs:
2023-06-04 00:03:06.210 UTC,"b2bc_api","b2bcreditonline",16024,"
Hi all,
I'm in the process of migrating from an RDS pg14 instance to pg15.3. As
part of the migration process, the application code makes a test connection
to the new instance. This failed. I tried manually connecting to the kube
pod where the test query was submitted from, and from there was able
, 7 September 2018 8:38 PM
To: pgsql-gene...@postgresql.org
Subject: connection error
getting below error from application side :
Last acquisition attempt exception:
org.postgresql.util.PSQLException: Connection refused. Check that the hostname
and port are correct and that the postma
On Fri, Sep 7, 2018 at 5:10 PM amul sul wrote:
>
> Do you have following entry as well?
>
> # IPv6 local connections:
> hostall all ::1/128 trust
>
> I hope "listen_addresses " in postgresql.conf is on default setting.
>
Sorry, I misread -- your local p
Do you have following entry as well?
# IPv6 local connections:
hostall all ::1/128 trust
I hope "listen_addresses " in postgresql.conf is on default setting.
Regards,
Amul Sul
On Fri, Sep 7, 2018 at 4:08 PM Sonam Sharma wrote:
>
> getting below error
getting below error from application side :
Last acquisition attempt exception:
org.postgresql.util.PSQLException: Connection refused. Check that the
hostname and port are correct and that the postmaster is accepting TCP/IP
connections.
the port no is set correct :
[postgres@lxsqlptgs
