From: | John Meredith <meredijo(at)gmail(dot)com> |
---|---|
To: | Daniel Weitzenfeld <dweitzenfeld(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Connecting to PostgreSQL server |
Date: | 2011-06-30 07:32:04 |
Message-ID: | BANLkTinz4gTh_8i-hzzO7tDd=5WdEx5drg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hi,
Is there any device between your postgreSQL server and PC, e.g. network
router or firewall?
Something else besides the iptables on your server can be blocking port
5432. I'd also check that your PostgreSQL server hasn't been configured to
listen on some other port.
On 30 Jun 2011 08:11, "Daniel Weitzenfeld" <dweitzenfeld(at)gmail(dot)com> wrote:
> Hi,
> I have a remote server with PostgreSQL on it.
> When I try to connect via python/pygresql, I get:
>
> pg.InternalError: could not connect to server: Connection refused
> Is the server running on host "##.##.##.###" and accepting
> TCP/IP connections on port 5432?
>
> Where I've blanked out my server's ip address for obvious reasons.
>
> I ssh'd to my server and did this to iptables:
>
> iptables -A INPUT -p tcp --dport 5432 -j ACCEPT
>
> restarted iptables, but still no dice.
>
> Any advice?
>
> Thanks in advance!
> -Daniel
From | Date | Subject | |
---|---|---|---|
Next Message | Vincent Ficet | 2011-06-30 08:30:45 | Re: pg_advisory_locks in a multithreaded application context |
Previous Message | Daniel Weitzenfeld | 2011-06-30 02:07:35 | Connecting to PostgreSQL server |