Cannot Share Looker Studio Report Due to reCAPTCHA Error

Hello,

I am experiencing a persistent issue in Looker Studio when trying to share any report (public or private).

Every attempt shows this error message:

“Veuillez débloquer le service Google reCAPTCHA et réessayer.”

(“Please unblock the Google reCAPTCHA service and try again.”)

Here is what I have already tried, without success:

  • Tested multiple browsers (Chrome, Safari, Edge)

  • Tested multiple devices (iPad, iPhone, Windows PC)

  • Tested multiple networks (home, mobile, company)

  • Tested with and without incognito mode

  • Tested a brand-new empty report → same issue

  • Deleted cookies/cache and ensured all Google domains are allowed

  • No other Google accounts logged in

  • Issue persists for several days

This happens even on a brand new empty report, so it seems related to my Google account being stuck in a CAPTCHA_REQUIRED state.

Could someone from Google reset/unblock my CAPTCHA status so that I can share Looker Studio reports again?

Thank you!

4 Likes

I’m having the same issue, and this has started happening recently. It was working fine before. Any help would be appreciated. Thanks!

1 Like

Did you have any resolution to this? I am having the same problem and have no idea where to go from here.

1 Like

The same here! Help

1 Like

I have the same issue u.u

1 Like

Same issue here. To add, when troubleshooting I asked a remote coworker to try sharing a report (within the same account) and they didn’t get this issue. Can anyone replicate this? If so, then could the problem be location based (possibly a Google blocking IP situation)? Hopefully we get a solution soon. :folded_hands:

1 Like

I do too have the same issue. Please help.

1 Like

Same here

1 Like

Open console.

It will likely throw a CORS error; you should copy the JavaScript code from the reCAPTCHA file and paste it into the console.

1 Like

Looks like that’s it. There is an error with “Reason: CORS header ‘Access-Control-Allow-Origin’ missing” being logged.

1 Like

same issue

1 Like

Same issue here

1 Like

Hi everyone,
i’ve been experiencing the same issue over the past few days. I eventually managed to resolve it by switching to a different computer and a different network. From there, I was able to assign roles to the report without any problems. I also tried disabling the VPN and changing browsers, but that didn’t help. The only solution that actually worked was using another computer on another network. Hope it helps.

1 Like

3 days now, multiple devices. It’s locked on private link and I can’t edit any share settings without the Captcha error. Zero support from Google. What is happening! All our companies reports are down.

1 Like

I am also facing the same issue. Deeply frustrating that Google has no resolution.

1 Like

As a few mentioned here, it seems to be machine/OS related bug. I managed to share the reports again by doing it via a Windows machine with Chrome browser. All my Apple devices still show the Recaptcha error, regardless of browser, network.

Hopefully this will help some of you until Google fixes this (if at all).

2 Likes

Having the same issue with Looker for 2 days already - can’t share reports, both old or new ones.

  • Tested multiple browsers (Opera, Chrome, Firefox) and different networks (haven’t tried a new device so far)
  • Tried incognito mode
  • Tried changing the time zone
  • Cleaned cookies/cache, everything
  • Enabled Java in browser
  • Turned on and off VPN

It’s frustrating and weird. Also this happened after the latest Google’s core update launch, so I wonder if this could be connected.

There seems to be a general problem with sharing Looker reports if my account is the Owner - not only sharing access from my behalf.

I asked another person (say, person A) who was previously added by me as an Editor, to share access to my report to a new person (person B). The Editor (person A) was successful to send access, but the new person (person B) could not view the report anyway.

Hope it gets fixed any time soon…

Hi everyone. Apologies for the trouble here. We’ve taken steps to mitigate the problem. Can you let us know if this issue is still happening?

2 Likes

My colleagues and I experienced the same issue, and it was resolved after updating our Chrome browser (142.0.xxx or later).

@Rick_E Thank you - works for Opera / Windows now. :star_struck:

Didn’t update anything since yesterday.

1 Like