Status Update
Comments
jo...@carexpert.com.au <jo...@carexpert.com.au> #2
or...@gmail.com <or...@gmail.com> #3
jo...@google.com <jo...@google.com> #4
d....@breeze.social <d....@breeze.social> #5
mi...@gmail.com <mi...@gmail.com> #6
or...@gmail.com <or...@gmail.com> #7
ja...@skira.se <ja...@skira.se> #8
d....@breeze.social <d....@breeze.social> #9
We "solved" this issue by connecting to BigQuery instead and adding our GCP CloudSQL postgres database as an external connection (see
SELECT * FROM EXTERNAL_QUERY(
'us.connection_id',
'''SELECT customer_id, MIN(order_date) AS first_order_date
FROM orders
GROUP BY customer_id''')
If BigQuery is in the same area as the postgres database, you do not pay for the transfer costs, so costs are negligible. This "solution" only works for Google Cloud Platform users, as I think only CloudSQL database are available for federated queries.
ma...@introspect.io <ma...@introspect.io> #10
al...@gmail.com <al...@gmail.com> #11
gi...@googlemail.com <gi...@googlemail.com> #12
us...@gmail.com <us...@gmail.com> #13
ma...@qesh.ai <ma...@qesh.ai> #14
pa...@odyzeo.com <pa...@odyzeo.com> #15
pa...@odyzeo.com <pa...@odyzeo.com> #16
so user for datastudio, i created custom rule in pg_hba.conf with md5 , and updated his password to md5; reverse of this tutorial:
for rest I leave scram-sha-256 (security)
jo...@makingscience.com <jo...@makingscience.com> #17
Can't reach the host. Please double check your connection parameters. Learn more about database connectors
Bu if I do the same in PSQL 12, I can connect with the DB.
em...@salevale.com <em...@salevale.com> #18
er...@gmail.com <er...@gmail.com> #19
ki...@myclearhead.com <ki...@myclearhead.com> #20
ja...@gmail.com <ja...@gmail.com> #21
ke...@banzai.org <ke...@banzai.org> #22
ch...@greyscout.com <ch...@greyscout.com> #23
nf...@gmail.com <nf...@gmail.com> #24
sv...@gmail.com <sv...@gmail.com> #25
il...@gmail.com <il...@gmail.com> #26
You need to switch authentification from scram-sha-256 to md5, probably the newer hashing is not supported yet.
I managed to get it working on Postgres 14 by following the steps listed in the comment in this thread:
jo...@carexpert.com.au <jo...@carexpert.com.au> #27
fe...@brassun.com.br <fe...@brassun.com.br> #28
hi...@elmy.fr <hi...@elmy.fr> #29
pa...@gmail.com <pa...@gmail.com> #30
ma...@gmail.com <ma...@gmail.com> #31
al...@mamrenko.name <al...@mamrenko.name> #32
ma...@fourthwall.com <ma...@fourthwall.com> #33
+1
sa...@gmail.com <sa...@gmail.com> #34
+1
wi...@medallion.fm <wi...@medallion.fm> #35
[Deleted User] <[Deleted User]> #36
[Deleted User] <[Deleted User]> #37
[Deleted User] <[Deleted User]> #38
Requesting to help getting PostgreSQL 14 in the eligible versions list.
ca...@getbamba.com <ca...@getbamba.com> #39
mu...@ambar.tech <mu...@ambar.tech> #40
[Deleted User] <[Deleted User]> #41
th...@gmail.com <th...@gmail.com> #42
ja...@agromais.cloud <ja...@agromais.cloud> #43
th...@lintendance.co <th...@lintendance.co> #44
ca...@gmail.com <ca...@gmail.com> #45
so...@gmail.com <so...@gmail.com> #46
ja...@valora.com <ja...@valora.com> #47
[Deleted User] <[Deleted User]> #48
We need this!
g....@gmail.com <g....@gmail.com> #49
ew...@gmail.com <ew...@gmail.com> #50
[Deleted User] <[Deleted User]> #51
cl...@gmail.com <cl...@gmail.com> #52
pe...@bluetrucklogistics.com <pe...@bluetrucklogistics.com> #53
jo...@gmail.com <jo...@gmail.com> #54
This is the top bug by a wide margin (137 votes vs 2nd place with 29 votes).
an...@gmail.com <an...@gmail.com> #55
ma...@gmail.com <ma...@gmail.com> #56
a....@dodobrands.io <a....@dodobrands.io> #57
[Deleted User] <[Deleted User]> #58
dr...@gmail.com <dr...@gmail.com> #59
ti...@gmail.com <ti...@gmail.com> #60
al...@livetheworld.com <al...@livetheworld.com> #61
[Deleted User] <[Deleted User]> #62
ha...@xertica.com <ha...@xertica.com> #63
+1
ri...@digible.com <ri...@digible.com> #64
mu...@bankraya.co.id <mu...@bankraya.co.id> #65
yo...@adeo.com <yo...@adeo.com> #66
na...@hyperlane.xyz <na...@hyperlane.xyz> #67
gr...@gmail.com <gr...@gmail.com> #68
ar...@ip-pilot.com <ar...@ip-pilot.com> #69
aa...@gmail.com <aa...@gmail.com> #70
aa...@wisermanagers.com <aa...@wisermanagers.com> #71
ma...@outlook.com <ma...@outlook.com> #72
[Deleted User] <[Deleted User]> #73
I consider this an important security fix since the only way to support Google Data Studio is to set the authentication method back to insecure md5.
ga...@gmail.com <ga...@gmail.com> #74
pl...@gmail.com <pl...@gmail.com> #75
[Deleted User] <[Deleted User]> #76
d....@gmail.com <d....@gmail.com> #77
d....@gmail.com <d....@gmail.com> #78
je...@proximabiz.com <je...@proximabiz.com> #79
Still not able to connect to postgres v14.
Note - works with postgres v12.
za...@gmail.com <za...@gmail.com> #80
ar...@creditsage.com <ar...@creditsage.com> #81
he...@animall.in <he...@animall.in> #82
zh...@gmail.com <zh...@gmail.com> #83
fo...@gmail.com <fo...@gmail.com> #84
em...@vapaus.io <em...@vapaus.io> #85
me...@gmail.com <me...@gmail.com> #86
vi...@allinpower.nl <vi...@allinpower.nl> #87
m....@gmail.com <m....@gmail.com> #88
vr...@gmail.com <vr...@gmail.com> #89
+1
me...@allinpower.nl <me...@allinpower.nl> #90
ma...@lowereast.nl <ma...@lowereast.nl> #91
gu...@gmail.com <gu...@gmail.com> #92
[Deleted User] <[Deleted User]> #93
cz...@gmail.com <cz...@gmail.com> #94
au...@gmail.com <au...@gmail.com> #95
jo...@gritsee.com <jo...@gritsee.com> #96
en...@varaheanalytics.com <en...@varaheanalytics.com> #97
sh...@statement.io <sh...@statement.io> #98
gy...@gmail.com <gy...@gmail.com> #99
[Deleted User] <[Deleted User]> #100
lu...@zeca.ai <lu...@zeca.ai> #101
id...@finwise.co.il <id...@finwise.co.il> #102
+1
sa...@hyll.com <sa...@hyll.com> #103
sa...@hyll.com <sa...@hyll.com> #104
lu...@amalgama.co <lu...@amalgama.co> #105
lo...@gmail.com <lo...@gmail.com> #106
mi...@gmail.com <mi...@gmail.com> #107
ni...@chefclub.tv <ni...@chefclub.tv> #108
km...@gmail.com <km...@gmail.com> #109
ce...@google.com <ce...@google.com> #110
co...@google.com <co...@google.com> #111
+1
[Deleted User] <[Deleted User]> #112
do...@gmail.com <do...@gmail.com> #113
[Deleted User] <[Deleted User]> #114
jo...@lambentdata.com <jo...@lambentdata.com> #115
ni...@aramix.ai <ni...@aramix.ai> #116
si...@gmail.com <si...@gmail.com> #117
pe...@prosit.no <pe...@prosit.no> #118
ir...@bormadago.com <ir...@bormadago.com> #119
pn...@gmail.com <pn...@gmail.com> #120
[Deleted User] <[Deleted User]> #121
Sorry, we encountered an error and were unable to complete your request.
va...@doorboost.com <va...@doorboost.com> #122
The solutions should not be downgrading authentication.
va...@doorboost.com <va...@doorboost.com> #123
You need to set a flag for password_encryption to be md5.
Edit your instance, go to flags, and add a flag, password_encryption and set it to md5.
Then you can update the password for the user you want to use for looker, and this will encrypt the password in md5.
The issue is looker auth is only supporting md5.
[Deleted User] <[Deleted User]> #124
And I also tested by adding password_encryption flags to md5.
But it doesn't still work.
[Deleted User] <[Deleted User]> #125
as...@gmail.com <as...@gmail.com> #126
om...@gmail.com <om...@gmail.com> #127
[Deleted User] <[Deleted User]> #128
I can't see how a Google product cannot support the latest connectors for the latest Postgres versions where clearly the old auth method is obsolete otherwise md5 would have been kept as the de facto standard
az...@gmail.com <az...@gmail.com> #129
om...@gmail.com <om...@gmail.com> #130
[Deleted User] <[Deleted User]> #131
ms...@globalswitchboard.io <ms...@globalswitchboard.io> #132
Seriously need this fixed.
he...@hcl.com <he...@hcl.com> #133
rg...@google.com <rg...@google.com> #134
We've added support for PostgreSQL versions 13 and 14.
If you're still having trouble connecting to those versions, please check the information in this Help Center article:
If you're STILL having trouble after checking those instructions, you can post the details on the Looker Studio Help Community:
Thanks!
zl...@google.com <zl...@google.com>
26...@gmail.com <26...@gmail.com> #135
[Deleted User] <[Deleted User]> #136
Likewise, I am still unable to connect to Postgres 14. I've posted as much information in the "Looker Studio Help Community":
`rg...@google.com` and `zl...@google.com`, I hope you'll be able to support us more directly here or escalate this to the right people, so that your hard work to support Postgres 14 can actually be used!
en...@getmasset.com <en...@getmasset.com> #137
[Deleted User] <[Deleted User]> #138
ja...@rapihogar.com <ja...@rapihogar.com> #139
ma...@paydora.finance <ma...@paydora.finance> #140
[Deleted User] <[Deleted User]> #141
ha...@stable.auto <ha...@stable.auto> #142
se...@gmail.com <se...@gmail.com> #143
Sorry, we encountered an error and were unable to complete your request.
Error ID: e820c6a7
em...@devolut.tech <em...@devolut.tech> #144
er...@gmail.com <er...@gmail.com> #145
zl...@google.com <zl...@google.com> #146
We are looking into the issue and will have an update soon.
[Deleted User] <[Deleted User]> #147
Same here. Took me a while to find out that this was the issue.
si...@google.com <si...@google.com> #148
Hi, we identified the issues and applied the fix. Now connection issue between Postgresql 14 and Looker studio should be fixed/
Thanks,
co...@therealtonystark.com <co...@therealtonystark.com> #149
ms...@friendshipshelter.org <ms...@friendshipshelter.org> #150
er...@gmail.com <er...@gmail.com> #151
co...@therealtonystark.com <co...@therealtonystark.com> #152
er...@inoquos.mx <er...@inoquos.mx> #153
om...@gmail.com <om...@gmail.com> #158
as...@gmail.com <as...@gmail.com> #159
pi...@ext.adeo.com <pi...@ext.adeo.com> #160
Sorry, we encountered an error and were unable to complete your request.
Error ID: 4b1caa17
added sll certificate and same message
With Error ID random
br...@gmail.com <br...@gmail.com> #161
Ma...@blueshieldca.com <Ma...@blueshieldca.com> #162
sa...@gmail.com <sa...@gmail.com> #163
ev...@five9.com <ev...@five9.com> #165
br...@gmail.com <br...@gmail.com> #166
ab...@searce.com <ab...@searce.com> #167
"Sorry, we encountered an error and were unable to complete your request.
Error ID: 73cbd83d"
Description
Here is the error :
Sorry, we encountered an error and were unable to complete your request.
Error ID: 9d5ae78e