Ошибка rss wp http error curl error 28 connection timed out after 10000 milliseconds

Приветствуем вас! Вы видите ошибку cURL 28: Превышено время ожидания соединения на вашем сайте WordPress? Ошибка cURL 28 — распространенная проблема WordPress REST API, которая может повлиять на производительность вашего веб-сайта и привести к его непредсказуемому поведению.

В этой статье мы покажем вам, как легко исправить проблему cURL error 28 на вашем веб-сайте WordPress.

Что такое cURL в WordPress?

CURL — это программная утилита, используемая WordPress и многими другими веб-приложениями для отправки и получения запросов данных с использованием URL-адресов.

WordPress использует cURL для обработки нескольких запросов API. Он доступен как расширение языка программирования PHP, и ваша хостинговая компания WordPress позаботится об этом.

Библиотека cURL играет решающую роль в том, как WordPress работает за кулисами. Если он не настроен должным образом, ваш веб-сайт не будет работать должным образом.

Что вызывает ошибку cURL 28 в WordPress?

Неспособность своевременно ответить на запросы данных сервера вызывает ошибку 28 cURL в WordPress.

WordPress использует REST API (метод программирования) для отправки и получения запросов данных. Если время ожидания этих запросов истекло, вы увидите это как критическую проблему в отчете о работоспособности сайта с заголовком «Ошибка REST API».

Расширение ошибки покажет вам дополнительную информацию, включая сообщение об ошибке:

Error: cURL error 28: Operation timed out after x milliseconds with x bytes received (http_request_failed)

Вы также можете увидеть другую связанную проблему с заголовком «Ваш сайт не может выполнить запрос обратной связи». В нем будет аналогичное сообщение об ошибке со следующим описанием.

«Запрос обратной связи к вашему сайту не удался, это означает, что функции, использующие их, в настоящее время не работают должным образом».

Что может вызвать тайм-аут cURL?

Ряд сценариев может вызвать тайм-аут cURL в WordPress:

• Например, плагин брандмауэра WordPress может блокировать запрос REST API, считая его подозрительным действием.
• Если ваш DNS-сервер работает некорректно, это также может вызвать сбой HTTP-запросов и вызвать ошибку тайм-аута cURL в WordPress.
• Плохо настроенный хостинг-сервер может просто иметь очень низкий порог тайм-аута, что может помешать правильной работе определенных процессов WordPress.

Давайте посмотрим, как устранить и исправить данную проблему.

1. Временно отключите брандмауэр WordPress

Если вы используете брандмауэр WordPress или плагин безопасности, временно отключите его.

После этого вам нужно посетить страницу отчета о работоспособности сайта WordPress, чтобы узнать, решена ли ваша проблема.

Если да, то вам нужно проверить журналы брандмауэра WordPress, чтобы узнать, какие запросы API были заблокированы. Это либо определит источник проблемы, либо вы можете настроить параметры брандмауэра, чтобы не блокировать законные запросы API.

2. Отключите все плагины WordPress

Плагины WordPress создают собственные запросы API для отправки и получения данных. Если эти вызовы слишком часты или для выполнения требуется слишком много времени, это может вызвать ошибку cURL в отчете о работоспособности вашего сайта.

Самый простой способ выяснить это — отключить все плагины WordPress. Просто перейдите на страницу «Плагины»-«Установленные» и выберите все плагины.

После этого щелкните раскрывающееся меню «Массовые действия», чтобы выбрать «Деактивировать», а затем нажмите кнопку «Применить».

Теперь вы можете посетить отчет о работоспособности сайта, чтобы узнать, исчезла ли проблема. Если это устранило проблему, вы можете активировать свои плагины один за другим, пока проблема не появится снова.

Это поможет вам найти плагин, который может вызывать проблему.

3. Убедитесь, что ваш хостинг-сервер использует новейшее программное обеспечение

Следующий шаг — убедиться, что ваш хостинг-сервер WordPress использует последние версии PHP, библиотеки cURL и OpenSSL.

Вы можете проверить это, просмотрев вкладку системной информации на странице «Инструменты»-«Здоровье сайта».

Просто перейдите на вкладку «Информация» и разверните раздел «Сервер». Отсюда вы можете получить информацию о программном обеспечении, установленном на вашем хостинг-сервере WordPress.

В идеале ваш сервер должен использовать PHP 7.4.13 или выше, curl 7.74.0 или выше и OpenSSL 1.1.1 или выше.

Если это не так, вам необходимо связаться с вашей хостинговой компанией и попросить их обновить программное обеспечение для вашей учетной записи хостинга.

4. Устранение проблем с небезопасным контентом SSL

Если ваш сайт использует HTTPS / SSL, но он не настроен должным образом, это также может привести к тому, что ваш веб-сервер заблокирует небезопасные запросы cURL.

Точно так же, если ваш веб-сайт не использует HTTPS / SSL, но он сделал вызов API с использованием URL-адреса HTTP, то эти запросы тоже не будут выполнены, и вместо этого вы можете увидеть следующую ошибку cURL:

Ошибка: ошибка cURL 7: не удалось подключиться к порту localhost 443: в соединении отказано (http_request_failed)

Чтобы исправить это, вы можете попросить своего хостинг-провайдера переустановить сертификат SSL для вашего сайта.

5. Обратитесь за помощью к поставщику услуг хостинга

Если описанные выше действия не помогли устранить ошибку cURL 28 то, проблема, скорее всего, связана с средой хостинга.

Есть много факторов, которые могут контролироваться и исправляться только вашей хостинговой компанией. Например, если их DNS-серверы не могут своевременно разрешать запросы, это приведет к тайм-ауту запросов cURL.

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

Просто отправьте им запрос в службу поддержки с подробными сведениями об ошибке, и их технический персонал сможет устранить неполадки и применить исправление для ее решения. Ну что, у нас на этом все. Всем пока!

С уважением Вячеслав и Валерия!

Понравился материал? Поделитесь с друзьями!

The digital world is currently experiencing incredible growth and change. Competition leads to the search and development of new ways to capture the market, as well as tools that could do this as efficiently and quickly as possible.

Due to the need to be the most competitive in their niche, digital applications are increasingly being improved and updated providing their users with a wider range of options and capabilities. Which in turn leads to the fact that applications require regular updates and corrections to maintain maximum efficiency. However, with this approach, there is one drawback – a fairly frequent update often leads to appearing more compatibility errors.

In our example, such kind of errors was caused by the new version of WordPress 5.2 and the introduction of a new tool called Site Health.

You may have already seen similar errors when using the new Site Health tool. Their description on the Status page of Site Health tool is as follows

The REST API encountered an error
The REST API request failed due to an error.
Error: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received (http_request_failed)

Your site could not complete a loopback request
The loopback request to your site failed, this means features relying on them are not currently working as expected.
Error: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received (http_request_failed)

What causes the issue

REST API and loopback requests issues due to cURL error 28 is happening due to the fact that PHP script in curl waits for the session to free itself from the first script that calls the API.

In most cases, the real reason of the above errors is the incorrect mechanism for using PHP sessions within plugins or themes when they are using the session_start () function.

For example, within some plugins or themes, you can find a similar to below piece of code that is responsible for a PHP session activation and may cause the above errors.

function custom_session_init()
{
    if ( !session_id() ) {
        @session_start();
    }
}

Manually check for plugins and theme compatibility

One of the best way to find the source of the issue is to deactivate all plugins and switch to a default WordPress theme like Twenty Twenty or similar. If issues disappear then you need to activate your plugins one by one, until you will see the error on Status tab of WordPress Site Health tool. Then you need to check your custom theme by activating it and disabling all plugins.

Step by step guide:

1. Create your WordPress site backup. You can do this manually or by using a backup plugin such as BackupBuddy
2. Log in to your WordPress site
3. Go to Appearance -> Themes
4. Install and activate the latest default WordPress theme, for example, Twenty Twenty. Be careful, in some cases(custom themes), the settings or widgets may be reset.
5. Go to Plugins -> Installed plugins
6. Choose all plugins and deactivate them
7. Activate one plugin at a time and check the Status page of Site Health tool
8. Repeat step 7 until you will find the issue
9. If you do not find the issue during plugin check than keep all plugins deactivated. Switch to your custom theme and check whether your theme causes the issue.

How to fix REST API and Loopback request issues due to cURL error 28

