WordPress.org

Forums

[resolved] SSL insecure components (5 posts)

  1. happyboyblue
    Member
    Posted 2 years ago #

    Hello

    I am running 3.5.1 on http://www.lgbtnetwork.eu and I have an SSL. I have changed URL to https:// and have downloaded SSL Insecure Content Fixer and WordPress HTTPS but http://www.whynopadlock.com/check.php is showing five insecure items:

    Insecure URL: http://www.lgbtnetwork.eu/wp-includes/js/jquery/jquery.js?ver=1.8.3
    Found in: https://www.lgbtnetwork.eu/

    Insecure URL: http://www.lgbtnetwork.eu/wp-includes/js/jquery/ui/jquery.ui.core.min.js?ver=1.9.2
    Found in: https://www.lgbtnetwork.eu/

    Insecure URL: http://www.lgbtnetwork.eu/wp-includes/js/jquery/ui/jquery.ui.widget.min.js?ver=1.9.2
    Found in: https://www.lgbtnetwork.eu/

    Insecure URL: http://www.lgbtnetwork.eu/wp-includes/js/jquery/ui/jquery.ui.tabs.min.js?ver=1.9.2
    Found in: https://www.lgbtnetwork.eu/

    Insecure URL: http://stats.wordpress.com/e-201321.js
    Found in: https://www.lgbtnetwork.eu/

    These items are showing when I click view source on the page but I have no idea where they are coming from, I cannot find the reference to change it to HTTPS.

    This is driving me nuts. Please help if you can.

    Thanks

    Rob

  2. webaware
    Member
    Posted 2 years ago #

    In the Plugins admin page, the SSL Insecure Content Fixer plugin has a link "test is_ssl()". What does it report when you click it?

  3. happyboyblue
    Member
    Posted 2 years ago #

    Hi, thanks for the reply. it shows:

    is_ssl() says: no, SSL not detected

    Your server is behind a load balancer or reverse proxy.

    Please add the following code to your wp-config.php file, above the require_once:
    if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https')
    $_SERVER['HTTPS']='on';

    I have added the code to wp-admin in the line above the require_once but it is still showing this error.

    Any help would be greatly appreciated.

    Thanks

    Rob

  4. happyboyblue
    Member
    Posted 2 years ago #

    It seems to be fixed. Thanks a lot for your help

    Rob

  5. webaware
    Member
    Posted 2 years ago #

    No worries, glad it's working.

    cheers,
    Ross

Topic Closed

This topic has been closed to new replies.

About this Topic