Recovering after crash

[jhfelectric]

version 2024 server edition

Hello,

After a system crash I was able to recover all my photos by reinstalling postgresql and importing the database.
When starting PSU on the server, all is correct.
When starting PSU on another computer using admin user, I get this error:

2024-05-01 19:38:06.982 EEST [10540] FATAL: no pg_hba.conf entry for host "fe80::f48e:89bc:85d5:adc5%4", user "idimager_main", database "photosupreme_thumbs", SSL off

When starting PSU on another computer using non-admin user, I get this error:

2024-05-01 19:44:37.315 EEST [1804] FATAL: no pg_hba.conf entry for host "fe80::5a0a:9eed:c7ac:8c%4", user "idimager_main", database "photosupreme", SSL off

I have modified the pg_hba.conf file to match the user manual.

I hope someone can help !
Thanks
Jhfelectric

[Hert]

A warm welcome to the User-to-User forum. And sorry to read about your crash.

To recover PostgreSQL, follow the instructions from the Maintenance manual for migrating to anew computer. The most important is that after installing PostgreSQL (follow the PSU instructions) you must first create a new Photo Supreme catalog. Once that is created you can restore these newly created databases from the backup.
Hope that helps

[jhfelectric]

Hi,
Thanks for the reply.
Yes that is what I did, first create a new PSU catalog. After the empty databases have been created, I then restored the old data on top.
PSU has been recreating the thumbs for 3 days, I was connected as admin on server.
But when I tried to connect from another computer, I received the messages noted previously. Note that they are not the same depending on the user, and that the host address looks like IPv6 ??
I messed around with various values in the pg_hba.conf file, but I always get the same error in the Postgresql log.
Thank you for the follow up.
Jhfelectric

[Hert]

Did you follow the PostgreSQL configuration instructions from PSU? If your local network uses IPv6 (as it appears to do) then change the IPv6 host in the pg_hba.conf to ::1/0

If that also doesn't work then try a Google search on "postgresql no pg_hba.conf entry for host". That gives this (among many other):
https://dba.stackexchange.com/questions ... y-for-host