Sign in loop

Thanks for getting in touch, and sorry to hear you’ve been unable to proceed with setup. As you’ve moved from a subdomain you may be correct, the site registered on the Site Kit service differs to your current URL.

Before requesting a reset can you attempt the steps below, which can allow the service to recognize your new URLs?

1. Temporarily switch your “WordPress Address (URL)” and “Site Address (URL)” from https://infoamazonia.org to https://www.infoamazonia.org in your WordPress General Settings configuration. (adding the www)
2. Log back into your site once requested and then undo the changes you made (reverting back to the full address without www)
3. Open a browser incognito window
4. Attempt setup once more

Please let me know if that works for you. If that fails please share your previous subdomain based URL and I’ll request a reset of your site. I’m curious to know also if you still have access to that subdomain based setup.

Hi @jamesosborne, sorry for the delay. That unfortunately didn’t work. The previous URL was https://dev.infoamazonia.org which we also changed to add the www to it and perhaps find a way around it on that subdomain, but we had no luck in it as well.

As far as I can recall I might have registered the plugin with https://dev.infoamazonia.org just to test and removed it afterwards. Now I can’t register it again in any of these two environments…

Thanks for the update and providing the additional details. It does indeed sound like a previous domain was registered on the Site Kit service. I’ve requested a reset now so I’ll keep you updated here as soon as I have an update.

We’re also working on making changes to allow for resetting sites on the service for such scenarios.

Hi @jamesosborne. Thanks for this. Were you able to do the reset already?

@bwstefano I didn’t hear back just yet but let me request an update now. I’ll hopefully have an answer for you today.

@bwstefano We’ve now reset the site registered on the Site Kit service – https://dev.infoamazonia.org. Can you try once more to connect Site Kit and inform me if it works?

Hi @jamesosborne, it didn’t… But it might also be worth mentioning I’m not trying to use Site Kit with https://dev.infoamazonia.org. That was the testing environment. We want to use it with https://infoamazonia.org.

Sorry to hear that. There was a record of dev.infoamazonia.org on the Site Kit service and resetting this site reference would normally allow you to proceed with https://infoamazonia.org in cases whereby you may have migrated to your newer domain without resetting Site Kit.

As a site reset didn’t work if you want to share your Site Health information privately via this form I can inspect your setup to check for any possible plugin or hosting environment incompatibilities. If you have any other WordPress sites on the same hosting platform I’m curious to also know if you’re able to complete Site Kit setup with any of these sites.

Thank you, James. I’ve just filled the form.

Many thanks for sharing and providing the additional site setup information. There do seem to be plugins that could potentially impact Site Kit setup, in particular if you migrated from a staging site.

While we investigate this internally you may wish to attempt setup following the steps below:

1. Install and activate the Health Check & Troubleshooting plugin.
2. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
3. From the same screen click on the “Available Plugins” tab at the top right and then click on the “Enable” option next to “Site Kit by Google”
4. Attempt to setup Site Kit once more

Please inform us if the experience you encounter is the same as initially experienced, looping back at a particular stage (ie. Clicking on the “Sign in with Google” button)

Hi James, just did these steps but had no luck yet… Nothing has changed after trying the Health Check & Troubleshooting, unfortunately.

Sorry to hear that. While being mindful of asking you to perform more troubleshooting steps would it be possible for you to share this experience with Chrome developer tools enabled, highlighting any console errors? That way we may be able to determine what’s occurring and I can escalate this or create a GitHub issue if appropriate.

You can use a service such as Loom or RecordIt to share any video recording, while using the same form previously used if you prefer to share privately.

@bwstefano We’ve located another possible staging site reference on your site now and reset it. Do you mind trying to reconnect one more, it would be great to hear if you can finally connect.

Hi again, @jamesosborne. Unfortunately that still didn’t work. I’ve filled the form again, adding current Site Health Info and a link to a screen recording I made while trying to connect it again after clearing Chrome’s cache and cookies, logging in to my WordPress and Google accounts, resetting Site Kit on WordPress, and removing its permissions from my Google account. I couldn’t see any relevant message at the browser’s console, but perhaps you are able to spot I didn’t.

If you need I can also create a temporary account at our WordPress so you can evaluate it by yourself, in case you don’t see any other measure or troubleshooting I could take.

Many thanks for providing the additional insights, I can see multiple console errors output during setup and with this I’ll create a GitHub issue so we can investigate this further.
https://github.com/google/site-kit-wp/issues/2924

If you need I can also create a temporary account at our WordPress so you can evaluate it by yourself, in case you don’t see any other measure or troubleshooting I could take.

Unfortunately we’re unable to access users sites as per WordPress support forum guidelines. I appreciate the troubleshooting steps you’ve taken undertaken so far and I’m uncertain if any action can be taken on your side that will allow you to proceed. You may wish to attempt Site Kit setup with another email, I’m curious if that makes a difference. Regardless I’ll update you here as soon as I’ve spoken with the team or as soon as I have an update on this.