Thread: enhance documentation for SSH-tunneled access to database
Hi, "How do I... Use pgAdmin II via a secure (encrypted) connection?" (http://pgadmin.postgresql.org/pgadmin2/pgadmin2.php?ContentID=11) is an excellent start. I am using the same set-up for mysql for months without a problem. To get this also working with postgres, I tried many approaches with no success, but then, I noticed that 1) even on the server on which postmaster/the database is running, I get <<[root@calimero data]# psql -h localhost -p 5432 -U myUserId myDB psql: could not connect to server: Connection refused Is the server running on host localhost and accepting TCP/IPconnections on port 5432?>> so, perhaps, something needs to be changed on the server side first? 2) secondly, Fred says to enhance pg_hba.conf, but he doesn't hint how to get that additional IP address: Especially since more and more db-servers are behind firewalls and NATed, this is not so trivial. My finding so far is that "/sbin/ifconfig" provides this additional IP-address that is not visible to the outside. Anyway, any hints how to solve 1) would be highly appreciated! Ralf
Hi Ralf, Unfortunately I never used SSL with pgAdmin II myself, so cannot add to the detail in the howto, however you might like to try pgAdmin III (currently at beta 2 release) which includes built in SSL support and provides all the core functionality of pgAdmin II. You can find pgAdmin III at www.pgadmin.org/pgadmin3/. Regards, Dave. > -----Original Message----- > From: Ralf Hauser [mailto:ralfhauser@gmx.ch] > Sent: 13 September 2003 11:19 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] enhance documentation for > SSH-tunneled access to database > > > Hi, > > "How do I... Use pgAdmin II via a secure (encrypted) connection?" > (http://pgadmin.postgresql.org/pgadmin2/pgadmin2.php?ContentID =11) is an excellent start. I am using the same set-up for mysql for months without a problem. To get this also working with postgres, I tried many approaches with no success, but then, I noticed that 1) even on the server on which postmaster/the database is running, I get <<[root@calimero data]# psql -h localhost -p 5432 -U myUserId myDB psql: could not connect to server: Connection refused Is the server running on host localhost and accepting TCP/IPconnections on port 5432?>> so, perhaps, something needs to be changed on the server side first? 2) secondly, Fred says to enhance pg_hba.conf, but he doesn't hint how to get that additional IP address: Especially since more and more db-servers are behind firewalls and NATed, this is not so trivial. My finding so far is that "/sbin/ifconfig" provides this additional IP-address that is not visible to the outside. Anyway, any hints how to solve 1) would be highly appreciated! Ralf ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Dave, Thanks for the quick help. In the meantime, I solved the problem: 'enable "tcpip_socket" in postgresql.conf'. It would be great if Fred could integrate these two newbie obstacles into the documentation. Rgds r. > -----Original Message----- > From: Dave Page [mailto:dpage@vale-housing.co.uk] > Sent: Samstag, 13. September 2003 14:38 > To: hauser@acm.org; pgadmin-support@postgresql.org > Subject: RE: [pgadmin-support] enhance documentation for SSH-tunneled > access to database > > > Hi Ralf, > > Unfortunately I never used SSL with pgAdmin II myself, so cannot add to > the detail in the howto, however you might like to try pgAdmin III > (currently at beta 2 release) which includes built in SSL support and > provides all the core functionality of pgAdmin II. You can find pgAdmin > III at www.pgadmin.org/pgadmin3/. > > Regards, Dave. > > > -----Original Message----- > > From: Ralf Hauser [mailto:ralfhauser@gmx.ch] > > Sent: 13 September 2003 11:19 > > To: pgadmin-support@postgresql.org > > Subject: [pgadmin-support] enhance documentation for > > SSH-tunneled access to database > > > > > > Hi, > > > > "How do I... Use pgAdmin II via a secure (encrypted) connection?" > > (http://pgadmin.postgresql.org/pgadmin2/pgadmin2.php?ContentID > =11) is an excellent start. > > I am using the same set-up for mysql for months without a problem. > > To get this also working with postgres, I tried many approaches with no > success, but then, I noticed that > > 1) even on the server on which postmaster/the database is running, I get > > <<[root@calimero data]# psql -h localhost -p 5432 -U myUserId myDB > psql: could not connect to server: Connection refused > Is the server running on host localhost and accepting > TCP/IP connections on port 5432?>> > so, perhaps, something needs to be changed on the server side first? > > 2) secondly, Fred says to enhance pg_hba.conf, but he doesn't hint how > to get that additional IP address: Especially since more and more > db-servers are behind firewalls and NATed, this is not so trivial. > > My finding so far is that "/sbin/ifconfig" provides this additional > IP-address that is not visible to the outside. > > Anyway, any hints how to solve 1) would be highly appreciated! > > Ralf > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if > your > joining column's datatypes do not match >