Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @soberpaddy. So we can determine what may have happened to result in this behavior, and ensure you can complete set up, please share the following:

    1. Your Site Health information. You can use this form to share privately if preferred.??
    2. Did you have Site Kit setup successfully on this site previously? This may include on a previous domain before a site migration, or prior to any changes to the site.

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

    Thread Starter soberpaddy

    (@soberpaddy)

    Hi @jamesosborne

    1. I have submitted the Site Health using that form.
    I have caching turned off on the site in case that was causing some kind of issue.

    2. This is the first install of SiteKit on the website.

    Let me know what are the next bets steps!
    CHeers
    John

    Plugin Support James Osborne

    (@jamesosborne)

    Many thanks for sharing the additional information. From checking the details I don’t notice anything obvious that may be causing this redirect. What we can do first of all, is ensure there are no browser or third party plugin related blocks. In order to do so, please follow the steps below:

    1. Login to your live site from a Chrome browser incognito window.
    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

    Let me know how you get on with the above. Should the same occur, please share any browser console errors on the page where you land back on. At that stage we may need to perform some checks for possible host level blocks.

    Thread Starter soberpaddy

    (@soberpaddy)

    I went through all these steps and got the same result.

    here is a link to the Console Error:
    https://snipboard.io/BYf1G3.jpg

    This site is on the same serevr as 15 other sites with most of them connected to SiteKit.

    Let me know the next best steps please

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update. In that case, what I suspect may be happening is the block is at host level. If you’re comfortable with cURL commands can you check both the below:
    curl -6 -I https://sitekit.withgoogle.com
    If you are unsure on how to perform this check then you can check with a website admin or your hosting provider. I suspect this check, which ensures IPv6 is used, will result in the same 403 error.

    curl -4 -I https://sitekit.withgoogle.com
    This check may allow you to connect, with a successful 200 error.

    If you’re unsure on the above please do ask your hosting provider, or if you wish to confirm your hosting provider I’m happy to perform some additional checks.

    Another indicator that this block may be at host level, specific to this site and not others (as this site may be hosted on a different IPv6 block), is to attempt Site Kit set up from this disposable WordPress site.

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

    Thread Starter soberpaddy

    (@soberpaddy)

    Sppoke with support and they found no issues

    https://snipboard.io/wWO05j.jpg

    I am with CLoudways – DIgital Ocean

    When I ran the cURL command I get this
    https://snipboard.io/60DozJ.jpg
    First one – server not found – second one OK

    Let me know what this means thank you!

    Plugin Support James Osborne

    (@jamesosborne)

    Appreciate you performing these checks @soberpaddy, while also checking with your hosting provider.

    Based on you not being able to communicate with the IPv6 command, I’ll need to check this with the team while also possibly reaching out to your hosting provider. What I suspect is happening, as with others who reported the same, is your site is on a specific IPv6 range which is blocked from communicating with Google servers.

    So I can ensure check this with the team can you please confirm your IPv6 address? You can check this from within your hosting control panel, or your hosting provider can provide you with this.

    Note also that if you’re able to temporarily disable IPv6 and then set up Site Kit I suspect set up will complete successfully. At that stage you can reenable IPv6 once more.

    Thread Starter soberpaddy

    (@soberpaddy)

    Hi @jamesosborne,

    Thanks for your replies.
    I spoke with support and they said they only support ipv4 – this is the address for that:
    159.89.131.134
    I am not sure what else to say here – there was not way they could disable/enable ipv6.

    And the ipv6 test was done on my system – not by the host.
    Cheers!

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @soberpaddy,

    Thanks for the update. In that case, if you performed a check using the commands at local level and not from your host, lets try some further tests.

    Firstly, can you try to reset Site Kit once more (Tools > Available Tools > Reset Site Kit). After doing so please attempt Site Kit set up once more.

    Secondly, do you see any invalid XHR response on the page where you land back on after being redirected? If so, please share details of this using the same form previously used, and not within this support topic. This can help indicate a block at host level. While it may not be protocol related there could be a firewall impacting setup.

    Let me know if you have any questions with the above. Depending on the details provided we may try a couple of other checks, which may include attempting setup from another device, or performing additional checks with your current environment.

    Thread Starter soberpaddy

    (@soberpaddy)

    HI there.
    I tried resetting again and it did not work.
    There is also nothing showing in the XHR option.

    I also just setup SiteKit on a different site that is on the same hosting to see if that is working.
    The site connected properly.

    I also disabled all plugins apart from SiteKit to setup againa and it did not work.

    Any other ideas?
    Cheers!

    John

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update @soberpaddy. Given you’ve performed a reset, never setup the plugin on this site previously, checks with third party plugins deactivated and you are communicating with Site Kit over IPv4 let’s perform a couple more checks.

    1. Do you have any firewall such as Modsecurity active at host level? If so you may wish to temporarily disable while attempting Site Kit setup.
    2. Do you see any PHP error logs relating to Site Kit? Your hosting provide may be able to assist with this.

    In addition, if you wish to perform a check with the Health Check & Troubleshooting plugin active, we have steps on the plugin website on how to do so. This will not only ensure Site Kit is the only active plugin (for you only as a logged-in administrator, but it will switch to a core theme which can be useful to rule out theme related functions or features impacting setup.

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

    Thread Starter soberpaddy

    (@soberpaddy)

    Ok – i have have an update which I am hoping will help.
    A previous web developer created a different folder for the plugins/themes to load from for security reasons –
    public_html/app
    Is the name of the folder.
    Could that be the root of the problem and if so, what is the best way to solve it?

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for the update @soberpaddy. Such changes can indeed cause issues. Is it possible for you to revert to the standard plugin directory before attempting Site Kit set up once more?

    Thread Starter soberpaddy

    (@soberpaddy)

    Hi @jamesosborne

    Ok – I reset all the folders to the standard wp-content – but still getting this redirect issue.

    Any ideas on next best steps to troubleshoot please?

    Thanks

    Plugin Support James Osborne

    (@jamesosborne)

    Now that you’ve moved the plugin back to the standard wp-plugins directory, you may need to reset Site Kit once more (Tools > Available Tools > Reset Site Kit), to ensure all previous records (which may include some incorrect callback URLs) are updated.

    After doing so, please attempt Site Kit set up once more. If you encounter any errors, we’ll need to perform some checks either at host level, or maybe from a new WordPress administrator account.

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Redirecting to PAGE NOT FOUND’ is closed to new replies.