Senri Miura

Correction of description errors (the following is correct)

However, for encrypted sites of “https”, following the steps to enable Jetpack and perform a site health check, the same fatal error was displayed as before.

Wpcom Connection Test
My site name is not connected.: 200
Contact Jetpack support.
After all, encryption sites don’t seem to have improved.

Hi Darnelldibbles,

Thanks for the detailed explanation for the solution.
I tried it immediately.
This time I experimented with two websites.
One is a “https” site (https://senris.com) and the other is a non-public, “http” unencrypted site.

Report the result.

For unencrypted sites with “http”, following the steps to enable Jetpack and perform a site health check, no fatal error was displayed.
For unencrypted sites, Jetpack seems to work properly with the above steps.

However, for non-encrypted sites of “https”, following the steps to enable Jetpack and perform a site health check, the same fatal error was displayed as before.

Wpcom Connection Test
My site name is not connected.: 200
Contact Jetpack support.

After all, encryption sites don’t seem to have improved.

Today, Jetpack has been updated to 8.4.1, but the following error is still displayed.

1 fatal problem

Wpcom Connection Test

My site name is not connected .: 200

Contact Jetpack support.

The same applies if you downgrade WordPress to 5.3.

Hello darnelldibbles,

Thank you for your reply immediately.
Unfortunately, not all issues seemed to be communicated.

Not all problems have been solved yet!

My website diagnostics “Site Health Check” still shows fatal errors.
The same phenomenon occurred on my other test server. As a trial, it was the same even if I downgraded to WP5.3.2. Isn’t this a bug in the Jetpack plugin (site-health.php?)?

Site health status
Fatal problem
“My site name” is not connected .: 200

Right now, after setting the Jetpack again after a while, I successfully connected to WordPrees.
Jetpack’s server may have had a problem, and Jetpack technicians may have fixed the problem, anyway I report that the “403 error” of problem has been resolved. (200 error is unresolved)

Although there is a time lag, the following measures were taken for restoration for your information.

1. Add the following sentence to “.httaccess” (essentially unnecessary)
# Accept xmlrpc.php
<FilesMatch “xmlrpc.php”>
Allow from all
</ FilesMatch>

2. Uninstall Jetpack plugin and install it again

3. Activate Jetpack and go to settings (if failed, go to step 4)

4. Disable and enable Jetpack plugin

5. After a while, enable Jetpack and configure again

After that, when the site health check was executed, “xxxxxxxx Not connected.: 200” was still displayed as “1 fatal problem”, so this problem has not been resolved.

By the way, even after uninstalling the plug-in “Jetpack” and installing and setting again, the following error was also displayed and I could not proceed to the setting.

The Jetpack server was unable to communicate with your site https://www.senris.com/xxxxxxx [HTTP 403].

Hello carike,

Thank you very much.
Immediately, I will ask a question to “Jetpack ’s support forum”.

2020.3.29 Addendum

Right now, the author of Transposh has contacted me.
In Transposh’s translation engine setting, It seems that it works even if Google is prioritized, so I changed the setting to Google priority.

Therefore, I opened an untranslated page (URL) and switched to English, and confirmed that punctuation processing was performed correctly. However, some sentences have not been translated, and there seems to be a time lag in translation. It is not yet known if that part will be translated in the future. Please wait for this issue.

https://www.senris.com/popcorn/?lang=en

The above page did not display well when Google was prioritized, and all text was translated when Bing was prioritized.
After all, it still doesn’t seem to work properly if Google is prioritized in the translation engine settings.

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

In addition, there is another request for improvement.
Transposh translation seems to be unable to translate in real time compared to other translation plugins. It seems that the translation server is translating through its own proxy server, causing a considerable time lag. Regarding automatic translation, we request improvement so that translation can be performed in real time.

P.S. After that, I tried using it, but there was no big problem. However, if the translation engine is prioritized by “Bing”, the translation accuracy will be inferior to Google, so in the next version upgrade, I hope you’ll improve to work with Google Translate.
And, If there is an HTML link tag in the sentence(check “Disable html entities break”), it cannot be translated well. I hope this problem also will be improved in the future.

This morning, I’ve chatted with the author of Transposh and learned how to fix a Japanese translation bug that occurred with Transposh (V1.0.6.1).
With the following settings, you can now convert correctly!

? Translation Engines ? Select preferred auto translation engine ? Bing at the top (Bing / Google / Apertum / Yandex / Baidu)
? Advanced ? Parser related settings ? Check “Disable punctuations break”

Thanks to the author!

Though my PHP version is 5.3.3, in the latest version 1.6.3 of Easy FancyBox, my server had occurred parse error, too.
Thus I’ve corrected the PHP code in order to above. In the result, this parse error has fixed.
mrtvy, thank you so much.
I hope this problem will be solved in next version up soon.

As other issue, I cannot select a translation engine in Automatic Translation Settings Screen.
See at https://senris.com/transposh/translation-settings.jpg