Error 403 after update to latest version

Hi @joeygr –

Could you share more information about the 403 error? Where were you getting the error?

Looking at your site, I can see that we’re getting a 403 Error when we try to connect to your site via the xmlrpc.php file. Jetpack communicates with your site using this file.

I’d ?suggest ?checking if ?you ?have ?any? security ?plugins ?activated that? might? be? blocking? our requests.? If ?not, ?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.?

Jetpack? uses? this ?file ?to? communicate ?with ?your ?site, ?but ?some ?hosts ?block? connection ?requests ?to ?that ?file.

Our? requests ?look ?like ?the ?following:

-?File:? ?https://www.beyou.nl/xmlrpc.php?
-?User-agent?header:? Jetpack ?by ?WordPress.com
-?IPs: ?https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

Please ?ask ?them? to ?allowlist ?the ?IP ?addresses? listed? above. ?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.

yes it can be because for now jetpack plugin is disabled because they work on the backoffice to add new products. I gonna try tonight to put back on. I get it on the backoffice. When i go to the backoffice login page. I get also when auto update was tried to update last night this error:

lugin Jetpack (jetpack) update failed due to the following issue: PHP Fatal error: Uncaught Error: Call to undefined method Automattic\Jetpack\Connection\Error_Handler::check_api_response_for_errors() in /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php:44 Stack trace: #0 /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php(462): Automattic\Jetpack\Connection\Client::remote_request() #1 /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-package-version-tracker.php(102): Automattic\Jetpack\Connection\Client::wpcom_json_api_request_as_blog() #2 /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-package-version-tracker.php(63): Automattic\Jetpack\Connection\Package_Version_Tracker->update_package_versions_option() #3 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/class-wp-hook.php(307): Automattic\Jetpack\Connection\Package_Version_Tracker->maybe_update_package_versions() #4 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters() #5 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/plugin.php(476): WP_Hook->do_action() #6 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/load.php(1102): do_action() #7 [internal function]: shutdown_action_hook() #8 {main} thrown in /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php on line 44 Fatal error: Uncaught Error: Call to undefined method Automattic\Jetpack\Connection\Error_Handler::check_api_response_for_errors() in /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php:44 Stack trace: #0 /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php(462): Automattic\Jetpack\Connection\Client::remote_request() #1 /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-package-version-tracker.php(102): Automattic\Jetpack\Connection\Client::wpcom_json_api_request_as_blog() #2 /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-package-version-tracker.php(63): Automattic\Jetpack\Connection\Package_Version_Tracker->update_package_versions_option() #3 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/class-wp-hook.php(307): Automattic\Jetpack\Connection\Package_Version_Tracker->maybe_update_package_versions() #4 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters() #5 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/plugin.php(476): WP_Hook->do_action() #6 /var/www/vhosts/beyou.nl/httpdocs/wp-includes/load.php(1102): do_action() #7 [internal function]: shutdown_action_hook() #8 {main} thrown in /var/www/vhosts/beyou.nl/httpdocs/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-client.php on line 44 [{"name":"jetpack","old_version":"11.2","new_version":"11.3","status":"Updated"}

Hi @joeygr

When you’re able to, can you please deactivate and delete Jetpack entirely, and then reinstall it, as described here:

https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reinstalling-jetpack

*Please note* you shouldn’t lose any data (including stats and followers), but your settings will be reset so you’ll need to set them again after reinstalling and reconnecting.

Let us know if that helps!

@bruceallen

Deactivated and deleted. Works until you complete setup and login with a WordPress.com account.

@lastsplash

Tried whitelisting the IPs and disabling XLM-RPC protection on my server. Still same issue after authorizing a WordPress.com account.

@bruceallen @lastsplash Seems to only impact the WP Admin user once logged in.

• This reply was modified 2 years, 2 months ago by welime.

Yes, only for WP Admin. I have the same. I also turned it off and while it’s off, everything works

@joeygr / @welime – I’m not sure if you’re on the same site (beyou.nl) or account, but here is what I would try next, based on what I’m seeing here.

It’s possible that this is related to the WP Optimize plugin. Would you be able to follow these exact steps for me?

1. From the wp-admin dashboard of your site, please go to Jetpack > Dashboard > Connections > “Manage site connection” from your left-hand menu.

2. Click the “Disconnect” button. If it’s already disconnected, you can skip to the next step.

3. Deactivate your Jetpack plugin by heading to Plugins > Installed Plugins and finding “Jetpack by WordPress.com.”

4. Completely uninstall Jetpack.

5. Dump the cache of your WP Optimize plugin and then deactivate it.

6. Deactivate all of your other plugins.

7. Install the newest version of Jetpack.

8. Activate Jetpack.

9. In Jetpack > Dashboard > Connections > “Manage site connection,” Click the “Set up Jetpack” button and continue through the approval process.

If those steps don’t work, could you try them in order one more time after switching your theme to something more minimal, such as Twenty Twenty Two?

Once everything looks normal with Jetpack connected, you can switch the theme back and start activating your plugins one by one to see if the issue comes back.

Please let us know the results of this troubleshooting and we can go from there. Thanks!

—

@sakras Since you already opened your own thread, I’ll respond to you there:

https://www.ads-software.com/support/topic/blocks-access-to-the-admin/

@madhattersez I’m not running the WP optimize plugin.

• This reply was modified 2 years, 2 months ago by welime.

I tried to disabled. and install new from scratch. But when i connect to jetpack i get error 403. Any idea?

@welime Gotcha, thanks for that.

Could you please start a brand new thread and mention your site’s URL there? If you want it to remain private, you can also contact us via this form here instead.

@joeygr Just to confirm, you installed Jetpack from scratch with all other plugins completely deactivated and your theme switched out and you still encountered a 403 error in your wp-admin?

If so, can you tell me the version of your WordPress’ core and your PHP version?

Have the same situation error 403 when login into the admin panel.
To go around type /index.php after you get the error 403.
Like yourwebsite.com/wp-admin/index.php

Maybey its better to check whats changed ij last update. Before i gonna change all on my website. The only thing whats changed is the jetpack update. Other all the same.

This worked for me.

https://www.ads-software.com/support/topic/blocks-access-to-the-admin-codification-errors/