Bobcares

WordPress Loopback cURL Error 28 | Troubleshooting Tips

by | Sep 26, 2022

In this article, we will look into the details of “cURL error 28, loopback request cannot complete on WordPress site”. Bobcares, as a part of our WordPress Support Services offers solutions to every WordPress query that comes our way.

“cURL error 28, WordPress could not complete a loopback request”

WordPress and a number of other web apps transmit and receive data requests over URLs using the PHP module called cURL. Since it is a PHP library, we have to make sure we have the recent version of PHP so that the cURL version will also be up-to-date.

wordpress loopback curl error 28

The cURL error 28 is a fairly frequent WordPress REST API problem that can affect a website’s performance and possibly lead it to behave strangely. WordPress manages a variety of API queries using cURL. It is essential to how WordPress functions in the backend. So, if we don’t configure the site correctly, WordPress can’t function properly.

When does the error appear?

WordPress sends and receives data requests via the REST API (a programming approach). If these queries time out, a serious issue titled “The REST API encountered in error” will appear in the Site Health report. We get additional error details when we expand the error, stating:

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

We also notice a problem with the message “Your site could not complete a loopback request”. The following description will appear when we expand on this problem.

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

So when the system is unable to fulfill the server’s request for data within the timeout period, we will encounter the cURL error 28 on the WordPress site. There are a number of causes for the cURL to timeout, including the DNS server not functioning properly, which would fail HTTP requests and result in a cURL timeout error in WordPress, or the WordPress firewall plugin denying the REST API request because it considers it to be suspicious behavior.

How to fix cURL error 28 on WordPress?

The two main solutions we advise for fixing the issue include:

  • Disable firewall: After temporarily disabling the firewall, go to the site health report. If there is no error, then examine the WordPress firewall logs and find those API requests that causes the error previously. So we can find the origin of the issue or we can configure the firewall settings to not restrict authorized API requests.
  • Disable plugins: Deactivating all WordPress plugins is the quickest way to determine which one is causing the problem. After that, check the Site Health report once more to see if the problem has been resolved. If the problem is fixed, we can begin activating each plugin one at a time until the problem recurs.

[Looking for an answer to a different question? We’re only a click away.]

Conclusion

In this post, we include details about cURL error 28 and the loopback issue on the WordPress site. We also include the methods from our Support team to fix the issue.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF