Senri Miura

P.S.

I found another problem.
When displayed in IE, the title name will not be displayed either.
(In this example, “functions.php”)
Since this plugin seems to have various problems, it may be replaced with a plugin that will be displayed properly in IE in the near future. (Highlighting Code Block etc.)

Hello Yui,

Thank you for your immediate reply. I’m sorry for my reply being delayed.
This bug seems will be fixed in the 5.4.1 release, so it doesn’t seem to matter.
After that, I’m using the following patch.

/ * Add script to functions.php * /
/ * [WordPress 5.4] Multi-file uploader bug fix * /
function my_admin_media_views_style() {
if ( wp_style_is( ‘media-views’ ) ) {
$style = <<<STYLE
div.moxie-shim.moxie-shim-html5,
div.moxie-shim.moxie-shim-html5 input[type=”file”] {
display: inline;
}
STYLE;
wp_add_inline_style( ‘media-views’, $style );
}
}
add_action( ‘admin_enqueue_scripts’, ‘my_admin_media_views_style’ );

Supplement:

The following email has received from a Jetpack engineer regarding the matter I was inquiring this morning.

It seems that the server side of Jetpack handled the trouble.
Note that the “403 Forbidden” error is because I was temporarily disabling the Jetpack plugin.
Now it works fine as follows:

https://www.senris.com/wp302ja/xmlrpc.php?for=jetpack
↓
XML-RPC server accepts POST requests only.

From Jetpack Engineer
　　↓
Apr 17, 17:59 UTC
Senri,

Thanks for the extra information – I updated Jetpack to know that your Site URL is https://www.senris.com/wp302ja.

That got the xmlrpc.php working fine: https://www.senris.com/wp302ja/xmlrpc.php?for=jetpack
However, when jetpack actually tries to connect to it, we’re still getting a “403 Forbidden” error. I’m assuming it has to do with a rule in your custom .htaccess, or perhaps a security system on your host.

At this point, I would recommend reaching out to your webhost to see if they are able to check their PHP error logs to find out where the 403 errors are happening, and perhaps to start over with a new, clean, default .htaccess.

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

* Omitted below

• This reply was modified 4 years, 7 months ago by Senri Miura.

Hello James,

I just enabled Jetpack again and moved to the configuration process, and this time I was able to set up safely without errors.

My site health status has also changed to good, and there are no fatal errors.
I didn’t change anything on this server, so maybe there was a problem with the server side of Automatic.

For the time being, this issue is resolved, so this thread is closed and OK.
Thankfully, I didn’t have to uninstall Jetpack.

Thank you very much.

Regards,
Senri Miura

P.S.

Currently, my site already has replaced all features used in Jetpack with other plugins. All plugins except Jetpack are working normally.
Only Jetpack does not work properly.
Thus, if the next Jetpack update doesn’t fix the bug, we’ll uninstall Jetpack completely.

• This reply was modified 4 years, 7 months ago by Senri Miura.
• This reply was modified 4 years, 7 months ago by Senri Miura.
• This reply was modified 4 years, 7 months ago by Senri Miura.

I understand the IP range used by Automatic.

But, your answer is totally meaningless.
Even if .htaccess is set to the following, it does not work at all with the latest version of Jetpack.
Now, it doesn’t matter what your IP address is.

# Accept xmlrpc.php
<FilesMatch “xmlrpc.php”>
Allow from all
</ FilesMatch>

Currently, .htaccess is set to the above setting, but Jetpack and WordPress can not be linked, so Jetpack is disabled.

If this situation persists, I think uninstall Jetpack because it could use other plug-in instead of Jetpack.

• This reply was modified 4 years, 7 months ago by Senri Miura.
• This reply was modified 4 years, 7 months ago by Senri Miura.

I don’t need such templating support.

Even if I removed the block to https://www.senris.com/wp302ja/xmlrpc.php, the bug of Jetpack was not improved, so I asked.

In the definition of .htaccess,

