Loop log in

Hi @misdim,

Thanks for reaching out, and for sharing your Site Health information. As nothing obvious stands out at this point from reviewing the details please share the following:

1. At any stage do you recall migrate your site or change your site URLs, or your wp-admin URL? If so it’s possible that you were connected to Site Kit with this previous URL before any such change.
2. What is the final URL you land back on when you’re redirected to your wp-admin screen? I ask as it’s possible that a previous plugin set up may have been on a different site URL or wp-admin URL, and this may be references within this address.

Let me know if you have any queries with the above. Looking forward to hearing from you.

Hi James!

Thanks for the quick response!

1. The URLs are the same from the development of the site and this is the 1st time I installed the Google Site Kit and tried to connect it.

2. When I click on the Verify, button it is redirecting me to log in again here:

https://****.gr/wp-login.php?redirect_to=https%3A%2F%2F****.gr%2Fwp-admin%2Findex.php%3Faction%3Dgooglesitekit_proxy_exchange_site_code%26googlesitekit_code%3Dsitekit-***********ode%26googlesitekit_site_code%************%26nonce%************%26step%3Dverification&reauth=1

After typing the credentials, it is redirecting me on the link bellow, with this message “The link you followed has expired.
Please try again.”

https://*****.gr/wp-admin/index.php?action=googlesitekit_proxy_exchange_site_code&googlesitekit_code=sitekit-****ode&googlesitekit_site_code=****&nonce=****&step=verification

And when I click on “Please try again” it takes me to the Site Kit dashboard but it is not connected and the loop starts again.

(I am not sure if it is safe for the links to be public so I added some ****. Let me know If you need the whole links)

Thanks again!

Many thanks for sharing this update. Based on your update this indicates that incorrect site URLs on the Site Kit service are not the result of your set up loop, in particular as this is the first time you’ve attempted Site Kit set up.

As I suspect this may be related to your hosting set up please share a screen recording of your set up experience, using a service such as Loom or RecordIt. Within the screen recording please display the following:

1. Your Site Health status (Tools > Site Health > Status), which differs from your Site Health information that you previously shared. This can indicate any REST or cURL related error.
2. Any XHR response you encounter when attempting Site Kit setup.

When attempting Site Kit set up and demonstrating the above please do so from a Chrome browser incognito window. I ask as there can be sometimes browser related features or extensions that impact set up.

You can share the screen recording above using the same form previously used to share your Site Health information.

An alternative to sharing a screen recording above, is to attempt Site Kit set up using another WordPress site on the same hosting platform.

Let me know if you have any questions with the above.

Just shared via the form a recording of my screen with the issue and the Health status using an incognito window.

Hope it helps!

Appreciate you going to the effort of sharing this @misdim.

From reviewing the video I don’t see any invalid XHR response after you’re redirected. To try to determine the cause let’s perform the steps below, which will help rule out any third party plugin or theme conflicts, while also resetting any possible incorrect site reference URLs on the Site Kit service (for your site).

1. Reset the plugin (Tools > Available Tools > Reset Site Kit)
2. Install and activate the Health Check & Troubleshooting plugin.
3. Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
4. 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”
5. Attempt to setup Site Kit once more

