Jetpack произошла ошибка повторите попытку

Hey there @alexsender1965,

We’re only able to provide support in English, so I’ll be replying in English, but please continue writing in Russian if you prefer. We’ll use Google Translate to understand your replies.

I understand you’re experiencing an error when you try to load Jetpack > Dashboard. It looks like your site’s connection to the Jetpack plugin is currently broken, so we’ll want to get that resolved first and see if it clears up your dashboard error.

Jetpack communicates with your site via XML-RPC. When we try to communicate with your site, we are encountering the following error:

503 Service Unavailable
The server is temporarily busy, please try again later!

This particular error usually means that you are exhausting the available memory or resources on the site. If you get in touch with your web host and let them know you are encountering 503 errors, they should be able to check their server error logs and see what is going on.

It has been more than one week since we have heard from you, so I’m marking this topic as resolved.

But if you have any further questions or need some more help, you’re welcome to reply here or open another thread.

Просмотр 11 ответов — с 1 по 11 (всего 11)

Просмотр 11 ответов — с 1 по 11 (всего 11)

В связи с перездом на «зимнюю квартиру» и сменой интернет-провайдера, а значит сменой собственного IP-адреса, я получил неожиданный сюрприз.  Установленный мною  несравненный плагин для WordPress на этом сайте — Jetpack, принцип работы которого в сфере статистики посещаемости сайта я немного описал в статье «Сервис статистики от плагина Jetpack», выдал сюрприз от его системы безопасности: он просто не пустил меня в админпанель блога.

Плагин не дал авторизоваться из-за смены IP-адреса, посчитав мой новый потенциально опасным. Это не шутка и, что примечательно, данный «розыгрыш» произошел аж месяц спустя, после того, как я сменил провайдера! Ничего себе реакция… 🙂

Такую проблему, однако, предлагают решить сами авторы плагина. Совет открывается при переходе по ссылке в окне блокировки. Кликаем по ней и попадаем на страницу сайта плагина, в котором подробно (на английском языке) объясняется, что необходимо сделать администратору сайта, чтобы разблокировать вход в админку собственного сайта. Как оказалось, таких способа два.

1.Добавляем IP-адрес в разделе плагина на сайте wordpress.com

Для тех, кто установил плагин Jetpack, известно, что администратору необходимо автризоваться на сайте wordpress.com и, желательно, добавить туда свой сайт. Поэтому первый способ основан на том, что при установке плагина, он, сразу определив  IP-адрес администратора сайта, вносит автоматически в разряд безопасных. Но может случиться, как у меня, что при смене этого адреса, плагин почему-то определит новый адрес небезопасным (бывает такое). Для того, чтобы исправить положение, нам придется перейти на страницу плагина в wordpress.com, перейти на вкладку «My Sites» (Мои сайты»), выбрать нужный сайт (если вы установили плагин на более, чем один сайт), кликнуть в меню (в самом низу) по ссылке «Settings» («Настройки»), а затем в открывшемся меню, вызвать информацию ссылкой «Security» («Безопасность»).

Далее все просто, в нужном окне добавляем ваш новый IP-адрес и обновляем настройки. Здесь же можно добавить любые IP-адреса, которые администрация считает безопасными (это могут быть авторы контента, другие пользователи сайтом, например).

На картинке, кстати, отображенеы два моих адреса — верхний, был у меня ранее, в тот время, когда я установил плагин Jetpack.

2. Добавляем запись в файл wp-config.php

Авторы плагина предлагают так же еще один простой способ разблокировки IP-адреса. Все что необходимо сделать — добавить в файл сайта под названием wp-config.php вот такую строку :

DEFINE (‘JETPACK_IP_ADDRESS_OK’, ‘XXXXX‘);

Красным выделено число — это нужный вам IP-адрес. Замените, вставив нужный. У меня теперь это число 5.153.128.67.

Всё! Желаю всем успехов!

(Visited 45 times, 1 visits today)

Have trouble connecting Jetpack to WordPress.com? If so, here are some steps that will help you solve the problem.

Before following this troubleshooting, first check that your site is publicly available, as Jetpack will not be able to connect to it otherwise! You can learn more about why it’s necessary to have your WordPress.com account connected to Jetpack here.

Running the Jetpack Debug Tool

The Jetpack Debug Tool can identify many different causes for connection issues.

Error Messages

Seeing an error message when trying to connect Jetpack or from the Jetpack Debug Tool above?

Visit the Error Messages page to see the most common errors, their causes, and how to resolve them.

Site Health

Check your site’s health status under Tools > Site Health from the left-hand menu.

This page will run a number of different checks and provide critical information about your WordPress configuration as well as any other items that may require your attention.

Your xmlrpc.php File

Jetpack needs this file to connect to your WordPress.com account.

