| From: | Jacques Lamothe <JLamothe(at)allconnect(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | "rod(at)iol(dot)ie" <rod(at)iol(dot)ie>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL |
| Date: | 2011-12-27 19:49:17 |
| Message-ID: | A464248CE14E60408AC030D3CD1790BA02721A@ACMAILNODE01.allconnect.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
thanks
-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)gmail(dot)com]
Sent: Tuesday, December 27, 2011 2:48 PM
To: Jacques Lamothe
Cc: rod(at)iol(dot)ie; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
On 12/27/2011 11:44 AM, Jacques Lamothe wrote:
> Yes I'm running on amazon.aws and yes I requested my admin to open the port, do you know how I can check its status
The AWS firewall is for an account so it lives outside the instances.
The way I check is using the AWS Management Console. You need account
access for that though, so you may have to talk with the admin.
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2011-12-27 22:07:26 | Re: invalid memory alloc request size |
| Previous Message | Jacques Lamothe | 2011-12-27 19:48:29 | Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL |