Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQWIV-0006Ny-2l for pgsql-admin@arkaria.postgresql.org; Fri, 10 Feb 2023 16:30:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pQWIT-0004Bn-V8 for pgsql-admin@arkaria.postgresql.org; Fri, 10 Feb 2023 16:30:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQUAG-0002iY-TF for pgsql-admin@lists.postgresql.org; Fri, 10 Feb 2023 14:14:13 +0000 Received: from mail-cy.bbox.fr ([194.158.98.48]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQUAB-0007Hk-7a for pgsql-admin@postgresql.org; Fri, 10 Feb 2023 14:14:11 +0000 Received: from mail.jppozzi.dyndns.org (mer91-h01-176-172-74-140.dsl.sta.abo.bbox.fr [176.172.74.140]) by mail-cy.bbox.fr (Postfix) with ESMTP id 7122B37; Fri, 10 Feb 2023 15:14:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.jppozzi.dyndns.org (Postfix) with ESMTP id F36EC300222; Fri, 10 Feb 2023 15:14:02 +0100 (CET) Received: from mail.jppozzi.dyndns.org ([127.0.0.1]) by localhost (mail.jppozzi.dyndns.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ALE7L0d--rYu; Fri, 10 Feb 2023 15:14:00 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.jppozzi.dyndns.org (Postfix) with ESMTP id AF8AC300220; Fri, 10 Feb 2023 15:14:00 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.jppozzi.dyndns.org Received: from mail.jppozzi.dyndns.org ([127.0.0.1]) by localhost (mail.jppozzi.dyndns.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id vshkalbhYyVV; Fri, 10 Feb 2023 15:14:00 +0100 (CET) Received: from mail.jppozzi.dyndns.org (mail.jpp.fr [192.168.2.21]) by mail.jppozzi.dyndns.org (Postfix) with ESMTP id 8BD2130004E; Fri, 10 Feb 2023 15:14:00 +0100 (CET) Date: Fri, 10 Feb 2023 15:14:00 +0100 (CET) From: JP Pozzi To: Jamie Romano Cc: pgsql-admin Message-ID: <117008288.1097.1676038440504.JavaMail.zimbra@jppozzi.dyndns.org> In-Reply-To: References: Subject: Re: Proxy pgadmin connection issue MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_fc35c069-6194-42f5-a484-824cc2d19f12" X-Originating-IP: [192.168.2.8] X-Mailer: Zimbra 8.8.15_GA_4484 (ZimbraWebClient - FF102 (Linux)/8.8.15_GA_4481) Thread-Topic: Proxy pgadmin connection issue Thread-Index: VAA8DnX5TFDabB69F0FItyp5Nvbo9Q== X-VADE-SPAMSTATE: clean X-VADE-SPAMSCORE: -100 X-VADE-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudehhedgiedtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuuefqfggjifgfgffupdcuqfgfvfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvvefkjghfufggtghiofhtsegrtdgtreertdejnecuhfhrohhmpeflrfcurfhoiiiiihcuoehjphhpsehjphhpohiiiihirdguhihnughnshdrohhrgheqnecuggftrfgrthhtvghrnheptdetvefhvdeukeelieefffevtedvieeuveevgfelueduleeguefftdfgleffjeelnecuffhomhgrihhnpehmrggvrhhskhdrtghomhenucfkphepudejiedrudejvddrjeegrddugedtpdduledvrdduieekrddvrdeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepudejiedrudejvddrjeegrddugedtpdhhvghlohepmhgrihhlrdhjphhpohiiiihirdguhihnughnshdrohhrghdpmhgrihhlfhhrohhmpehjphhpsehjphhpohiiiihirdguhihnughnshdrohhrghdpnhgspghrtghpthhtohepvddprhgtphhtthhopehjrghmihgvrdhrohhmrghnohesvghnthgvrhhprhhishgvuggsrdgtohhmpdhrtghpthhtohepphhgshhqlhdqrggumhhinhesphhoshhtghhrvghsqhhlrdhorhhg List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_fc35c069-6194-42f5-a484-824cc2d19f12 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello,=20 The problem is probably with the Firewall, no rule to enable the port 5432.= =20 I think it would not be a solution to expose that port to the "bad" outside= ;=20 Connect a terminal emulator to a machine "inside" and you will be able to u= se pgadmin;=20 Regards=20 JP P=20 De: "Jamie Romano" =20 =C3=80: "pgsql-admin" =20 Envoy=C3=A9: Vendredi 10 F=C3=A9vrier 2023 00:48:59=20 Objet: Re: Proxy pgadmin connection issue=20 Please remove me from the email list. Great group but I just wanted to get = a sense of the questions and discussion.=20 On Thu, Feb 9, 2023 at 05:02 Pawan Singh < [ mailto:pawan.singh@maersk.com = | pawan.singh@maersk.com ] > wrote:=20 Hi, PostgreSQL Community!=20 I have a question =E2=80=93 How can we connect to Postgresql database in pg= admin4 behind corporate proxy?=20 I am getting connection timed out error while trying to connect to postgres= db=20 Thanks!!=20 Classification: Internal=20 From: Loles < [ mailto:lolesft@gmail.com | lolesft@gmail.com ] >=20 Sent: Thursday, February 9, 2023 10:50 AM=20 To: [ mailto:pgsql-admin@postgresql.org | pgsql-admin@postgresql.org ]=20 Subject: Max I/O traffic=20 This message was sent from outside of your organization. Please do not clic= k links or open attachments unless you recognize the source of this email a= nd know the content is safe.=20 Hi, PostgreSQL Community!=20 I have a question for experts..=20 How much is the maximum number of I/O calls that PostgreSQL currently suppo= rts?=20 Thanks!!=20 The information contained in this message is privileged and intended only f= or the recipients named. If the reader is not a representative of the inten= ded recipient, any review, dissemination or copying of this message or the = information it contains is prohibited. If you have received this message in= error, please immediately notify the sender, and delete the original messa= ge and attachments.=20 Maersk will as part of our communication and interaction with you collect a= nd process your personal data. You can read more about Maersk=E2=80=99s col= lection and processing of your personal data and your rights as a data subj= ect in our [ https://www.maersk.com/front-page-requirements/privacy-policy = | privacy policy ]=20 Please consider the environment before printing this email.=20 --=20 V/r,=20 Jamie=20 301-606-7624=20 --=_fc35c069-6194-42f5-a484-824cc2d19f12 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello,

The problem is probably with the Firewall, no rule to enable = the port 5432.
I think it would not be a solution to expose that port to= the "bad" outside;
Connect a terminal e= mulator to a machine "inside" and you will be able to use pgadmin;

Regards

JP P


De: "Jamie Romano" <= jamie.romano@enterprisedb.com>
=C3=80: "pgsql-admin" <pgsql= -admin@postgresql.org>
Envoy=C3=A9: Vendredi 10 F=C3=A9vrier 2= 023 00:48:59
Objet: Re: Proxy pgadmin connection issue
<= div>
Please= remove me from the email list.  Great group but I just wanted to get = a sense of the questions and discussion. 

On Thu, Feb 9, 2023 at 0= 5:02 Pawan Singh <pawan.singh@maersk.com> w= rote:

 

Hi, PostgreSQL Community!

 

I have a question =E2=80=93 How can we connect to Po= stgresql database in pgadmin4 behind corporate proxy?

 

I am getting connection timed out error while trying= to connect to postgres db

 

Thanks!!

 

 

<= span style=3D"font-size:10pt;color:black">Classification: Internal

From: Loles <lolesft@gmai= l.com>
Sent: Thursday, February 9, 2023 10:50 AM
To: pgsql-admin@postgresql.org
Subject: Max I/O traffic

 

This message was sent from outside of your organization. Plea= se do not click links or open attachments unless you recognize the source o= f this email and know the content is safe.

 

Hi, PostgreSQL Community!

 

I have a question for experts..

 

How much is the maximum number of I/O calls that Pos= tgreSQL currently supports?

 

Thanks!!




The information contained in this message is privileged and intended only f= or the recipients named. If the reader is not a representative of the inten= ded recipient, any review, dissemination or copying of this message or the = information it contains is prohibited. If you have received this message in error, please immediately notify the = sender, and delete the original message and attachments.

Maersk will as part of our communication and interaction with you collect a= nd process your personal data. You can read more about Maersk=E2=80=99s col= lection and processing of your personal data and your rights as a data subj= ect in our privacy policy

Please consider the environment before printing this email.
--
= V/r,
Jamie

301-606-7624

--=_fc35c069-6194-42f5-a484-824cc2d19f12--