Support » Plugin: Really Simple SSL » mixed content filter check curl failure

  • Resolved netwisp

    (@netwisp)


    I’m having problems where the mixed content curl check started failing with error code 28 (timed out). Really Simple SSL’s help page is really unhelpful for how to track this down other than to say to contact the provider. I am the provider and I still have no idea. This server isn’t configured any differently than all the other ones where it works – plus it used to work until recently. The firewall nor mod_security are not configured to block normal requests to the website. I can also see in the apache log files the request for the URL is succeeding:

    http://www.xxx.yyy.zzz – – [06/Nov/2019:14:44:57 +0000] “GET /wp-content/plugins/really-simple-ssl/testssl/serverhttpson/ssl-test-page.html HTTP/1.1” 200 156

    Manual requests to that page also work without interruption.

    Yet Really Simple reports no data was returned in 5001 ms. What else can I do to track down this issue? It would be great to get an idea of what curl call was failing to get an idea of what is wrong. The only thing the debug section shows is that the request failed.

    Thanks in advance for any assistance.

    • This topic was modified 3 months, 1 week ago by netwisp.
    • This topic was modified 3 months, 1 week ago by netwisp. Reason: proofreading
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Mark

    (@markwolters)

    Hi,

    cURL errors are usually caused by an outdated version of cURL or PHP. What cURL version and PHP version are you using? The mixed_content_fixer_detected() function tries to check for the data-rsssl=1 marker in the page source. This request returns a timeout. The ssl-test-page check is coming from a different function. What is happening is that the cURL request cannot retrieve your homepage to check for the data-rsssl=1 marker.

    Mark

    Hi Mark,

    “cURL errors are usually caused by an outdated version of cURL or PHP. What cURL version and PHP version are you using? ”

    I’m using PHP 7.2 and Curl 7.29.0 on CentOS 7. There’s nothing “outdated” about this setup. And like I said, it was working fine before and also works fine on dozens of other wordpress sites.

    “The mixed_content_fixer_detected() function tries to check for the data-rsssl=1 marker in the page source. What is happening is that the cURL request cannot retrieve your homepage to check for the data-rsssl=1 marker.”

    Right, but there’s nothing blocking that request so I have no idea why its usually not working. Unless for whatever reason, the page request is taking longer than 5 seconds to complete? Because you’ve changed your check from directly calling curl to using wp_remote_get (which then calls curl), your help page should be updated to reflect that you now have to create filters in order to change how curl operates as it looks like wordpress is going to override any settings you try to use.

    Plugin Author RogierLankhorst

    (@rogierlankhorst)

    Hi @netwisp,

    We’ve moved from directly calling curl to wp_remote_get a long time ago, no major changes were made in the last months to how these checks work.

    The problem is, there can be several causes of a failing cURL request, mostly caused by a server configuration. It’s hard to pin down the cause without access to the server in question.

    As it’s just a check, meant to alert a user when the mixed content fixer, it’s really harmless, and can be ignored if you can verify that the html of your webpage contains the mixed content fixer marker, data-rsssl.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.