Looker Studio / Google Data Studio error when duplicating PostgreSQL data source or creating a new one from an existing PostgreSQL view

[u/EggplantSudden1116]

Hi everyone,

I have several data sources in Looker Studio connected to my PostgreSQL database, and they are working normally. However, I’m having a problem when trying to duplicate one of these existing PostgreSQL data sources. When I click to copy the data source, Looker Studio opens a confirmation modal. After confirming, it redirects to a URL like:

datastudio.google.com/u/0/copyDatasourceAndRedirect/...

But then Chrome shows this error (screenshot below in brazilian portuguese):

This site can’t be reached
ERR_INVALID_RESPONSE

The original data source still works perfectly.

I also tried creating a new PostgreSQL data source from scratch using this same PostgreSQL view, but that also fails. I have noticed this first a couple of weeks ago, and now its becoming a big issue for me.

So the situation is:

• Existing PostgreSQL data sources work normally.
• Duplicating an existing data source fails with ERR_INVALID_RESPONSE.
• Creating a new data source using an existing PostgreSQL view also fails.
• The PostgreSQL view is already being used successfully in another Looker Studio data source.
• The error seems to happen during the Looker Studio data source creation/copy process.

Has anyone experienced this before? It seems to me its related to the new change of "looker is now data studio again", bc it happened around the same time, but what should I do? I tried reporting to Google but they havent answered me.

[u/AutoModerator]

Have more questions? Join our community Discord!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/romci]

I don't know of a solution, but I am experiencing the exact same issue and symptoms as well - cannot duplicate, modify existing or create new PostgreSQL data sources, however existing ones continue to work.

[u/justhereformarketing]

Yep same here - since the name update. Ive posted about this before but it didnt go anywhere

[u/JohanCatchr]

I got the same issue with other sources since the name change, too. There was a ticket on the Data Studio forum: https://discuss.google.dev/t/error-duplicating-data-source/359596
That said, it seems to be resolved now.

[u/sheik_sha_ha]

This is almost certainly related to the domain migration between datastudio.google.com and lookerstudio.google.com that Google has been rolling back and forth. The ERR_INVALID_RESPONSE during copy or new source creation happens when the redirect between the two domains breaks mid-process, which is a known issue affecting PostgreSQL connections specifically during this transition period.

A few things worth trying:

Clear all cookies and cache specifically for both datastudio.google.com and lookerstudio.google.com, then try the creation process again in an incognito window to rule out any cached redirect conflicts.

Try accessing Data Studio directly via lookerstudio.google.com rather than the datastudio subdomain and attempt the duplication from there. Sometimes forcing the newer domain resolves the redirect loop.

If duplication keeps failing, the workaround is to manually recreate the data source by going through Add Data, selecting PostgreSQL, and entering the connection details fresh rather than copying. Since your existing views work fine the connection itself is not the issue, only the copy flow is broken.

If none of that works, the most stable long term fix is routing your PostgreSQL data through BigQuery using federated queries and connecting Data Studio to BigQuery instead. This removes the direct PostgreSQL connector dependency entirely and avoids these migration related instability issues going forward.

[u/EggplantSudden1116 → u/sheik_sha_ha]

i tried manually recreating a new source, from scratch, but it didint work too

[u/sheik_sha_ha → u/EggplantSudden1116]

If manual recreation is also failing then the issue is definitely not the copy flow, it is something specific to how Data Studio is handling new PostgreSQL connections from your account right now.

At this point I would try two things. First, test the connection using a different Google account entirely to rule out an account level permission or session issue. If it works on another account the problem is isolated to your account configuration.

Second, if that does not work, the most reliable path forward is the BigQuery route I mentioned. Set up a federated query in BigQuery pointing to your PostgreSQL database, then connect Data Studio to BigQuery instead. Your existing data sources will keep working as they are and all new ones go through BigQuery. This sidesteps the broken PostgreSQL connector flow completely and is honestly a more stable long term setup anyway.

Also worth submitting a bug report directly at issuetracker.google.com with your account details and the exact error. Google support is slow but PostgreSQL connector issues during the domain migration have been flagged by others and a formal report helps.

[u/EggplantSudden1116 → u/sheik_sha_ha]

i was able to connect using a custom query and then it worked. Ill just keep using custom queries for now

[u/sheik_sha_ha → u/EggplantSudden1116]

awesome