Error when connecting to Postgre SQL DB servers with DBeaver using SIA

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Error when connecting to Postgre SQL DB servers with DBeaver using SIA

L4 Transporter

Hi all,

 

When trying to connect to DBeaver, the client gives the error: "the server's client_encoding parameter was changed to sql_ascii"

This happens to a set of servers only, and with the same client, direct connectivity is possible.

Has anyone encountered this and resolved?

 

Thanks in advance!

9 REPLIES 9

L4 Transporter

Did you check Session Diagnostics already?

Inside SIA interface

L7 Applicator

Hi @Maneesh Yatiwella​ 

 

The error message suggets that client_encoding required to be UTF8 in DBeaver to work properly.

 

Can you please check with DBeaver team whether they can set allowEncodingChanges to True?

 

Hope it helps!

Hi @Malhar Vora​ ,

 

The issue is that when connecting directly to the DB with the client, there's no issues. However, when connecting to the same DB with the same client via SIA this happens.

 

Hi @Airton Amaral​ ,

 

Yes.

Compared a working one with the one in issue as well. No hints.

 

L7 Applicator

Hi @Maneesh Yatiwella​ 

 

Can you please check whether TLS is enabled on the DBeaver ?

 

The connectivity might be failing due to TLS handshake from SIA to DB.

 

Hope it helps ‘

Hi @Malhar Vora​ ,

Yes, tried

It seems that changing anything in the DBeaver client makes no difference.

 

BR,

Maneesh

L4 Transporter

@Malhar Vora​ , @Airton Amaral​ Thanks for the input. I asked the customer to check on the PostgreSQL instances to change the settings instead of the DBeaver client. Seems it is working for the DBs we tried.

L4 Transporter

Hi @Maneesh Yatiwella​ ,

 

I’m glad to hear the issue is resolved!

If one of the replies helped you along the way, please mark it as ‘Best Answer’ to assist other community members with similar questions.

 

Thank you! Omri

Hi Omri,

 

The issue could be resolved by asking to change the settings at the PostGre SQL instance. It seems like there are some limitations with SIA for some clients even though the documentation specify only DB versions. Because all the DB that did not support were on a different version. However, as per the documentation, that version should support

 

BR,

Maneesh

  • 213 Views
  • 9 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!