[vwnc] Accessing Store remotely

Hello,

I have a Store repository on my machine that I would like to share with
a remote user.  My Store repository is called "storeRepository" and I
can connect locally with no problem.

The remote user uses my ipaddress to attempt to connect, i.e.,
100.20.91.120:5432_storeRepository.

(The ip address is made up for this example.) This fails with the error
message: "Peer communications error".

What should a remote user enter for the "Environment" field when
attempting to connect?

Is there some setup that I must perform to allow remote access?

Thanks,
Frank

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

It's likely an issue with not having a hole in your firewall for access
to your local network -- If this is the case your database will never 'see'
the connection.. If you're using PostgreSQL I believe the typical port # is
5432 if I recall..

On Thu, 23 Jul 2009 12:18:05 -0400, Squeaker <[hidden email]> wrote: _______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Most likely you haven't set PostgreSQL to allow anything other than  
localhost connections. I don't recall how to change that, but there  
are good Postgres docs online

James Robertson
Cincom Smalltalk Product Evangelist
http://www.cincomsmalltalk.com/blog/blogView
Talk Small and Carry a Big Class Library




On Jul 23, 2009, at 12:18 PM, Squeaker wrote:

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

there are two .conf files for postgres, one is pg_hba.conf and the other
is postgres.conf (or something pretty close to that). In the
postgres.conf file you need to setup your listenAddress so that it is
un-commented and so that its value is '*' (any address)

Also in your pg_hba.conf you need to edit your list of allowed databases
and what IPs can login (this is commented in the file itself, describes
how to do it).

Basically what you should do is just set everything to be wide open
while you test out your networking (don't forget you need to restart
postgres whenever you change your config) - then lock it down with
security as soon as it looks like the networking is ok..

If you break something when you lock it down you'll know soon enough ;-)

Let me know how it goes,

David

ps 0.0.0.0/24 or 0.0.0.0/0 are useful values to use in pg_hba.conf for
IP addresses (towards the bottom)
-----Original Message-----
From: Squeaker <[hidden email]>
To: [hidden email]
Subject: [vwnc] Accessing Store remotely
Date: Thu, 23 Jul 2009 12:18:05 -0400

Hello,

I have a Store repository on my machine that I would like to share with
a remote user.  My Store repository is called "storeRepository" and I
can connect locally with no problem.

The remote user uses my ipaddress to attempt to connect, i.e.,
100.20.91.120:5432_storeRepository.

(The ip address is made up for this example.) This fails with the error
message: "Peer communications error".

What should a remote user enter for the "Environment" field when
attempting to connect?

Is there some setup that I must perform to allow remote access?

Thanks,
Frank

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

On 23.07.2009, at 18:39, James Robertson wrote:

> Most likely you haven't set PostgreSQL to allow anything other than
> localhost connections. I don't recall how to change that, but there
> are good Postgres docs online

Googe for "pg_hba.conf"

Andre

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

David Long wrote:

>
> Let me know how it goes,
>
> David

I got things sorted out thanks to the help provided by the responses here.

Here is what I figured out:
1. on ubuntu, all the ports are open so I did not have to mess around
with iptables
2. The only changes that were required is to modify the config files
"postgresql.config" and "pg_hba.conf" files (as described in the
responses in this thread).
3. It seems that using "restart" for the server did not work for me, it
would not read the changes made to the config files.  I had to
explicitly  "stop" and "start" the server before the changes in the
config file would be read.

Thanks for all the help,

Frank

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Yes, I used iptables for a while, but on the latest Ubuntu I find it
isn't necessary.

David

-----Original Message-----
From: Squeaker <[hidden email]>
To: [hidden email]
Subject: Re: [vwnc] Accessing Store remotely
Date: Fri, 24 Jul 2009 09:12:42 -0400

David Long wrote:

>
> Let me know how it goes,
>
> David

I got things sorted out thanks to the help provided by the responses here.

Here is what I figured out:
1. on ubuntu, all the ports are open so I did not have to mess around
with iptables
2. The only changes that were required is to modify the config files
"postgresql.config" and "pg_hba.conf" files (as described in the
responses in this thread).
3. It seems that using "restart" for the server did not work for me, it
would not read the changes made to the config files.  I had to
explicitly  "stop" and "start" the server before the changes in the
config file would be read.

Thanks for all the help,

Frank

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc