Sign in loop
-
We are having the same issue detailed on this topic. The sign in page is in a loop and we can’t finish setting the plugin. We’ve recently changed the URL, removing a subdomain from it as the website was in a testing environment before being moved to production. Perhaps a site reset on Site Kit’s service would help?
I’ve already removed the plugin, disconnected the service from my Google account, and redo all steps again, but had no luck. I also tried using a different browser. The version installed is the latest one already, but I had to disabled it to provisionally use a different Analytics plugin so we don’t miss logging our audience numbers.
The page I need help with: [log in to see the link]
-
One other check which may prove useful is to set your Cloudflare configuration to “Development Mode“, as it looks like you have your DNS records pointing to their servers.
Let me know if you need assistance on performing this check. After doing so please inform me if you encounter the same issue.
Hi James, our staff will start a clean environment at their server next week. I’ll let you know once I test Site Kit on it. Meanwhile, I did try setting Site Kit one more time at geojournalism.org with the Development Mode in Cloudflare enabled, but had no luck.
That’s great, looking forward to hearing from you in relation to a clean install.
Hey @bwstefano ,
Its just a follow-up message – did you get a chance to setup fresh WordPress version along with Site Kit on the same server?
We are trying to to reproduce this issue at our end. Your valuable input on this issue will be helpful for us to escalate this issue.
Best Regards,
Thanks, @abdullahramzan. We weren’t able to setup a fresh WordPress yet, but our team will have it done by next week and I’ll update you after I test Site Kit on it.
Hi Abdullah, James,
We’ve set a new, clean testing environment at https://kit.infoamazonia.org/ and the issue happened again.
Well, the environment started with WordPress 5.4.4 and I’ve installed Site Kit before doing anything else. I went to configure Site Kit and saw a message stating that “Site Kit cannot access WordPress REST API”. It would allow me to proceed anyway, so I did. After that, I’ve tried to set and got stuck in the same sign-in loop problem I had with the other two websites that I’ve set in this server and which I brought above.
After that I updated WordPress to version 5.7.1, removed the two other plugins that came with it (Akismet and Hello Dolly), removed the other themes that came with it, and updated the theme Twenty Twenty-One. Then I tried with Site Kit again and the message above wouldn’t show up anymore, even after resetting Site Kit. Still, the sign-in loop issue remained.
I’ve also checked Site Health and WordPress states it’s passing on all tests.
With that, I think we can bet the problem is in the environment where these three environments are set, right? So which details or tests would you need us to do to evaluate and fix whatever is wrong here?
Many thanks for going to the trouble of setting up a test site. The WordPress REST API is required during setup in order to communicate with the Site Kit service. In such cases it’s normal that you can only get so far when attempting setup with such restrictions.
Can you share the current hosting provider for this site, I don’t see it referenced in the last form you provided. I can see if I can find out more information on whether there are any restrictions.
Hello @jamesosborne, I’m working with @bwstefano to solve this problem.
Wordpress API is working properly, in this public endpoint, for example, we can see the public users list: https://kitinfoamazonia.hacklab.com.br/wp-json/wp/v2/users.
I’ve changed the url as a test to see if it wasn’t any cloudflare settings but we are still experiencing the same problem.
I’m thinking that the problem my be related to our ingress-nginx configurations that might be preventing some header forwarding or something like that. We are trying to debug this here but if you can think of something related to this please share with us.Hi @brmagrini, thanks for providing an update. The REST endpoints now seem available for the original site also, so you’re correct, that rules that out. As you can’t proceed with the clean WordPress install you can perform the following WP CLI command providing you have WP CLI setup:
wp eval 'print_r(wp_remote_head("https://sitekit.withgoogle.com"));
Alternatively you can use the below command from your host terminal:
curl -I https://sitekit.withgoogle.com
Let me know the status of either of the above.
The response for the first command:
Array ( [headers] => Requests_Utility_CaseInsensitiveDictionary Object ( [data:protected] => Array ( [content-type] => text/html; charset=utf-8 [vary] => Accept-Encoding [content-encoding] => gzip [x-cloud-trace-context] => 9613e804cbd6a2768993ffe57dccb2f1 [date] => Tue, 25 May 2021 00:21:22 GMT [server] => Google Frontend [cache-control] => private [alt-svc] => h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" ) ) [body] => [response] => Array ( [code] => 200 [message] => OK ) [cookies] => Array ( ) [filename] => [http_response] => WP_HTTP_Requests_Response Object ( [response:protected] => Requests_Response Object ( [body] => [raw] => HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Content-Encoding: gzip X-Cloud-Trace-Context: 9613e804cbd6a2768993ffe57dccb2f1 Date: Tue, 25 May 2021 00:21:22 GMT Server: Google Frontend Cache-Control: private Transfer-Encoding: chunked Alt-Svc: h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" Connection: close [headers] => Requests_Response_Headers Object ( [data:protected] => Array ( [content-type] => Array ( [0] => text/html; charset=utf-8 ) [vary] => Array ( [0] => Accept-Encoding ) [content-encoding] => Array ( [0] => gzip ) [x-cloud-trace-context] => Array ( [0] => 9613e804cbd6a2768993ffe57dccb2f1 ) [date] => Array ( [0] => Tue, 25 May 2021 00:21:22 GMT ) [server] => Array ( [0] => Google Frontend ) [cache-control] => Array ( [0] => private ) [alt-svc] => Array ( [0] => h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" ) ) ) [status_code] => 200 [protocol_version] => 1.1 [success] => 1 [redirects] => 0 [url] => https://sitekit.withgoogle.com/ [history] => Array ( ) [cookies] => Requests_Cookie_Jar Object ( [cookies:protected] => Array ( ) ) ) [filename:protected] => [data] => [headers] => [status] => ) )
The responde for the second command:
HTTP/2 200 content-type: text/html; charset=utf-8 vary: Accept-Encoding x-cloud-trace-context: 337d02bad074e5905973a1b27b1a6fce date: Tue, 25 May 2021 00:22:47 GMT server: Google Frontend alt-svc: h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
Thanks for the update. The raw connection for your origin host seems fine. Going back to the site you setup – https://kit.infoamazonia.org can you perform the following checks on this site:
- Login to your site from a Chrome browser incognito window
- Install and activate the Health Check & Troubleshooting plugin.
- Navigate to “Plugins > Health Check & Troubleshooting > Troubleshoot”.
- 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”
- Attempt to setup Site Kit once more
You can exit troubleshooting mode afterwards.
If the same occurs on this test site please install the REST API Log plugin and before attempting setup once more. You can then share any non 200 responses from “Tools > Rest API Log”.
With the health-check plugin the result was the same.
after installing REST API Log plugin and trying again it generated no logs on REST API Log Entries.That’s interesting. Do you have WP Cli setup? If so you can run the below command:
wp eval 'print_r(wp_remote_head("https://sitekit.withgoogle.com"));'
The above is an alternative test to the cURL command previously checked.
Array ( [headers] => Requests_Utility_CaseInsensitiveDictionary Object ( [data:protected] => Array ( [content-type] => text/html; charset=utf-8 [vary] => Accept-Encoding [content-encoding] => gzip [x-cloud-trace-context] => ba7188ac1a46ea52378867f5930e6154 [date] => Thu, 27 May 2021 13:31:34 GMT [server] => Google Frontend [cache-control] => private [alt-svc] => h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" ) ) [body] => [response] => Array ( [code] => 200 [message] => OK ) [cookies] => Array ( ) [filename] => [http_response] => WP_HTTP_Requests_Response Object ( [response:protected] => Requests_Response Object ( [body] => [raw] => HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Content-Encoding: gzip X-Cloud-Trace-Context: ba7188ac1a46ea52378867f5930e6154 Date: Thu, 27 May 2021 13:31:34 GMT Server: Google Frontend Cache-Control: private Transfer-Encoding: chunked Alt-Svc: h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" Connection: close [headers] => Requests_Response_Headers Object ( [data:protected] => Array ( [content-type] => Array ( [0] => text/html; charset=utf-8 ) [vary] => Array ( [0] => Accept-Encoding ) [content-encoding] => Array ( [0] => gzip ) [x-cloud-trace-context] => Array ( [0] => ba7188ac1a46ea52378867f5930e6154 ) [date] => Array ( [0] => Thu, 27 May 2021 13:31:34 GMT ) [server] => Array ( [0] => Google Frontend ) [cache-control] => Array ( [0] => private ) [alt-svc] => Array ( [0] => h3-29=":443"; ma=2592000,h3-T051=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" ) ) ) [status_code] => 200 [protocol_version] => 1.1 [success] => 1 [redirects] => 0 [url] => https://sitekit.withgoogle.com/ [history] => Array ( ) [cookies] => Requests_Cookie_Jar Object ( [cookies:protected] => Array ( ) ) ) [filename:protected] => [data] => [headers] => [status] => ) )
-
This reply was modified 3 years, 10 months ago by
brmagrini.
Many thanks for sharing the additional information, all looks good from that check also. I’ll discuss this with the team once more and report back to you here. In the meantime can you please share your Site Health information using this form based on the https://kit.infoamazonia.org site?
- The topic ‘Sign in loop’ is closed to new replies.