Thanks for reaching out @stevesideas, and appreciate you sharing the troubleshooting actions taken so far. Based on your findings shard, this may indeed be related to client site timeouts, or possibly a block at host level. To determine more on this, please share the following:
- Your Site Health information. You can use this form to share privately if preferred. Feel free to include a link to, or contents of the WP Engine log within the form.
- If you visit your Permalink settings (Settings > Permalinks) and press the save changes button does the same occur if you visit your Site Kit dashboard once more and reload the page? Note that you don’t need to make any permalinks changes. This will refresh your .htaccess file, which can sometimes be corrupt.
Note that one option which we can also try is to reset Site Kit, although this would be a last resort as you’ll need to connect all previously connected modules once more. This will wipe all authentication tokens and allow for a clean re-authentication.
Let me know if you have any questions with the above. Thank you.
Hi James,
I did already try reset site kit but this didn’t help.
I just tried the permalinks save but this didn’t help either.
I’ve filled out the private form and sent to you.
Thanks
-
This reply was modified 4 days, 20 hours ago by
stevesideas.
Thanks for sharing the additional information @stevesideas. Given I don’t see anything obvious from performing some checks, please share the following:
- 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.
- When checking the Site Kit dashboard from a Chrome browser incognito window does the same occur? If so, please share any browser console errors that appear. This can help indicate a browser or caching related block.
- Do you see any invalid XHR responses on the Site Kit dashboard where the error occurs? If so please share details of this using the same form previously used.
Let me know if you have any questions with the above. I can’t state for sure the issue at this time, but it may also be worth checking if any such errors occur on another site from the same hosting control panel. Once we have the above I can also check this with the team. Thank you.
Hi James,
1. No warnings
2. I have filled out another form showing the x3 errors when running in incognito mode.
3. Not XHR errors.
@stevesideas Thanks for sharing the information. I have been unable to find anything with this added information. To dig deeper into this, please could you share the following:
- Do you have any browser extensions active? If you do could you disable these and try again? Some may even run while using Incognito so be sure to check this.
- A recording of this happening with the console window open so we can see while this is happening on screen.
- A copy of your HAR file. You can follow these instructions to obtain this. Please be sure to share this information privately via the form we shared or any other private means.
Let me know if you have any questions about the above.
Hi Adam,
1. I turned off all extensions. This did not help.
2. I’ll record this and send via the form.
3. Sure. I’ll do this as well.
Hi @stevesideas, thanks for sharing the HAR file, that’s very useful and helped us identify the issue, but it’s hard to say exactly what the cause is. The issue does appear to be a hosting related one rather than in Site Kit, but hopefully it’s more clear now so that hosting support can be more helpful.
The dashboard crash happens because there is a call happening there which is defined in a JS file that we expect to be present but isn’t. Your HAR file shows it’s being loaded, but is being redirected to ~ which isn’t a valid URL and what is causing the problem because the JS for this file is never loaded.
I did some extra testing and found that this same issue is observable in any URL with the word “location” in it anywhere in the request path or query parameters. For example: https://stevesideas.net/location or https://stevesideas.net/ideas/?location=boom
This is specifically relevant for this issue because the file responsible for this error is a JS file googlesitekit-datastore-location-2de0487cfab22825cb12.js
Like I said, we can see the problem but can’t see where it’s coming from, so I’d suggest reaching back out to WP Engine with these details. If you’re using your own Cloudflare account for this site, the issue may be in the configuration there as well since I can see the site is behind Cloudflare, but if not, then WP Engine should be able to track it down.
I hope that helps. Best of luck and let us know if we can be of any more assistance.
