Dmytro

Try to downgrade to 3.3.3

I had a lot of troubles after last update

Here is my ticket https://my.leap13.com/contact-support/ticket/443443 , thank you!

Can you, please, try to use any VPN maybe? According to the this test https://www.host-tracker.com/en/ic/4/55a619c0-d998-4ebe-a260-68626e2f01d4 there is no problems with website access

Thank you for your answer.

Here is a link to a test site https://pafe.miy.link/ with active 4.9.55 version
With active Version 4.9.55 I cant see carousel content, with 4.9.51 all is ok

Hi, thanks for your answer.
I sent report again (screenshot https://i.imgur.com/7mce0JX.jpg)

Here is one more time screenshot of phpinfo https://i.imgur.com/ZRJXzgU.jpg

Is there anything I can try to solve this?

I created test.php in the root of my website (same folder where .user.ini, wp-config.php, wordfence-waf.php and wp-content folder are located) with next code:

<?php
echo phpinfo();

I opened that file in the browser like https://mydomain.com/test.php and made Screenshot provided in the first message.

So there is no sense to check any settings or files, as I understand, because this file shows final php settings that is active for my site.
So auto_prepend_file option is filled correctly but wordfence does not see that

Thank you

Any changes? Give us some working quick fix (this is not working https://www.ads-software.com/support/topic/annoying-notifications-4/#post-13470027 )

Ok, my issue is resolved now, but I still has no guess why it presented.
Maybe there was an update of Jetpack plugin and something changed in the way it works and I had to reconnect website.

All configuration on the webhost side was correct and all function on wp dashboard and view counts are working properly after I authorized again Jetpack with WordPress.com account (even with active webhost limits related with xmlrpc connections).
Also I see stats on wordpress.com site again after Jetpack re-authorization

Thank you anyway!

The Jetpack connection is still broken

I understand that and I’m trying to find why

403 and 405 are very similar in kind, since they represent responses when the server itself is forbidden or rejecting the request.

Yes, but it’s important for me, because hosting denying connection to xmlrpc.php using 403 code, and if you are getting 405 – I have to search in some other places

I’ve seen that those errors have settled now, but you still haven’t connected your WordPress.com account to Jetpack. To do that, head over to this page.

You can then click on “Set up Jetpack” and then approve the connection to your WordPress.com

I can’t see that button “Set up Jetpack”, I will check from pc later. Thank you

Last question, how to find account username or email connected to my site now (I see statistics in wp dashboard , so some account connected, but I logged into two accounts on WordPress.com and I can’t see my site there) ?

My hosting removed limits for my sites but they said it’s not related with this issue, because you should get 403 error and not 405 if limits are active

I found some strange problems, maybe this helps:
1. I cant see account name connected to Jetpack (https://i.imgur.com/HOzrOm2.jpg)
2. I’m trying to access statistics on WordPress.com using my wordpress.com email/pass – but It says – there is no connected site, but I see statistics in wp dashboard

Thanks again! I will check twice

Thank you for your answer.
XML-RPC endpoint is opened only for jetpack IPs (https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/)
Did you check from one of those ips or from any other?

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

Аналогичная ошибка. Версия 5.1 работает с архивами кастомных таксономий отлично, версии 5.2.х при попытке на фронте зайти на страницу архива – internal server error

this thing does not work too:

function remove_action_template_redirect() {
   remove_action('template_redirect','redirect_canonical');
   remove_action( 'template_redirect',   'wp_shortlink_header', 10, 0);
   remove_action( 'template_redirect', 'maybe_redirect_404' );
   remove_action( 'template_redirect', 'wp_old_slug_redirect');
}
add_action('wp_loaded','remove_action_template_redirect');