Hi there @jjacoberger,
Thanks for reaching out, and also sharing details of the troubleshooting efforts you’ve undertaken. As we’re currently investigating reports of this it would be great if you could share the following:
- Your Site Health information. Within the form please include your current hosting provider.
- When checking the Site Kit dashboards from a Chrome browser incognito window do you see any browser console errors on the same screen where this notice appears? If so please share any such errors.
- Would it be possible for you to share a screen recording of your experience setting up the plugin, that shows your full experience? You can use a service such as Loom or RecordIt to share. Feel free to include this in the above Site Health information form.
Let me know if you have any questions with the above. Once we have this information we can investigate this further or provide you with some troubleshooting suggestions, which may include attempting setup from another site on the same hosting platform or using another Google account to attempt setup.
@jjacoberger Out of curiosity are you using a specific browser to attempt setup? If so please check does the same occur from a Chrome browser.
Thread Starter
JohnJay
(@jjacoberger)
I completed your form as requested. I received the same error using Chrome, Edge and Brave.
I was finally able to complete the setup using Firefox in Incognito mode.
Many thanks for sharing, and glad to hear you’ve been able to successfully connect using Firefox. I’ve checked your details and as nothing stands out I suspect this may be browser specific. By any change do you have other WordPress sites where you can check for the same setup experience with, using the Brave and then Chrome browser?
Thread Starter
JohnJay
(@jjacoberger)
Yes, I have several other sites – I can try them later on this afternoon and let you know what happens.
That would be great, thank you! We’re curious to know if the same always occurs with the Brave browser while then on the same sites does the same occur when switching to Chrome in particular.
@jjacoberger Just following up with you to check whether you’ve had an opportunity to check your other sites for the same error?
Thread Starter
JohnJay
(@jjacoberger)
I actually finally did last evening – sorry for the delay but serious life events interfered.
On the first site:
- I was using the Brave Browser
- I entered the Google account and password to connect
- I agreed to continue granting access to the account
- I received the error
- I logged into the site Admin Dashboard again using Chrome
- I followed all prompts to connect to the Google account
- I received the error again
- I logged into the site using Firefox
- I followed all the prompts enter login credential and connect to the Google account
- I connected Site Kit successfully with Firefox
On the second site:
- Site Kit had been connected to a Google Account so I disconnected it and reset Site Kit
- Trying to reconnect, I went through all the same steps with the same experience as on the first site
On the third site:
- Using the Brave browser, I was able to Connect Site Kit with a Google account successfully the first time I tried.
Interestingly, the first and third sites, where one was successful on the first try and the other was not, are exact duplicates of each other hosted by the same company.
Many thanks for the update, and no problem about the delay. I hope all is well regarding your reasoning.
In relation to the first and third sites there is a particular configuration within the Brave browser which we’ve been able to recreate the same error message with when enabled (Shields > Look and feel > Auto-redirect AMP pages). I wonder did you have this enabled at any stage. I can’t be sure why the results were inconsistent, however, it’s possible this configuration may not always trigger or detect AMP URLs.
On the second site do you recall whether you were using the Brave browser when you encountered this error? If so please share whether you were able to successfully connect when switching to Chrome.
Thread Starter
JohnJay
(@jjacoberger)
Yes, on the second site, I received the error using brave. After I got the error with Brave, I switched to Chrome and got the same error. I connected on the third attempt with Firefox.
Many thanks for the update. I’ll add your notes to the related GitHub issue, where we’ve been adding details on this error, which other users also reported.
While I’ll close this support topic now given you’re successfully connected please inform me if you have any AMP related Chrome browser extensions active, such as the Redirect AMP to HTML extension.
I ask as the error you’re encounter is something we’ve been able to recreate using such extensions, or browser related configurations regarding AMP.
Thread Starter
JohnJay
(@jjacoberger)
I do not have any AMP extensions installed or active.
