Unable to access PostgreSQl Server during update to VB365 v8

[simhub]

During the update to VB365 v8 I get the following error message:

Unable to access PostgreSQl Server using SQL authentication. Enable SQL authentication in your PostgreSQL server and try again.

I have done the steps from KB4638, checked the config files ‘ph_hba’ and ‘ph_ident’, everything looks fine. The hostname has not been changed.

Case: #07404023

[Mike Resseler]

Hey Simhub,

Thanks for opening a support case. Let us know what the investigation shows. Does this mean the upgrade is stuck?

[simhub]

Thanks for your reply. Yes udpate is stuck.

[michaelsgcmd]

I'm having the same issue as well.
In my case the hostname of the machine was updated when it was first setup

[simhub]

In that case this article should help --> https://community.veeam.com/blogs-and-p ... tname-6348

[Mike Resseler]

That article is for VBR, not for VB365. I have not tested this on a VB365 server and not sure if it will work to be honest

[OashaP]

Hi, we are also having the same problem.
Unfortunately, the given KB article from the error message was not able to resolve our problem.

Case Nr. #07415085.

[ReKe]

Hello,

I try to upgrade a V7 to v8 on a VM for a verry smal custoumer where also VBR is installed. I follwed this KB https://www.veeam.com/kb4638 to use the postgre for VBR und V365. This one worked for me on other parallel installations. But on this one I still can't install V365.

The error is still "Unable to access PostgreSQl Server using SQL authentication. Enable SQL authentication in your PostgreSQL server and try again."

Greetings Rene

Case-ID: 07421946

[ReKe]

Hello,

for me probblem was solved. IPV6 was diasbled on the networkcard. Maybe something that also should be mentioned in KB4638 that defnetly IPV6 is needed with v8.

Greetings Rene

[DaStivi]

disable IPv6 only on the NIC in Windows doesn't disable IPv6 completely or fully nor is this supported, maybe this is the reason... there is ah RegKey to control IPv6! the recommended setting there is to "prefer IPv4 over IPv6" ... and never touch the IPv6 Checkbox on any of the NICS then! even windows uses this internally...

[michaelsgcmd]

IPv6 being disabled was the fix for me as well.
Once it was enabled I was able to get passed the SQL authentication.

[novusbrian]

FYI to anyone running into this issue, but you don't want to enable IPv6 for whatever reason, here's a solution that forces PostgreSQL to use IPv4 only.

1) Stop all Veeam services
2) In the 'postgresql.conf' file, instead of specifying a listen address of "*", use "0.0.0.0" instead. This binds PostgreSQL to listen on IPv4 only
3) In 'pg_hba.conf', comment out any line that contains references to IPv6 address spaces. Eg: "::/0"
4) Restart PostgreSQL server
5) Restart Veeam services
6) Run the Veeam Backup for Microsoft 365 installer again