Sign in loop

  • Resolved bwstefano

    (@bwstefano)


    4 years ago

    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]

Viewing 14 replies - 46 through 59 (of 59 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    @brmagrini I’ve created a GitHub issue from which I’ll discuss your case with the team. In the meantime can you confirm that the same occurs when using a different Google account to setup the plugin – a non Google Workspace account, and at what stage you’re redirected during the setup process?

    Done. If you can think of any header that might be blocker by nginx let us know.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing. The URL in your Site Health information doesn’t match the subdomain URL provided previously, https://kitinfoamazonia.hacklab.com.br and https://kit.infoamazonia.org. Can you share what way you’ve setup this site and which clean install you would like to work from?

    In additional to confirming the site URL please confirm that the same redirection occurs when using a different Google account to setup the plugin – a non Google Workspace account, and at what stage you’re redirected during the setup process?

    We don’t have another environment, but, in case I’ve sent the wrong site’s information, I’ve sent it again now through the form.
    Information from this site:
    kitinfoamazonia.hacklab.com.br
    Thanks

    Plugin Support James Osborne

    (@jamesosborne)

    We’ll use that one to discuss with the team so, thank you. Can you please also answer the below:

    confirm that the same redirection occurs when using a different Google account to setup the plugin – a non Google Workspace account, and at what stage you’re redirected during the setup process?

    I ask because in a previous video sent for the initial site I noticed the email in use looks like a Google Workspace email. If you can share the above, and at what stage you’re redirected it would be most helpful. You can share a video or screen recording using a service such as Loom or Recordit.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing the video, useful to see what’s occurring. While I’m awaiting an engineer check of the details in the GitHub issue I’ve created here’s one more check you can perform:

    1. Create a new administrator account within that WordPress install
    2. Login to your site from a Chrome browser incognito window
    3. Reset Site Kit (Tools > Available Tools > Reset Site Kit)
    4. Setup Site Kit once more, using a non Google Workspace account

    If the same occurs please share whether you find any critical errors when checking your Site Health status.

    Plugin Support James Osborne

    (@jamesosborne)

    Many thanks for your patience on this. I’ve had an engineering review your experience and there may be a host level redirect impacting setup or it could be a case that only certain headers or query parameters are being allowed.

    For the next steps we’re happy to check your hosting provider on our side. Can you confirm the hosting and plan currently used?

    We use a custom server, with kubernetes and docker, using nginx ingress to manage external access to http services. If you could specify what information would be relevant to you I’ll be glad to answer.

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @brmagrini,

    Unfortunately I don’t have much insights on any possible ingress nginx configurations or possible conflicts. I’m happy to escalate this once more to our engineering team if you can confirm the same occurs with any WAF or security features temporarily deactivated which you may be aware of.

    Alternatively feel free to comment within the existing GitHub issue, with Adam happy to review your existing setup or error logs.

    Thanks @jamesosborne , I’ve commented on the github issue. There is no other WAF or security features in this test environment, but I’ll keep investigating the ingress rules that could be leading to this and following the github issue.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update. Please do share any additional findings with hosting configurations should you be able to proceed.

    Plugin Support James Osborne

    (@jamesosborne)

    @brmagrini Just following up with you to check if you’ve had time to troubleshoot this from your hosting setup?

    @bwstefano Just following up here that upon further review and discussion with our team, this appears to be an issue with your hosting provider that unfortunately isn’t something that we can address on the Site Kit side of things. I’m marking this issue as resolved, but if you have any additional questions about Site Kit, feel free to create a new topic. Thank you!

Viewing 14 replies - 46 through 59 (of 59 total)
  • The topic ‘Sign in loop’ is closed to new replies.