Looker studio connection to postgres database

Looker Q&A Looker Studio
1

hello everyone!

i need ur urgent support please,

i’ve got my company database connection details so i can access the db now using pgadmin, but when

i try to connect it to looker studio it shows the following error :
((

Sorry, we encountered an error and were unable to complete your request.

Error ID: 796d1ee0

))

and when i try to connect my personal db that i made for test
i get this error
((

Sorry, we encountered an error and were unable to complete your request.

Error ID: bd1dc20f

))

please tell me if i miss something or any tips would be help
Thanks

2

Hi elaf,

I use the postgres connector a lot, and there are two major issues that I’ve come across that may help find your solution.

  1. Ensure that your postgresql database allows incoming connection for Looker Studio. I believe you should request from your sql admin for them to add 142.251.74.0/23 as a Authorized Network. (This would be under Connections → Summary → Security if you use Cloud SQL in GCP.)

Reminder that you should never allow people on the web to tell you to add their IP, I could be someone trying to steal your companies data. Check out the following link from google for a full answer on connecting to a postgres database and the listed IP Address range. You can also search it on Welcome to Looker Studio  |  Google Cloud to find this answer yourself if you don’t trust my link.

  1. I have found that connecting datasets with capital letters and spaces in the column names can be finicky. I recommend renaming all columns to follow (URL Removed by Staff)

Hope this helps!

Dylan

1 Like
3

Hi,

Every several weeks, we suddenly can’t authenticate postgres server in RDS with :

"Sorry, we encountered an error and were unable to complete your request.

Error ID: 5fbb2428"

I connect to the DB from python, pgadmin and basically any other tool except looker. after several hours its ok again. Has anybody faced the same issue ?

Thanks,

1 Like
4

Hi Talikted,

You posted this under another person’s thread, I suggest you ask this question on the main Looker or Looker Studio forum as a question.

Sincerely,

Dylan

5

Hi Dylan,

As this is related I thought it’ll make sense continue this one.

But will do.

Thanks,

1 Like
6

I’m having the same problem and find this so frustrating. My Postgres db is in GCP - you would think this would be quick and painless!

I’ve added the IP to the connections list. It still doesn’t work. Any other suggestions? Thanks

7

Same issue here.

I also use PostgreSQL connector in Looker Studio, and I often see the error ID: b5fe1687.
I hope the issue is resolved as soon as possible.

Thank you,

8

I would need to see both the settings for your environment and your connection information, as well as the columns in the dataset to be of any good use. I would recommend trying to follow these instructions to the T and googling how to use the postgresql connector.

Link : https://support.google.com/looker-studio/answer/7288010?hl=en&ref_topic=7332343&sjid=8314665333712265374-NC#zippy=%2Cin-this-article

9

Were you able to resolve this?

10

Buenas !

Fíjate el nombre de las tablas y columnas , normalmente es por algún carácter que pones en mayúscula o algún carácter especial.

Evita usar nombres en MAYUSCULAS .

Saludos !

11

Hi,

I just went through the same issue but managed to connect after a while.

First tip, is look at your database logs to see if you have any errors connection errors (we use AWS RDS, and the logs are available in the AWS RDS logs tab).

If there is no logs at all, it means that the connection might be blocked by a firewall, if such, add 142.251.74.0/23 to your firewall.

If there are database logs, it will usually help you.

In our case, the database error was “:FATAL: no pg_hba.conf entry for host “142.251.74.48”, …, no encryption”
This suggests that the connection was not encrypted, and after some research,
I found out that in order to connect over SSL with GoogleLooker, I need to upload the AWS SSL certificate which can be found here: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html#UsingWithRDS.SSL.CertificatesAllRegions

Hope this helps.

Jon

1 Like
12

Hey this is it actually. This helped me connect it through. Thanks a lot!!

13

At least for me, I solved this error by enabling SSL – very confusing to have Looker not simply say this was the error, and even more confusing the Looker requires you to generate your owner certificates - you can do so with this script: https://github.com/thusoy/postgres-mitm/blob/master/postgres_get_server_cert.py