RE: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

Hi Bikram,

I was thinking about the win10 firewall, as you mentioned having intalled pgadmin4 on win10. Haven't used this setup on my own, just know, some installers (pgadmin4?) open up specific ports during installation. Might be, your local firewall is configured not to allow all tcp outbound traffic and blocking 5433?

Best,

Tim Scheurenbrand

On Mon, Aug 12, 2019 at 11:51 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com> wrote:

Hi Tim,

 

Thanks for your quick response.

Are you thinking port 5433 is not opened for listening on the postgres database server?

[root@cemtore01 ~]# systemctl status firewalld.service

â firewalld.service - firewalld - dynamic firewall daemon

   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)

   Active: active (running) since Mon 2019-04-01 05:49:28 CDT; 4 months 11 days ago

     Docs: man:firewalld(1)

Main PID: 883 (firewalld)

   CGroup: /system.slice/firewalld.service

           ââ883 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

 

Apr 01 05:49:28 cemtore01 systemd[1]: Started firewalld - dynamic firewall daemon.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.

Apr 01 05:49:30 cemtore01 firewalld[883]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.

May 22 11:25:23 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: port

May 22 11:25:40 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: ports

May 22 11:27:07 cemtore01 firewalld[883]: ERROR: INVALID_ZONE: zone

 

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

 

 

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.

 

From: Tim Scheurenbrand <info@timscheurenbrand.de>
Sent: Monday, August 12, 2019 4:25 PM
To: Bikram MAJUMDAR <Bikram.Majumdar@aqsacom.com>; pgsql-admin@postgresql.org
Cc: bikramma@gmail.com
Subject: Re: Need help in establishing pgadmin4 to connect to the postgres database server when the database is listening on port 5433 (instead of port 5432)

 

Hi Bikram

Have you checked your firewall settings?

Tim Scheurenbrand

On Mon, Aug 12, 2019 at 11:08 PM +0200, "Bikram MAJUMDAR" <Bikram.Majumdar@aqsacom.com> wrote:

 

Hi ,

We need help in resolving connection issues using the pgadmin tool.

We had our pgadmin (pgadmin4) installed a few months back on windows 10 and we were able to use it for  our postgres server running on port 5432.

But, recently we had to change our postgres server port from 5433 to 5432 - 

And accordingly, in pgadmin we changed the port also to 5433 – but we are receiving connection timed out error in connecting to our server (see below screen shot).

 

 

 

Please help to resolve this issue.

 

Bikram Majumdar

Sr Software Developer/DBA, Aqsacom Inc.

c. 1.972.365.3737

e. bikram.majumdar@aqsacom.com

s. BIKRAM MAJUMDAR

 

 

Disclaimer. This electronic mail message contains CONFIDENTIAL information which is (a) CUSTOMER / SUPPLIER / PARTNER PRIVILEGED COMMUNICATION, WORK PRODUCT, PROPRIETARY IN NATURE, OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) intended only for the use of the Addressee(s) named herein. If you are not an Addressee, or the person responsible for delivering this to an Addressee, you are hereby notified that reading, copying, or distributing this message is prohibited. If you have received this electronic mail message in error, please reply to the sender and take the steps necessary to delete the message completely from your computer system. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AQSACOM. AQSACOM accepts no liability for any damage caused by any virus/worms transmitted by this email.