Site Kit: Error: Bad Request (missing parameter: ‘code’)

Hi there @lee03351,

Thanks for reaching out and also sharing your Site Health information. From checking your site and details provided I don’t see anything obvious that would be causing this issue. So we can determine more please share the following:

1. At what stage do you encounter this error? (ie. When initially setting up the plugin, after clicking on the “Continue” button at the Sign in with Google stage)
2. Do you see any warnings or errors when checking your Site Health status (Tools > Site Health > Status), which differs from your Site Health information requested above? Such errors may include REST endpoint references.
3. When checking the Site Kit dashboards from a Chrome browser incognito window do you see any browser console errors on the same screen where this notice appears? IF so please share any such errors.

Once we have the above information we can propose some troubleshooting suggestions. These may include ruling out your plugin environment impacting setup, using the Health Check & Troubleshooting plugin, or performing some checks with your hosting setup. Based on other reports either could be cause of this error.

Note also that if you see an option to “re-do the plugin setup” please go ahead and check does the same occur after clicking on this link and proceeding to attempt setup once more.

I’m getting this same error too, it’s when trying to setup the plugin. It connects my Google account but right after going to the callback URL I see that error.

And I can’t access the Site Health tab because it gives a timeout. Console shows a 404 on an URL:

https://sitekit.withgoogle.com/v2/site-management/setup/ 400

Uh oh, just retried after submitting my last message… and it worked.

Same error like other people in the community:
`
Hope you see this and advice on issue.

@rickmaxter Could you please open a new topic of your own so that we can assist you individually with this. Thanks.

@adamdunnage , We are also facing the same error during sitekit integration.
also creating a new topic.

Same thing here. I ran health and check. disabled all plugins and still get the same error.

@vasami @wrwl Please open a new support topic and we’d be happy to assist with your case individually. Thank you!

@jamesosborne
My other webiste is expericing the exact same issue.

Here is the error I am getting with icongnito windows when trying to connect to accounts

Request URL: https://sitekit.withgoogle.com/v2/site-management/setup/
Request Method: GET
Status Code: 400 
Remote Address: 142.251.42.241:443
Referrer Policy: strict-origin-when-cross-origin

Thanks for the update @lee03351,

When you mention this is the error from an incognito window can you share whether you also get the same “Bad Request (missing parameter: ‘code’)” error” when using a Chrome browser incognito window?

In addition please share the browser you were initially using when you reported this error, or when you checked on your other site. This would be very helpful as other users also reported the same, and we’re currently undergoing some browser based testing to replicate this.

I’ve been facing the exact same issue, any insight on how to fix it.

update: I’ve been able to solve this on brave with this by disabling the auto-redirect AMP pages under the shields as listed here: https://www.ads-software.com/support/topic/cant-install-sitekit-bad-request-missing-parameter-code-2/

• This reply was modified 2 years, 6 months ago by astroajay. Reason: Solved

@astroajay Glad to hear you’ve been able to resolve this. Nice find on reviewing the other support topic for this particular configuration within the Brave browser (Shields > Look and feel > Auto-redirect AMP pages).

@lee03351 Can you confirm whether this issue remains on your own sites, and in particular if you’ve encountered this when using the Chrome browser’s incognito mode.

As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Just to add to this, for me it was Brave shields causing the issue.

I simply logged into my WordPress dashboard using a different browser (Safari) and repeated the setup steps and it worked.

Many thanks for letting us know @severisth! Great to get confirmation from users impacted by this.

If you run into any further strange behavior or if you have any questions be sure to get in touch.