1. WordPress Native PHP Sessions Plugin

According to the statement of the WordPress team – WordPress does not use sessions in any way at all. All user states controlled with cookies.

It also means you should avoid using a session within your code for WordPress. However, if your site or plugin requires using PHP sessions for some specific tasks and you can’t avoid using sessions, you can try WordPress Native PHP Sessions Plugin.

The plugin will not solve all session based issues, but in the particular case it may help. If after installing this plugin errors will still be present, you need to consider other solutions to this problem using one of the tips below.

2. Use session_write_close()

PHP sessions created with session_start() function may cause issues with REST API and loopback requests due to cURL error 28. According to recommendations of WordPress core team active PHP session should be closed before making any HTTP requests

In order to close an active session, you can to use one of the two options below

1) If you need to make changes to the session, then after entering the data, close the session from writing:

session_write_close(); 

2) If you are sure that you do not need to make changes to the session data, use the read_and_close option when starting the session:

session_start([
    'read_and_close' => true,
]);

3. Use cookie

A cookie is a small portion of data which web server sends to the user’s browser. After receiving the piece data, the browser saves it locally on computer. Next time when you are requesting another page from the same server, browser sends the cookie back to the server inside Cookie HTTP header.

Usually, cookie used for recording and analyzing user behavior, storing using preferences and settings, shopping carts, logins, and any other data that server should remember.

How to create, update and delete cookie

In order to set cookies we need to use the PHP function setcookie(options) which can accept various options, such as:

• Name – name of the cookie
• Value – a piece of data which you want to store
• Expires – time during which cookies exist
• Path – the path on the server in which the cookie will be available on
• Domain – the (sub)domain that the cookie is available to
• Secure – Indicates that the cookie should only be transmitted over a secure HTTPS connection from the client
• httponly – When TRUE the cookie will be made accessible only through the HTTP protocol. This means that the cookie won’t be accessible by scripting languages, such as JavaScript

setcookie(name, value, expire, path, domain, secure, httponly);

Create

To create cookies, you just need to add a few simple lines of PHP code to function.php file of you active theme or inside your custom plugin files. In the example below, you can see how to create a ‘map_data cookie’ cookie with 30 days lifetime which containing value ‘John’

$cookie_name = 'mwp_data_cookie'; // set the name of the cookie
$cookie_value = 'John'; // set the value of the cookie
$cookie_expire = time() + 60*60*24*30; // set cookie lifetime for 30 days
setcookie($cookie_name, $cookie_value, $cookie_expire); //  30 days

Next piece of code will show you how to receive cookie value:

// Now you can receive cookie value
if(!isset($_COOKIE[$cookie_name])) {
        print 'Cookie "' . $cookie_name . '" does not exist';
} else {
        print 'Cookie "' . $cookie_name . '" value is:'.$_COOKIE[$cookie_name];
}

Update

In order to update cookie you need to overwrite it with a new one by using the same name.

$cookie_name = 'mwp_data_cookie'; // set the name of the cookie
$cookie_value = 'John Doe'; // set updated value of the cookie
$cookie_expire = time() + 60*60*24*30; // set cookie lifetime for 30 days
setcookie($cookie_name, $cookie_value, $cookie_expire); //  30 

Delete

If you want to delete the cookie you need to set date in the past, to trigger the removal process.

$cookie_name = 'mwp_data_cookie';
setcookie($cookie_name, '', time() - 3600); // set expiration date 1 hour ago

If you don’t know how to program or don’t want to do it on your own, then you better find a good developer and assign this task to him. Or you can just contact us

See Also: WordPress site health guide: How to get 100% check score?

Although WordPress is a reliable Content Management System (CMS), it’s not infallible, especially when you’re making high-level customizations to the software. Therefore, you might sometimes run into WordPress errors. One of these is “cURL error 28: connection timed out.”

The good news is there are a few ways to fix the cURL error 28 in WordPress. These methods range from simple fixes, such as deactivating your plugins, to more advanced procedures, like updating your SSL settings.

In this post, we’ll explore the cURL error 28 and its causes. Then, we’ll explain how to solve this issue in WordPress using six different methods. Let’s get started!

What Is the cURL Error 28 in WordPress?