You can exit troubleshooting mode afterwards.`

If the same occurs please share whether you see any browser console errors when you encounter the “The link you followed has expired” error. I’ll then check this with the team.

Tried the steps you described above but the result is still the same.

There is an error (403) at the console at the “The link you followed has expired” page:

GET https://****.gr/wp-admin/index.php?action=googlesitekit_proxy_exchange_site_code&googlesitekit_code=sitekit-****&googlesitekit_site_code=****&nonce=****&step=verification 403

I also just installed Site Kit for the 1st time on a different domain on the same server and I get the same error and loop there too.
Although I have other domains on the server with Site Kit and it works great.

Many thanks for sharing these insights, including testing on another site on the same service. This looks similar to hosting related issues we’ve encountered previously, with hosting or CDN configurations the cause.

So we can collect all insights you’ve kindly provided while I discuss this with the team I’ve created a GitHub issue for this, which you can find here.

There are a couple of things you may wish to check, while you await me discussing this with the team. Some of these are listed within that issue I created for you, and include the following:

1. Checking Site Kit set up from another device
2. Checking for any differences between the sites that have Site Kit successfully connected, compared to the ones that didn’t. This may include PHP and cURL versions.

I’ll discuss your case with the team early next week. Feel free to add any insights between now and then if you wish, or add comments to the related GitHub issue. Thanks for your patience on this, hopefully we can determine the cause!

Great!!

I checked for differences between a site with a working Site kit and this one and they don’t have any.
They both have:
– Theme: Avada 7.7.1
– WordPress: 6.0
– PHP: 7.4.30
– cURL: 7.64.0

I unistalled and re-installed the plugin but with no result.
I also checked the logs from ModSecurity 2.9. You can see them bellow:

2022-06-20 11:18:04 Error .078273 [NOTICE] [21726] [T1] [94.71.4.194:27701-H3:482E66507C0C8353-8#APVH_****.gr:443:MODSEC] mod_security rule [id “33308”] at [/etc/apache2/modsecurity.d/rules/custom/002_i360_1_vectors.conf:15] triggered!

2022-06-20 11:18:35 Error .119993 [NOTICE] [21726] [T2] [94.71.4.194:27701-H3:482E66507C0C8353-348#APVH_****.gr:443:MODSEC] mod_security rule [id “33308”] at [/etc/apache2/modsecurity.d/rules/custom/002_i360_1_vectors.conf:15] triggered!

I switched off security rules with the ids “33332” & “33308” and tried again. In this case I dont get the errors in ModSecurity that I sent you above but the result is the same.
I also deactivated ModSecurity 2.9 but no result again.

Thanks again for your time!

• This reply was modified 2 years, 5 months ago by misdim.

Many thanks for sharing these insights! Interesting that there were some errors highlighted within your Modsecurity logs, and with the same experience with ModSecurity disabled. I’ve added these notes to the related GitHub issue, and I hope to have an update for you today after discussing this with the team.

Note also that what might be useful while the team review the GitHub issue is to share your Site Health information for the other site on the same server, where you mentioned you are experiencing the same redirect, on a first time Site Kit setup.

Regardless of the above I should have an update for you at some stage today.

Many thanks for your patience on this. I’ve discussed your case with the team and they don’t see anything obvious on the Site Kit service, used to connect your site and Google account with Google services.

As nothing stood out we suspect there may be something at host level blocking set up from this site. To try and determine more we can use Chromes Developer Tools, which may help indicate a connection break that isn’t visible from the videos you kindly shared previously.

In order to do so please follow the steps below:

1. Open a Chrome browser incognito window
2. Open the Chrome Developer Tools
3. Open the Network tab and ensure you have the “Preserve Log” option enabled
4. Attempt Site Kit set up once more
5. Check for any non 400 or non 200 error status within after you’re logged out of your site, by reviewing all the entries in the log.

Let me know if you spot anything unusual once you’re recording all events, using the steps above. You can also share a screen recording once more of your experience, using the same form previously used to share privately.

Let me know if you have any questions with the above.

Just went through the steps you described above and tried to connect the Site Kit.
All the entries at the network tab have status 200. (Incognito and preserve log: on)

You think I sould contact my server hosting company?

Many thanks for checking this. Reaching out to your hosting provider may be useful, given the checks we’ve already performed.

There are a couple of other checks you can perform yourself at host level. One is to check your PHP version and configurations, and the other is to set up a new clean WordPress install, and check Site Kit set up from this site.

Let me know how you get on with the above.

I contacted my hosting provider and informed them about the problem and the steps that we’ve tried and they will check it.
I’ll let you know when I have an answer from them.

Many thanks for the update. And sure, let us know if you get any feedback from your hosting provider.

As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.