Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
robb183
Contributor III
Contributor III

Problems Encryption Method during version change - Postgres 9.6

During the version upgrade from Qlik Sense November 2019 to February 2022 the attached message appeared in the environment multinode.

Has anyone got the same message? Tips?

thank you

Roberto

 

robb183_0-1657013234523.png

 

Labels (1)
2 Solutions

Accepted Solutions
Eugene_Sleator
Support
Support

Hi @robb183  have you changed the encryption type, or enabled database traffic encryption? See this  article. 

View solution in original post

Albert_Candelario

Hello @robb183 ,

Thanks for posting.

 

Kindly go to the file mentioned and check the method used and if is using one of the mentioned ones as below:


# TYPE DATABASE USER ADDRESS METHOD

# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#host replication postgres 127.0.0.1/32 md5
#host replication postgres ::1/128 md5

 

If is not the case, kindly edit it and try to upgrade again and afterwards (once the upgrade is successful) change it back to the current method.

 

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer

View solution in original post

2 Replies
Eugene_Sleator
Support
Support

Hi @robb183  have you changed the encryption type, or enabled database traffic encryption? See this  article. 

Albert_Candelario

Hello @robb183 ,

Thanks for posting.

 

Kindly go to the file mentioned and check the method used and if is using one of the mentioned ones as below:


# TYPE DATABASE USER ADDRESS METHOD

# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5
# Allow replication connections from localhost, by a user with the
# replication privilege.
#host replication postgres 127.0.0.1/32 md5
#host replication postgres ::1/128 md5

 

If is not the case, kindly edit it and try to upgrade again and afterwards (once the upgrade is successful) change it back to the current method.

 

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer