Can’t Get SiteKit to Reconnect After Moving WP to Subfolder

  • Resolved dfender

    (@dfender)


    1 year, 9 months ago

    Hi:

    I needed to move my WordPress installation to a subfolder in order to make it work right with another plugin that will be a key component of my site. Unfortunately, I didn’t realize until it was too late that I should have “Reset Site Kit” in the available tools settings before I did this. Now, I when I try to reset SiteKit after reinstalling the plugin, it just keeps trying to connect to wp-admin in the root folder instead of going to the subfolder where wp is now installed and I get a 404 error.

    I did find the advise in another post to set both the WordPress address and the site address to the same address – and that worked to get it connected, but – like the other user – when I then reset the connection, put the addresses back to the way I want them, and then tried to reconnect SiteKit – I’m back to getting the error.

    I’ve looked through the Google analytics site to see if there is anything I can reset on that end to fix things and haven’t had any luck. Is there anything a Google admin can do to fix any mismatches and fix this issue for me? Or can delete everything on Google and create a new setup there that will connect (my site is still basically in development stages, so I don’t care if lose the little bit of data that has already been collected.)

    Thanks in advance.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Adam Dunnage

    (@adamdunnage)

    Hello @dfender thank you for opening a support topic with us. As you correctly stated previously, you needed to reset Site Kit before moving folders so that this didn’t happen.

    You could move your WordPress back to the initial folder location, perform a Site Kit reset and then move your WordPress install once more to the new folder and set up from scratch. Is this something that you would be able to try?

    Thread Starter dfender

    (@dfender)

    In a nutshell – THAT DID NOT WORK

    Specifically, what I did:

    1. Reset Site Kit in the existing subfolder install
    2. Deactivated and deleted the SiteKit Plugin
    3. Backed up my existing subfolder install
    4. Deleted the existing subfolder install
    5. Restored the wordpress install that was on the root drive
    6. Installed SiteKit and connected – everything loaded and connected fine
    7. Reset Site Kit
    8. Deactivated and deleted the Sit Kit plugin
    9. Uninstalled WordPress
    10. Restored my subfolder install
    11. Installed Google SiteKit from scratch
    12. Activated and tried to connect
    13. BACK TO REDIRECTING TO MY WEBSITE

    I’m no genius about this stuff, but it seems to me that the problem is the SiteKit plugin is pulling the location of the wp-admin file from the WordPress “Site Address” field instead of the “WordPress Address” field – because the address in my browser shows it’s going to the wrong place when it doesn’t work, and it connects just fine if you change the site address field to include the sub-folder in it – but that is not how I want the install to be.

    In any event, I’m done moving wordpress files around. If this can’t be fixed, I’ll just give up on it.

    • This reply was modified 1 year, 9 months ago by dfender.
    Plugin Support Adam Dunnage

    (@adamdunnage)

    @dfender Thank you for trying this and for the detailed steps you have shared that you took. Can I just check that when performing these steps that you changed the WordPress address and Site address values back to their original values when moving back to the initial file setup?

    If not then this could be why the reset at this stage didn’t quite work. Could you try again making sure to change these values too and let me know if that makes any difference?

    If you did try this then please let me know and we can reach out to the internal team to check your records on the service side to see if we can spot anything here.

    Thread Starter dfender

    (@dfender)

    Yes, when I reset the WordPress installation to the root location – both the site address and the WordPress address were set to the root as it originally was. And SiteKit connected just fine. Then I did the Reset Site Kit process and deactivated and deleted the plugin.

    I would welcome someone checking the records on the service side – that’s what I originally asked for.



    Plugin Support Adam Dunnage

    (@adamdunnage)

    @dfender thank you for confirming. I will reach out to the team to check your records on the service to see if anything is configured incorrectly. Once i have an update i will post it here for you.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @dfender Thank you for your patience while I checked this with the team. When checking your records we couldn’t find anything that stood out or configuration issues.

    Can I ask what the sub-folder was you were using and if you are still having trouble with this? Can you also ensure that you are on https when setting up the site, otherwise the redirect back to https could cause an issue.

    If possible, could you please share a recording of this happening with the redirect. You can use a service such as Loom to record and share the URL here.

    Thread Starter dfender

    (@dfender)

    I fixed it (I think)

    First – in an attempt that failed, I deleted my existing analytics setup on the Google site and created a new Google login for SiteKit to connect to to see if the problem was tied to the Analytics account.

    The same problem occurred – as soon as it goes to the “verification” page, it loops back to a 404 error on my website.

    So, following up on my original hunch that the problem all along has been that the SiteKit plugin is coded to grab the installation address from the “Site” address in the WordPress settings instead of the “WordPress” address, I simply added the subfolder between my web address and “wpadmin” to the link that was in browser’s address bar when the 404 page returned, hit return, and things magically started working.

    It didn’t get all the way through – after 3 or 4 pages it got hung up on a bad address again. But after I tried it a second time, everything connected and SiteKit is now happy and setup and attached to my new analytics account.

    So, now I’ll wait a couple days to see if data actually starts transmitting and I’ll check back in here to confirm one way or the other.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @dfender That’s great to hear that you managed to get through the setup! I will leave this topic open for you for now and please do let me know if you encounter any further issues.

    Plugin Support Adam Dunnage

    (@adamdunnage)

    @dfender Just wanted to check in with you to see if everything is still working as expected?

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Can’t Get SiteKit to Reconnect After Moving WP to Subfolder’ is closed to new replies.