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

  • Is this Jetpack or WP error? Sorry if posted incorrectly.

    In development console I have an pinging error (which is repeating as it keeps retrying).

    Says: WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403

    I am logged in as Admin.

    Using most recent Jetpack and WP releases, with AU language.

    https://www.ads-software.com/plugins/jetpack/

Viewing 15 replies - 16 through 30 (of 39 total)

  • When I make off all Jetpack modules and make on some of these ones, I have not this error.

    I had this issue because of a firewall plugin i used. It added some rules in .htaccess file which blocked connectivity to the Jetpack server. I disabled the plugin and used another alternative to that and it worked well

    Plugin Contributor Ryan C.

    (@ryancowles)

    @gans-s: Could you please follow the instructions that Jeremy posted above? Thank you!

    @nagpai: Thanks for the info! Do you recall which plugin you had to disable?

    @ryan Cowles: Thanks! I have not these troubles currently.

    @ryan Cowles it was All in One WP Security.. I have replaced it with Wordfence. Not having issues now.

    I remember having read in a thread about some .htaccess entry that causes this. trying to trace that out for you.

    Thread Starter snaphappyme

    (@snaphappyme)

    I have Wordfence and the socket error is still present and continuing for me.

    Try momentarily disabling Wordfence and see if it works.

    Thread Starter snaphappyme

    (@snaphappyme)

    @nagpai

    Thanks for the suggestion but it isn’t a wordfence related issue.

    It appears my site isn’t able to establish and hold an active connection with wordpress.com.

    The jetpack team is still investigating and working through the issue.

    Plugin Contributor Davor

    (@davoraltman)

    Hey folks ??

    The console error will only be displayed if you are not logged into WordPress.com. The fix is on its way but I don’t have an ETA on it at the moment.

    In the meanwhile, just stay logged into WordPress.com and the console error won’t be triggered. Cheers ??

    @nagpie

    I am having the same issue and have AIO WP Security installed. I installed the 6G firewall rules in .htacess. So that is probably the reason for this.

    Do you recall what line i .htaccess it was that is causing this – I wouldn’t mind doing a manual edit of my .htacess if I knew what to edit ??

    Please see the answer from davor.altman.

    If it’s not fixed, please try deactivating other plugins one by one, to find possible conflict with Jetpack.

    update:

    I’m still seeing in Chrome console:

    return pinghubConnections[ path ] = new WebSocket(‘wss://public-api.wordpress.com’ + path);

    WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Error during WebSocket handshake: Unexpected response code: 403

    WP 4.5.1
    woocommerce 2.5.5
    Jetpack 4.0.2

    davor.altman’s response works for me, thks

    Hi all, it probably has to do with the Notifications module in Jetpack. I do not know what specifically causes it, but disabling the Notifications module removes the error for me.

    I am having the same issues.
    WebSocket connection to ‘wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data’ failed: Error during WebSocket handshake: Unexpected response code: 403
    in Chrome.
    ———————–
    Any solutions.

Viewing 15 replies - 16 through 30 (of 39 total)
  • The topic ‘WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wp… failed 403’ is closed to new replies.