Client URL, also known as cURL, is a command line tool. Simply speaking, it transfers data to and from a server through URLs.

In the context of WordPress, the CMS uses cURL within the REST API. cURL handles API requests, enabling your website to access and transmit data to its server and corresponding database.

Here’s what that process looks like:

This data transfer process takes a certain amount of time. However, if it takes too long, it can time out and display the “cURL error 28: connection timed out” message.

You will typically see this message in the Site Health section of your WordPress dashboard. The error will have the headline “The REST API encountered an error”. Clicking on this heading will expand the message, where you might see the following:

Error: cURL error 28: operation timed out after x milliseconds with x bytes received (http_request_failed)

Alternatively, you may see this related error message:

The loopback request to your site failed, this means features relying on them are not currently working as expected.

Although WordPress is reliable, it’s not infallible- which is where troubleshooting guides like this come into play! 🚀Click to Tweet

What Causes the “cURL Error 28: Connection Timed Out” Error?

There are a few reasons you might be seeing the cURL error 28. For example, your WordPress firewall might interpret a particular REST API request as suspicious. Then, it will prevent it from completing in an attempt to protect your website against malware or other security threats.

Alternatively, a faulty or poorly-configured DNS server may prevent WordPress from loading the HTTP requests correctly. The DNS server receives domain name requests and translates them into IP addresses, sending users to the correct websites. If this process doesn’t work properly, it can time out and throw the cURL error 28:

Furthermore, your hosting provider may have put a low timeout limit on your server. This configuration means WordPress doesn’t have the time it needs to transfer the data between your website and its database.

Finally, WordPress plugins can cause this error message. Third-party software may contain code or scripts that interfere with the cURL data transfer process.

How To Fix the cURL Error 28 in WordPress (6 Methods)

In this section, we’ll explain how to fix the cURL error 28 in WordPress. We recommend trying each method in turn until the error message disappears.

It’s also worth considering using a staging site for this process. Then, you can troubleshoot the problem without affecting your live site.

With a Kinsta hosting plan, you can upgrade to premium staging environments. Then you can use up to five different environments, easily accessible from your MyKinsta dashboard.

Once you’ve fixed the issue on your staging site, you can push the changes live to solve the problem on your live website. Let’s start by explaining how to temporarily disable your firewall.

1. Temporarily Disable Your WordPress Firewall

We briefly touched on the idea of a WordPress firewall before. Essentially, this WordPress security mechanism filters suspicious traffic and prevents it from reaching your website. Sometimes, it might also be incorrectly blocking a legitimate REST API request and causing “cURL error 28: connection timed out.”

To verify if the firewall is causing the error, you’ll want to disable it temporarily. This process will differ slightly depending on your chosen software. We’ll show you how to do this with the Wordfence plugin.

In your WordPress dashboard, head to Wordfence > Firewall. Then scroll down to Web Application Firewall Status:

Select Disabled from the dropdown menu and click on Save Changes. Next, we recommend checking to see if your website still shows the cURL error 28.

After that, re-enable your firewall after a few minutes and see if it causes the error again. If so, consider choosing a different firewall plugin or contacting the plugin developers for further assistance.

2. Deactivate Your WordPress Plugins

Any of the WordPress plugins on your website could be causing the connection timeout error. Since you won’t know until you try them, this approach is all about trial and error. You’ll need to deactivate all your plugins and reinstall them one by one.

If you have access to your WordPress dashboard, this process is straightforward. Simply navigate to Plugins > Installed Plugins and check the top left box to select all of them. Then, click on Deactivate in the Bulk actions dropdown menu and hit Apply:

Alternatively, if the cURL error 28 is blocking access to your WordPress dashboard, you’ll need to manually disable your WordPress plugins. To do this, connect to your site with an SFTP client such as FileZilla.

Then, locate your wp-content folder. It should have a sub-folder called plugins:

Rename this folder to “plugins-old”. This will deactivate all of the plugins on your website. Next, you can log in to your WordPress dashboard and reactivate each tool until you find the one causing the issue.

Once you’ve found the problem plugin, you might consider downgrading WordPress until you can find a permanent solution. Otherwise, you can uninstall the plugin and look for alternative software for your site.

3. Explore Your SSL Settings

