Fatal error while activating site: Missing site_id or site_code

Hello @jbalyo thanks for getting in touch and sharing the information above. I’d be happy to help look into this for you. Please could you share the following:

1. Your?Site Health information. You can?use this form?to share privately if preferred.
2. Are you able to complete the setup from an Incognito window?
3. Any screenshots or recordings you can share. These can be added to the form requested above.

Please let me know if you have any questions on the above.

Hello Adam-

Thank you for your response.

1. My response has been submitted privately.
2. Tried it in an incognito window – same result.
3. I’ll be digging into this a little more and will add details if I find anything that could be helpful.

@jbalyo Thanks for sharing the information. I can see that at the time of submitting your Site Health that you were using Site Kit 1.105.0. We have now released 1.106.0 this week so could I ask if you see the same after updating the plugin?

If you do still see this after updating the plugin can you please try setting up Site Kit on this URL which will set up a temporary WordPress site for testing. Once set up, do you see the same fatal error?

@adamdunnage Thanks for the reply. Yes, I have tried the same setup process since upgrading to version 1.106.0. Also tried it while having all other plugins disabled and a default theme applied (Twenty Twenty-Three).

I went through the setup process on your demo site and it worked without any problems. On the site I’m working with it never gets to Step 1. Instead, it produces the fatal error upon returning from the “Sign in with Google” screen after selecting my account and clicking Continue.

I made a temporary modification on a copy of the plugin code to have it spit out the value of $query_params whenever that error occurs and site_id is indeed coming back empty, and the alternate parameter it is looking for (site_code) is missing altogether. Seems it needs to see at least one of the two.

Array
(
    [site_id] => 
    [step] => verification
    [code] => sitekit-ub....
)

I wonder if something CORS related could be blocking this? I’m not sure where that site_id should originate from.

@jbalyo Thanks for the added information. While I continue to investigate this, please could I ask you if you see any warnings or errors when checking your Site Health status (Tools > Site Health > Status), which differs from your Site Health?

Could you also ensure that any browser extensions you have active are temporarily disabled and try once more to see if you encounter the same?

@adamdunnage There are no Critical issues reported on the Site Health Status tool.

I went ahead and deactivated all other plugins, deactivated all browser extensions (browser used was Google Chrome), uninstalled and reinstalled a fresh copy of Site Kit version 1.106.0, switched to a default theme and tried again – it still produced the same error.

• This reply was modified 1 year, 7 months ago by typeless.

@jbalyo Thanks for confirming the above. While I continue to perform some testing on my side, could I also ask does the same happen with another site on the same hosting platform?

@adamdunnage It happens on both the Staging and Production version of the same site in the same hosting (AWS). However, I do manage other WordPress sites in similar environments which have not had this problem.

@jbalyo This is looking like it could be hosting related. It could be a particular AWS or firewall setting. We are limited to support for the Site Kit plugin so I’d suggest at this stage to check your AWS setup to see if any configuration here could be causing this.

If you are unable to find something then please let us know and we can continue to troubleshoot this with you where possible.

@jbalyo Just checking here if you had any update on this?

@adamdunnage

No success as of yet. I did go through and compare the server configuration of both a working and not-working site and everything seems exactly identical. Same firewall settings, same server configuration, same server type, same plugins, same theme and customizations, same headers… But one works and the other doesn’t. At this point I’m not sure if it would be hosting related since an identical hosting configuration both works and doesn’t at the same time.

Do you have any other ideas to try? Anything which might shed some light? Where is the site_id supposed to come from?

Thanks

@jbalyo Sorry to hear this but thanks for checking on the hosting side of things that’s very helpful to know. I have discussed this further with the team to see what we could check further.

I can confirm that this is not a CORS issue. It would help in troubleshooting this if we could see what’s happening with the http requests. To do this you can use this plugin and share the output to our private form so that you don’t post any site sensitive information in this topic.

Something could be going wrong with the request made for the site code. In this case the request we are specifically interested in would be for sitekit.withgoogle.com/o/oauth2/site/.

Once you are finished using the log http plugin and shared the information I would suggest disabling it so that it’s not left running in the background of your site. Once the information has been shared I can discuss this further with the team to see if we can see what is happening in this case and find a resolution for you. ?

@adamdunnage I have submitted the relevant HTTP requests to that form. Definitely looks to me like the site_id and site_secret are coming back in the second response payload, but maybe something else will stand out to you.

Thanks for continuing to look into this.

@jbalyo Thanks for sharing, I will pass this on to the team to look into further and post any updates here.

@adamdunnage Yes, we are using both a staging and a production environment. I would appreciate if you could please scrub our URLs from the above message if possible so they don’t become associated with debugging information in public searches.

Both environments have the same issue activating Site Kit regardless.

I got the same impression from the logs – code and site_code are passed back, but the plugin somehow does not receive them.