403 forbiden public-api.wordpress.com/pinghub/wpcom/me/newest-note-data

In the same browser, I can open:

wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data

It shows me (obfuscated):
Websocket client for /pinghub/wpcom/u/4******1/newest-note-data

This is with me logged in as the user shown as the “Jetpack Master User” in Site Health -> Info -> Jetpack.

I did notice that the Jetpack Site ID does not match the one from the pinghub/wpcom/u/4*****1 number.
My Jetpack Site ID is different. 4******5.

I already tried de-activating Jetpack, deleting it, re-installing, and re-activating it. That was all before I posted this topic.

I’m getting this same error starting today, sorry Ican’t help but hopefully a fix will come from this thread ??

@aetherscythe Thanks for the report! I believe the 403 errors are related to a known issue. There’s a workaround that you can try using here:

• https://github.com/Automattic/jetpack/issues/9170#issuecomment-376867824

In regards to the mismatch between site IDs, we’ll need your site URL in order to troubleshoot that issue further. Can you share your site URL with us here? Then we’d be happy to look into it further for you.

Hi, @ryancowles Thanks for the reply.

Am I reading correctly that the workaround is to disable the jetpack notifications altogether?
Turning off features is not a workaround, it’s a loss of functionality and is at most a suppressing of the symptoms. ??

Am I to understand that this known issue has been there since March of 2018 or before and it is still unresolved?

@ryancowles Is there a way I can share my site URL privately?

@ryancowles I found you on slack and shared the details. Thanks.

Hi @aetherscythe

We don’t use Slack for support, but you can contact us via this contact form and mention this thread. We’ll then get back to you by email.

Thanks!

Thanks, @drawmyface!
I did get a response from a nice person at Automattic on Slack in so far as the exact link to use to open an actual ticket.
I later realized the reason I could not open a ticket before was that I was trying to use me personal WordPress user, not the one that I use to maintain the site. So no purchase history (even for $0 items), no ability to open a ticket.

No response on the ticket, though and the problem persists.

My hunch is it has to do with 2FA. I even tried creating an API Key on the WP side, but no place to enter it in the JetPack plug-in. My browser is authenticated via 2FA, so I can open the wss URL, and JetPack was activated via same browser and I was challenged for 2FA at that time, but JetPack itself runs separately (not in my browser), so it is getting the 403 forbidden as a result. Just my guess. Well except it’s my browser throwing the error. :-/

Anyway it would appear to be a bug in JetPack or the WP side.

Any ideas?

Hi @aetherscythe

I see there is a ticket from you which I see has had a response since your message here – so we’ll continue to follow up with you via the ticket. As such I’ll close out this support thread in favor of the ticket. In the meantime do you notice the error when you are also logged into WordPress.com within the same browser? If you could confirm that via the ticket we can continue digging in. Thank you!

Karen,
Thanks. Yes I see the error even when logged into WordPress.com as the admin user that activated JetPack.
I’ll follow up in the ticket. Thanks.

I noticed something new just now logging into wordpress.com.
It offered to let me save my 2FA in the browser for 30 days.
Maybe that will help here?