• Recently we have changed our main site to SLL. So (network) administration is done over HTTPS.
    This works fine for the main site, and some ‘child sites’. However not every site makes use of SSL and therefore is configured to use http. Also this works fine.
    The only problem is upgrading WordPress.
    When trying to upgrade a site that is configured to use http (without S) the final step, network upgrade, fails when there is no HTTPS connection for a site.
    So I created self-signed certificates as a workaround, but now it fail with this error: Peer’s certificate issuer has been marked as not trusted by the user.
    The main error is that the network upgrade fails to change the connection to HTTP although this is set in the (child) sites configuration, second where can we “trust” a certificate?

Viewing 2 replies - 1 through 2 (of 2 total)
  • You should try adding this to your functions.php. It will allow your server to make https calls to itself without verification (this is relatively safe):

    add_filter( 'https_local_ssl_verify', '__return_false' );
    Thread Starter Marcel Rothuizen

    (@marcel-rothuizen)

    Thank you for the reply.
    It did not work, however triggered by your answer I looked in the core files and found there was an apply filter in class-wp-http-sreams.php.
    Added the line
    add_filter( ‘https_ssl_verify’, ‘__return_false’ );
    to this file and it works just fine.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Peer's certificate issuer has been marked as not trusted by the user.’ is closed to new replies.