403 Error Loop

  • Resolved mrwindowsx

    (@mrwindowsx)


    4 years ago

    I recently installed a new WordPress self-hosted and then installed the Jetpack plugin’s latest version, no other plugins were installed and activated, only Jetpack. I successfully configuring the plugin to connect to wordpress.com following the guidance. However, when I check the chrome debugger console, I found that there is some error caused by this plugin which always keeps generated. I use WordPress multisite installed with default theme twentytwenty-one and ensure the Jetpack plugin enabled in the networks, running on Apache server with PHP Version 7.4.16. Here is the error:

    Unchecked runtime.lastError: The message port closed before a response was received. public-api.wordpress.com/wp-admin/rest-proxy/?v=2.0#https://widgets.wp.com:1

    Unchecked runtime.lastError: The message port closed before a response was received.
widgets.wp.com/notifications/?jetpack=true&v=@automattic/[email protected]&locale=en#https://insurancewhat.com/wp-admin/index.php:1
    WebSocket connection to 'wss://public-api.wordpress.com/pinghub/wpcom/me/newest-note-data' failed: Error during WebSocket handshake: Unexpected response code: 403
g @ ?v=2.0:6
_ @ ?v=2.0:6
T @ ?v=2.0:6

    This error also causing the jetpack comment-like feature to not works properly and it keeps loading.
    I need help to solve this problem seriously from an expert on here forum. Really appreciate it. Thanks.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Jen H. (a11n)

    (@jenhooks)

    Hi @mrwindowsx,

    Thanks for doing all that preliminary troubleshooting. Did you get this resolved on your own? I’m seeing a solid Jetpack connection to WordPress.com now, and I’m not seeing any console errors when I visit your site.

    An important note, though: any time there’s a 403 error, that’s related to a security block. So, since you mentioned you weren’t running any other plugins, it wouldn’t be a security plugin causing the problem, which makes it likely that your host is the culprit. If you have trouble like this in the future, please contact your host’s customer support team and ask them if they’ve implemented anything that would interfere with Jetpack’s connection. You can refer them to our documentation if they need additional context:

    https://jetpack.com/support/getting-started-with-jetpack/fixing-jetpack-connection-issues/

    Let us know when you need us.

    Thread Starter mrwindowsx

    (@mrwindowsx)

    Hi @jenhooks

    It still not solved, the error raised when the user logged in, if not, you can also found the errors by going to the single posts, due to these errors the jetpack comment likes not works, and also wordpress.com notifications too. I contact the host and send the documentation link you provide, and everything already set up, PHP XML is activated and installed. This is from wordpress.com that forbids requests from the site host server, gives a 403 error. I also try to deactivate and reactivate this plugin with no luck, checking with Site Health and SSL cert with no issue.

    Plugin Contributor Jen H. (a11n)

    (@jenhooks)

    Hi @mrwindowsx,

    This is really peculiar. Can you send us a screenshot of the 403 error? You can use a service like https://snag.gy/ to share your screenshot with us if you don’t already have a preferred method. If you could copy and paste the error log entry for only this event, that would also be helpful.

    I’m not able to reproduce it anywhere on your site, but that might be because I’m not a logged-in user.

    When I tested the contact form, it looked like it submitted correctly: https://d.pr/i/WwLwD6 Did you see this comment show up in your WP Admin?

    I also see no console errors on your site, and your connection to Jetpack is good.

    You’re already using a default WordPress theme, and your plugins are very minimalist. This suggests to me that the issue is related to your host, though they’re saying they’re definitely not blocking anything, right?

    • This reply was modified 4 years ago by Jen H. (a11n).
    • This reply was modified 4 years ago by Jen H. (a11n). Reason: asked for more details
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘403 Error Loop’ is closed to new replies.

Tags