Brizy and Brizy Pro 2.0 causes REST API error

Francesco Lanni

• July 31, 2020 00:52

Since I can't edit any PENDING ticket, I guess i have to keep entering tickets. Receiving the following error in site health when Brizy free is loaided (forget about adding brizy pro)

The Rest API encountered an error

The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

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

Your site could not complete a loopback request

Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

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 out of -1 bytes received (http_request_failed)

Background updates may not be working properly

Background updates ensure that WordPress can auto-update if a security update is released for the version you are currently using.

• Warning Could not confirm that the wp_version_check() filter is available.
• Passed No version control systems were detected.
• Passed Your installation of WordPress doesn't require FTP credentials to perform updates.
• Passed All of your WordPress files are writable.
•  
• As soon as brizy is disabled, these errors are gone. The REST API error is real because the site had zero issues before, and now it struggles just to load.

1

• 

  Francesco Lanni

  • July 31, 2020 00:53

  The following should not have been a bullet

  As soon as brizy is disabled, these errors are gone. The REST API error is real because the site had zero issues before, and now it struggles just to load.

  1
• 

  Sandra Prunici

  • July 31, 2020 09:08

  Hi,

  Thank you for reporting this. Our team are already investigating this problem. It isn't a fatal error, it is a performance message. When we will have some more details regarding this issue, we will inform you here regarding this. I'm sorry for this inconvenience.

  Best regards,
  Sandra

  1
• 

  Matthias Hahn

  • August 03, 2020 10:50

  I have the same problem... Please fix.

  1
• 

  Sandra Prunici

  • August 07, 2020 11:48

  Hi,

  I want to inform you that this problem is solved and the fix will be released in the next update.

  Best regards,
  Sandra

  0

Please sign in to leave a comment.