# Accept xmlrpc.php
<FilesMatch “xmlrpc.php”>
Allow from all
</ FilesMatch>

However, I got an error in Jetpack settings.

At the time of your indication, the following definitions were used.

# XML-RPC access restricted, Automattic (Jetpack) allowed
<Files xmlrpc.php>
Order Deny, Allow
Deny from all
# IP address you want to allow
# Allow from XXX.XXX.XX.XX
Allow #Automattic
Allow from 192.0.64.0/18
</ Files>
#END XML-Restrict access to RPC, allow Automattic (Jetpack)

It is not blocked as it can be accessed by Jetpack crawlers.

If the meaningless support continues, we will uninstall the bug pack plugin called Jetpack.

The installation path of WordPress is as follows.

https://www.senris.com/wp302ja/

The following file is existing.
It’s a Jetpack bug, no matter what.

https://www.senris.com/wp302ja/xmlrpc.php

Hello darnelldibbles,

The installation path of WordPress is as follows.

https://www.senris.com/wp302ja/xmlrpc.php

Above file has been existed before.

Previous versions of Jetpack worked fine, but recent versions of Jetpack are behaving strangely.

• This reply was modified 4 years, 7 months ago by Senri Miura.

An error occurs in Jetpack 8.4.2 and I cannot set it!

After upgrading Jetpack to the latest version (8.4.2), the following error appeared on the Jetpack setting screen and I could not proceed at all.

Unable to insert blog. Please try again or contact support.

I get the same error when I disable all the plugins, uninstall and reinstall Jetpack, and enable it.
Jetpack is much worse than previous versions.

If this situation persists, unfortunately Jetpack seems to have no choice but to uninstall.

The server environment is as follows.

WordPress version 5.4
PHP version 7.1.33 (64bit)
MySQL version 5.7.29-log
cURL version 7.29.0
cURL SSL version NSS / 3.28.4
Server Apache
Operating system Linux
PHP SAPI cgi-fcgi

• This reply was modified 4 years, 7 months ago by Senri Miura.

I just updated Jetpack to the latest version 8.4.2,
As before, I got the following error:

Site health status

1 fatal problem

Wpcom Connection Test

My site name is not connected .: 200

By the way, the non-SSL site (http) that I manage also updated Jetpack to the latest version, and no fatal error occurred.

Correction of description mistake.
My site is at the following URL:

https://www.senris.com
(Rentaled by coreserver.jp)

The server security setting cannot be changed due to rental servers.

Hello! James Huff

Thank you for your reply.

My site is the following URL.
https://www.senris.com
(Rentaled by coreserver.jp)

Even if you unblock the XML-RPC, problem 3 still occurs.
Following this advice from other moderators and Jetpack supporters, I tried the following actions, but they were not resolved.

a. Disable & uninstall Jetpack
b. Disable all other plugins
c. Install & activate Jetpack
d. Activate all other plugins

or

a. Disable & uninstall Jetpack
b. Install & activate Jetpack

However, there are no plans to use Jetpack’s CDN function or other extended functions in the future, and for the time being, the integration between Jetpack and WordPress has been completed, so I plan to continue using it in this state.

• This reply was modified 4 years, 7 months ago by Yui.
• This reply was modified 4 years, 7 months ago by Senri Miura.

Hi darnelldibbles,

I’ve already contacted Jetpack Support.
Thank you for this time.

P.S.

After performing the above procedure to disable all plug-ins of the encrypted site (senris.com), a serious problem occurred on the site after the plug-in was activated.
And the database was restored to the normal state to restore the website to normal status I have to start over from restoration.

Therefore, please pardon the test of disabling the plug-in in the future.
In the site health check, a fatal error that the connection has been cut is issued, but actually the connection between Jetpack and WordPress is in place, so there is no particular problem in operation, so I think I will operate my site in this status for the time being.
We would like you to fix the bug of Jetpack so that it works only by replacing Jetpack. Those that are not are unfortunately useless.