Cookie check failed

Hi @clutrain

Can you tell us a little more about what’s happening? I don’t see a previous support request from this account on this topic. What were the 5 steps you were asked to try?

That error is generally caused by caching issues. Can you clear any caches you have on your site and/or check with your hosting provider if there is any server level cache that might need to be cleared, then try again?

OUps, sorry… It’s my first time writting! ;

The problem occur with Jetpack 11.8.4.

I did all 5 of the list from below. None of them worked! and I Click the link to this. ??

Here is what I get. Restore ping back to the same thing. On another page, It suggested to clear my Browser and desinstall Jetpack and re-installed… Same issue.

Many thanks…

Phil

Trouble with Jetpack?

It may be caused by one of these issues, which you can diagnose yourself:

1. A known issue. Some themes and plugins have known conflicts with Jetpack – check the list. (You can also browse the Jetpack support pages or Jetpack support forum to see if others have experienced and solved the problem.)
2. An incompatible plugin. Find out by disabling all plugins except Jetpack. If the problem persists, it’s not a plugin issue. If the problem is solved, turn your plugins on one by one until the problem pops up again – there’s the culprit! Let us know, and we’ll try to help.
3. A theme conflict. If your problem isn’t known or caused by a plugin, try activating Twenty Twenty-Three (the default WordPress theme). If this solves the problem, something in your theme is probably broken – let the theme’s author know.
4. A problem with your XMLRPC file.?Load your?XMLRPC file. It should say “XML-RPC server accepts POST requests only.” on a line by itself.
   • – If it’s not by itself, a theme or plugin is displaying extra characters. Try steps 2 and 3.
   • – If you get a 404 message, contact your web host. Their security may block XMLRPC.
5. A connection problem with WordPress.com. Jetpack works by connecting to WordPress.com for a lot of features. Sometimes, when the connection gets messed up, you need to disconnect and reconnect to get things working properly. Disconnect from WordPress.com

Still having trouble?

Ask us for help! Contact our Happiness team. W

Hey @clutrain – I checked the Jetpack connection for your site and it is showing everything is good at the moment. You can also check here:

• https://jptools.wordpress.com/debug

Could you please confirm if you are still having the issue? If yes, have you tried clicking on the Restore Connection option to see if that helps?

Hello @bizanimesh – I know, that is buggin me! My site health says the same, everything is fine… But I’ve click so many timesss (before trying the debug pages trick) on restore and it never worked! Same message come back, with same difficulties as listed before… Takes about 2 seconds.

Many thanks for your time!

Hi @clutrain,

Thanks for the update. Can you tell me which setting you are trying to update when you get this error?

Please try the following and let us know what you find out.

• Try a different browser
• Check for JavaScript errors. If you’re not sure how to do that, you can follow this guide: https://www.ads-software.com/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis

Hello @gaurav984,

Just like in the image, in simple Jetpack/Dashboard it start… In “recommendation” tab, there is a “circle 1”, suggesting there is one. When I click on it, nothing appear. Grey background with Jetpack logo, no suggestion block.

Thanks…

?I usually work with Chrome...  I tryed Firefox, same story!

? We hit something, but so many info, I don't know what to do!
Since I wasn't able to copy and paste the 34+1+2 issue in Google, here are the Firefox results : 


Some cookies are misusing the recommended “SameSite“ attribute 10

This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. admin.php

JQMIGRATE: Migrate is installed, version 3.3.2 load-scripts.php:9:709

downloadable font: no supported format found (font-family: "jetpack" style:normal weight:400 stretch:100 src index:1) source: (end of source list)

downloadable font: no supported format found (font-family: "Noticons" style:normal weight:400 stretch:100 src index:1) source: (end of source list)

This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”.

complete.html

Cookie “wpcom-thirdparty-cookie-check” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite complete.html:15:12

Partitioned cookie or storage access was provided to “https://widgets.wp.com/3rd-party-cookie-check/complete.html” because it is loaded in the third-party context and dynamic state partitioning is enabled.

Cookie “tk_tc” has been rejected for invalid domain. w.js:1:1557

Missing data from PHP (wpNotesArgs). admin-bar-v2.js:3:46

Error: request.message is undefined undefined

onMessage options opt-in.js:122:13

onMessage extension extension.js:24:25

Clean the cache of the scraper (new onComplete event) ial.js:450:21

Partitioned cookie or storage access was provided to “https://widgets.wp.com/notifications/?jetpack=true&v=none&locale=en#https://www.clubtraindirect.com/wp-admin/admin.php?page=jetpack#/woo-setup” because it is loaded in the third-party context and dynamic state partitioning is enabled.

Cookie “wp_api” has been rejected because it is already expired. rest-proxy

Cookie “wp_api_sec” has been rejected because it is already expired. rest-proxy

Partitioned cookie or storage access was provided to “https://public-api.wordpress.com/wp-admin/rest-proxy/?v=2.0#https://widgets.wp.com” because it is loaded in the third-party context and dynamic state partitioning is enabled.

InstallTrigger is deprecated and will be removed in the future. rest-proxy:16:5012

Firefox can’t establish a connection to the server at wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data. rest-proxy:16:5485

Uncaught (in promise) ApiError: Cookie check failed (Status 403)

????d https://www.clubtraindirect.com/wp-content/plugins/jetpack/_inc/build/admin.js?ver=0e6ab1eb1c407117ab5a:2
admin.js:2:149928

Firefox can’t establish a connection to the server at wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data. rest-proxy:16:5485

onMessage options opt-in.js:122:13

onMessage extension extension.js:24:25

Clean the cache of the scraper (new onComplete event)

Hello Phil,

I am seeing:

Firefox can’t establish a connection to the server at wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data. rest-proxy:16:5485

Uncaught (in promise) ApiError: Cookie check failed (Status 403)

I also reexamined your site’s connection with our https://ratelimit.rudyfaile.com/ tool. This tool shows how the XML-RPC requests are handled by your server. We should get 50 x “200 OK”; instead there is a number of 403 Forbidden server responses.

The HTTP?403 Forbidden?response status code indicates that the server understands the request but refuses to authorize it.
?
I understand that you have already checked that any security plugin blocks our requests. Is that correct?

As the next step, try contacting your hosting provider and asking them to check their security logs to see if they are blocking or otherwise limiting incoming and outgoing connections over XML-RPC.

Please ask them to allowlist the IP addresses listed here. Note that these IP addresses could change (or more could be added) at any time, which could break your connection to Jetpack. For this reason, we actually discourage allowing specific IPs, although, with some hosts, it may be the only option.?

Hi @clutrain,

Just checking in here to see if the issue is resolved on your end?

We generally close the thread we don’t hear from you for more than a week. Thanks!

Sorry… Business overwelm… Didn’t have time to check again with IT.

Most likelly, it’s an incomatible “something” on my site… I have to Clone it ans see if it works with only WP & JetPack… Frankly, I’m missing hours of sleep, I don’t have time to do that. Business is living a boom right now.

Cool, but not cool! ??

Thanks for checking.

Hi @clutrain,

Thanks for the update. Please take as much time as you need and get back to us once you are ready. No rush.

Best.

Hi there, @clutrain

Do you have updates about that? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!