• Resolved bzwoman

    (@bzwoman)


    Is this an issue with the plugin and/or server?
    (Note Server is running PHP 7.0.2-p10-gentoo)
    When SecSign plugin is activated SiteHealth shows these errors:
    An Active PHP session was detected
    A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.

    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 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 10001 milliseconds with 0 bytes received (http_request_failed)

    Also
    Background requests 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.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author SecSign

    (@secsign)

    Hi bzwoman,

    thanks for the notice. The plugin still seems to work as expected and we couldn’t see any misbehavior of the REST API. We are currently investigating the problems and will release an updated version once we find the cause of this warnings.

    Greetings
    The SecSign Team

    Thread Starter bzwoman

    (@bzwoman)

    This plugin is on two of my wordpress sites and both are displaying identical messages on SiteHealth. They do not reside on the same host servers.

    • This reply was modified 4 years, 6 months ago by bzwoman.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Critical Issues Detected’ is closed to new replies.