Start by checking example.com/xmlrpc.php (replacing “example.com” with your actual domain) in your web browser’s address bar. That page should return the following message:

XML-RPC server accepts POST requests only.

The message you see should look exactly the same, without any spaces or line breaks above or below it. Compare yours to this working example.

If you have blank lines or extra content in your xmlrpc file, you will receive an error. Please check here for fixes before you continue, and feel free to reach out to your webhost for assistance with those instructions.

Please note that your xmlrpc.php file must be in the home directory of your WordPress install. If it’s not, you can replace it by reinstalling the core files of WordPress (or asking your webhost to).

Your wp-config.php and .htaccess Files

If you or one of your plugins added code to either of these files, it may have caused a misconfiguration. You can check these guides for more information and typical settings to help revert the files back to their default state: wp-config / htaccess.

The PHP-XML Extension

The PHP on your site needs the XML extension in order to parse XML, which Jetpack needs to properly communicate with your site. Check with your webhost to make sure the PHP-XML extension is installed and active on your server.

Reinstalling and Reconnecting Jetpack

Sometimes you need to completely reset your connection between your site and our services. You can follow these instructions to accomplish that.

Cloudflare

If you are using Cloudflare on your site, check this guide to make sure Jetpack and Cloudflare are working together properly.

Plugin Conflicts

Sometimes other plugins can create a conflict with Jetpack that blocks it from connecting to WordPress.com.

To rule out a plugin conflict, deactivate all other plugins and keep Jetpack active, then try connecting again. If Jetpack connects, you can turn your plugins back on, one by one, to make sure everything keeps working.

A conflict may cause other issues in addition to not letting Jetpack connect, so check for anything else not working properly after activating each plugin. If you find that a plugin is causing a conflict with Jetpack, please reach out to that plugin’s developers to see if there is a fix to get it working with Jetpack.

Theme Issues

If you’re using a theme that’s not coded to modern standards or kept up-to-date with changes in WordPress development, then the theme could be creating issues with Jetpack’s connection or features.

Download and temporarily switch to one of the more minimal, default WordPress themes (such as Twenty Twenty Two) and see if the connection issues are resolved. If so, then you’ll need to either replace your original theme or talk to its developers to see if they can figure out where the conflict is happening and how to solve it.

Testing Your Site Speed

Your site must initially respond within 5 seconds for the Jetpack connection to work correctly.

You can check your site speed and overall performance with a variety of tools (like GTmetrix or WebPageTest) and follow up with your webhost by showing them the results. They may be able to help improve your site’s response and loading times from there.

SSL Certificates

Your SSL certificate makes sure the traffic on your site is safe and secure. Sometimes they can be misconfigured or expired, which will keep Jetpack from connecting to it. You can check for errors on your SSL certificate with this SSL Checker and test its overall health with this SSL Server Test. It should typically be graded A or A+, and you shouldn’t see any errors.

The most common SSL errors that your webhost must fix are:

• Self-signed: The certificate was not created by using standard security practices and is considered unsafe
• Missing chain/intermediate certificate: Some SSL certificates are applied to your site in multiple parts. When one or more are missing in the chain, the security becomes broken and incomplete
• Expired: Just like a domain, an SSL certificate needs to be renewed each year, or it will expire. Certificate renewals usually happen without you having to do anything, but sometimes automatic systems at your webhost may fail to do so

HTTPS Settings

Check that both the SITE_URL and HOME_URL settings under Settings > General in your wp-admin dashboard are using https before your domain rather than just http. Sites that use only http are not secure and aren’t using the SSL certificate mentioned above – https loads the certificate properly and will allow Jetpack to connect to it.

Also, make sure that all of your site’s traffic routes to https as well. For example, any requests to http://example.com should automatically redirect to https://example.com instead. Your webhost can help make sure that this happens as expected.

For more detailed information on troubleshooting SSL issues, please refer to this guide.

Server Credentials for Jetpack Backup

If you have issues adding your credentials to Jetpack Backup, we recommend contacting your webhost and asking them to provide you with this information so you can then enter it successfully into your Jetpack settings:

• Credential type (FTP, SFTP, SSH)
• Server address
• Port number
• Server username
• Server password
• WordPress full installation path

When You Should Contact Your Webhost for Support

This list of issues that must be addressed by your webhost rather than Jetpack support because they are server-related:

• SSL certificates
• Changes in IP addresses or domains/URLs
• Migration from one server to another
• Site is down or not responding
• Errors (500 / 502 / 504 / 403)
• Server resource or memory usage
• DNS problems
• Outdated server software (PHP, MySQL, etc.)
• File and folder permissions
• Problems that are still occurring even after Jetpack is uninstalled

Перейти к содержимому

#        <files wp-login.php>
#                order allow,deny
#                allow from 127.0.0.1 192.168.2.50
#        </files>