A Secure Sockets Layer (SSL) certificate is an essential security feature. When working correctly, it provides an encrypted connection between visitor browsers and your WordPress website.

However, an improperly installed or configured SSL certificate can cause issues on your website and block what it considers “insecure” requests. Therefore, it might trigger the cURL error 28 or other SSL connection errors such as cURL error 7.

First, you can verify if your SSL certificate is installed correctly by running an SSL check with the Qualys SSL Labs test. Just enter your hostname into the box and click on Submit. You’ll then receive a report highlighting any issues:

As you can see, our Kinsta hosting plans come equipped with a Cloudflare SSL certificate, and the above report shows no issues.

However, if you identify a problem with your SSL certificate, you can reinstall and reconfigure it, making sure you do so properly. To be sure, you can follow these instructions on how to correctly install an SSL certificate. After that, you can check to see if this has resolved the error.

4. Verify Your DNS Settings

As we briefly explained before, a poorly-configured DNS server can prevent WordPress from processing HTTP requests. This can throw the cURL error 28.

You’ll need to contact your hosting provider if the issue is with the DNS server itself. Your web host may be experiencing issues that prevent the server from processing requests before they time out.

Since you can’t control this process on your end, we recommend raising a support ticket with your host. This way, the support team can help you troubleshoot the issue and propagate the new DNS settings to put them into effect.

You can also verify DNS settings on your end. This method will be appropriate if you suspect that the issue is with your device (i.e., your computer).

You can adjust your DNS settings in Windows by pressing Windows + I. Then head to Network & internet and click on either Ethernet or Wi-Fi, depending on how your computer connects to the internet. Next, select the properties option for your connection:

Now open the settings for the DNS server assignment:

Select Manual from the dropdown menu and click on the slider next to IPv4:

In the Preferred DNS box, you can enter any of the following DNS addresses:

• Cloudflare: 1.1.1.1
• Google Public DNS: 8.8.8.8
• OpenDNS: 208.67.222.222

Then add one of the others to the Alternate DNS box. Remember to hit Save when you’re done. You may need to restart your computer before the changes take effect.

5. Check Your Server Limits and cURL Version

Outdated software or limited server resources may cause cURL requests to time out. For example, outdated PHP, cURL library, or OpenSSL could trigger the cURL error 28.

To check on this, head to Tools > Site Health > Info > Server in your WordPress dashboard:

You can read our article on the ideal WordPress PHP and server requirements to see if the values match up.

If they don’t, you can follow our guide on how to update your PHP version. Additionally, you can contact your hosting provider for further assistance or request to update the server configuration.

It’s also important to have some awareness of your website’s PHP memory limit and PHP time limit. This is because WordPress can time out when processing REST API requests if these limits are too low. As a result, this could cause a “508 resource limit is reached” or cURL error.

Again, your hosting provider generally sets the maximum values for these limits. Therefore, you’ll need to contact them if you’d like to increase the limits.

6. Contact Your Hosting Provider for Assistance

Finally, you may have tried all the troubleshooting methods in this tutorial, but you still see “cURL error 28: connection timed out”. While this can be frustrating, you have one last option: going directly to your web host for help.

If you’ve chosen a reliable hosting provider, you should have access to different support channels, such as live chat or a ticketing system. For example, at Kinsta, we provide live messaging and speedy responses:

When you contact your hosting provider, make sure to give as much information as you can about the error you’re seeing. Then your host will be better equipped to troubleshoot the issue.

Whether you want a simple fix, such as deactivating your plugins, or a more advanced procedure, like updating your SSL, this guide has you covered 🛠Click to Tweet

Summary

“cURL error 28: connection timed out” can be frustrating to see when you’re working on your WordPress website. Fortunately, there are a few ways to troubleshoot this issue.

To fix the cURL error 28, we recommend starting with easy solutions like temporarily disabling your WordPress firewall and deactivating your plugins. Then, you can move on to checking your SSL and DNS settings, along with your server resource limits. Finally, if all else fails, it might be time to contact your web host for assistance.

Are you looking for a hosting provider to help you with any technical issues? Our Kinsta managed WordPress hosting packages come with 24/7 premium support. Plus, you’ll have access to our Kinsta APM tool for monitoring your website and improving its performance. Check out our plans today!

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

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