Unable to login to database... Reason: FATAL

[preparac]

I'm running Beta 18 on my computer, untill a few days without problems. Now when I open it, PT3 starts, but give me no acces to my databases. I get followoming error message:

Unable to login to database (name of activ database) Reason: FATAL: np pg_hba.conf entry for host "::", user "postgres", database "name of activ database", SSL off

What this means and what to doo? Probably I messed up somenthing, because I mistankenly entered my Pokertracker license on THREE computers in my house? But I need pokertracker on THIS computer! If this is the problem - can I take back the licence from the other computers? Or how to resolve this? An if not, what could be the problem?

Appreciate your help

[preparac]

Edit:
I had installed a new router yesterday. Could this be part of the problem (Firewall etc.)? ... but on the other computer in the network I have a normal working copy of PT3 with another Database. So I don't know ...
PLZ help!!! I'm totally blocked!

[preparac]

Ok, I get no answer but I'm coming closer to a solution: It must be a network/router-Problem. I re-installed my old router/network configuration and now PT gives me access to my SQL-Database on my main-computer again and works normaly.

How I can make PT to work also with my new network/router

I really apreciate any help...

[WhiteRider]

You need to make sure your router/firewall is allowing postgres to have access to port 5432.

[preparac]

Thanks for your answer. Any hint how I do this? (never made something like this before ... sorry) ... And any Idea why then PT works normal on my other computer, which connects over the same router?

[WhiteRider]

Do you mean PT3 works fine on the other computer?
If so, then it must be some local config on that computer - do you have a firewall on each computer, or is the router doing it?
Compare your "pg_hba.conf" files on the 2 computers and see if you can find the difference (make a backup copy of them both before you change anything!). This file will be in the "C:\Program Files\PostgreSQL\8.3\data" folder.

[preparac]

Do you mean PT3 works fine on the other computer?

Yes, on the other computer it works fine

If so, then it must be some local config on that computer - do you have a firewall on each computer, or is the router doing it?

As I know, I have individual firewalls (one kaspersky firewall and 1 kaspersky trial version firewall) on my computers. I'm not aware, that I installed this new router as firewall and my kaspersky firewalls work normal, but I could check this with my provider ...

Compare your "pg_hba.conf" files on the 2 computers and see if you can find the difference (make a backup copy of them both before you change anything!). This file will be in the "C:\Program Files\PostgreSQL\8.3\data" folder.

I found a difference in th two "pg_hba.conf" files.
In the first one (Version SQL 8.2) which runs well, it says:

# METHOD can be "trust", "reject", "md5", "crypt", "password",
# "krb5", "ident", "pam" or "ldap".

In the second one (Version SQL 8.3) which doesn't give me access with the new router (but gives me with old one, which I connect through USB) well, it says:

# METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
# "krb5", "ident", "pam" or "ldap".

Both files end identically like this:

# TYPE DATABASE USER CIDR-ADDRESS METHOD

# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
#host all all ::1/128 md5

Any idea?
Again thanks for your help

[kraada]

Try removing the # before the:
host all all ::1/128 md5

line. The lines with # in front of them are commented out. It sounds like your computer is trying to use IPv6 for which there is no definition of your own computer in the postgres configuration file. So un-comment the line above (by removing the #) and that should give you the IPv6 route to localhost and then try restarting the database with Start --> Programs --> PostgreSQL --> Stop Service, then Start Service.

[preparac]

Kraada I LOVE you. This worked fine ... ! I just wiped out this #
Thank you for your help guys
(any idea why something like this could happen??)

And in general I wanted to tell you: don't let you discourage by the tons of angry comentars you get becaus of the bugs and delays. It is a graeat program and I'm looking forward for the new features you announced...
By the way: How exactly you plan to integrate the new features. I'm satisfied for the moment with Beta18 and I would prefer not to upgrade on build 3 if its not necessary (because of the lenghty conversion process of my database and especially because some users seem to have unteill now new disturbing problems with Build 3 - so I would like to wait little bit and use my Beta 18 more). But I didn't get well how this will work with future Betas. Will they be based on Build 3.0 or can I just go ahead and download the new Beta 19, 20 and so on over my actual 18 without upgrading to Build 3.0?

[WhiteRider]

Every update is based on the last, this included Betas and Builds.
When you update, you do not need to do anything to your database (for most updates - sometimes there will be a need to re-import but we hope these will be much rarer in future).
Just stop PT3 and install the update over the top.
Download and install PT3.

Build 3 only includes a few minor bug fixes, so the update will take only a few seconds - no need to do anything to your database.