[ome-users] Not able to connect remotely

[josh.moore at gmx.de]

Paulo Almeida writes:
 > Hi Josh,

Hi again Paulo.

What's important is that we get your topology straight. There are
three machines involved. 

 A, the database
 B, the server
 C, the client

B needs to be able to "see" the db on A. That means if you configure
OMERO on B, you'll need to point it at A, using either the hostname of
A or the ip address (which includes "localhost" and "127.0.0.1" if the
database is on the same machine). On A, you'll need to configure
pg_hba.conf to permit B to view that database. 

It seems you worked things out to this stage. 

The problem you're running into now is that C cannot communicate with
B. 127.0.0.1 always points to the localhost, so you'll need to
configure your client on C with "argos" or 172.22.50.245 (I'm guessing
that this is the right ip from your email).

Good luck,
Josh.

 > I did in fact have a line like this in /etc/hosts:
 > 
 > 127.0.0.1        localhost
 > 127.0.1.1        argos.igc.gulbenkian.pt argos
 > 
 > I removed the second line but then "java omero update deploy" wouldn't build 
 > successfully, complaining about a missing entry for 172.22.50.245 in 
 > pg_hba.conf. 
 > 
 > (that is the IP of argos)
 >
 > I then changed the first line to read:
 > 
 > 127.0.0.1      localhost argos
 > 
 > and "java omero update deploy" built successfully, but when I try to connect 
 > >from another computer I get the same error as before, except with 127.0.0.1 
 > now, instead of 127.0.1.1.
 > 
 > By the way, should the database host be set to argos, or can it be localhost? 
 > I had assumed it was localhost, but I'm not sure. Do the admin and insight 
 > clients interact directly with the DB or does the server do that?
 > 
 > Thanks,
 > Paulo