WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wp… failed 403

Logging into WordPress.com makes the error go away in the console, but that’s not a full-fledged “fix”. Waiting to see what Jetpack does. ??

As we said earlier in this thread, we’re aware of the issue and a fix is on its way but we don’t have an ETA on when this will be fixed.

In the meantime: the console error will only be displayed if you are not logged into WordPress.com, so as long as you stayed logged in, you won’t see the error.

+1 for disabling notifications in the Jetpack settings, error is no longer displaying in Chrome

Disabling notifications in Jetpack and/or being logged in to WordPress only seems to affect the error showing on the console log. The behavior that alerted me to the error still exists. I’m unable to reinstall WordPress, add a new theme or even upload a new theme. Each of these actions triggers the error (unless they are being hidden by disabling the notification in Jetpack.)

I’m unable to reinstall WordPress, add a new theme or even upload a new theme.

That’s most likely not linked to the error we’re discussing in this thread. The error mentioned here is only linked to Jetpack’s Notifications module, and shouldn’t affect any other element of your dashboard.
It shouldn’t affect WordPress updates either, as these don’t rely on JavaScript.

Do you get an error on the dashboard page when trying to reinstall WordPress or adding a new theme?

Hola, yo tengo el mismo error, y debido a ellos estoy teniendo problemas para cargar el Events Calendar de Event Espresso 4, espero puedan contribuir a encontrar el error, estoy usando la versión 4.5.2 y no tengo akismet ni jetpack.

On May 13 they said :

We’ve found out that the Websocket console error is only displayed if you are not logged into WordPress.com. If you are, the error will be gone.

We are working on a fix for this but I don’t have an exact ETA on it. However, you can remain logged into WordPress.com and the console error won’t be triggered.

I hope it makes sense. Thank you very much for your understanding and patience. Cheers ??

Today the issue still exists.

Right.. still issue exists..

@dreadlox @abiox We’re indeed still looking into this. However, until we fix that issue, the error mentioned in this thread shouldn’t affect any other element of your dashboard.

Do you experience any issues in your dashboard, linked to that console notice?