SSL Problems when "Upgrading Network" w/4.2.3

  • I just tried to update our WordPress install to 4.2.3. The update itself seemed to go OK, but when I tried to upgrade the individual sites I get this error:

    Warning! Problem updating https://swwdev2.unx.sas.com/blogs/wp.dev/globaltags. Your server may not be able to connect to sites running on it. Error message: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:func(144):reason(134)

    It says Warning, but it halts the process. Nothing is written to the debug log. We know our server’s SSL certificates are bad, but this hasn’t been a show-stopper before. The Unix sysadmin says he can’t fix our certificates without upgrading to a new version of Linux, so this is a real roadblock. In the past things like plugin updates have warned about the certificate, then tried a non-SSL connection and kept trucking.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter hallcp

    (@hallcp)

    Is there some way to escalate this issue? It’s still present in 4.2.4.

    Charles.

    I dont think this is an issue in WP itself. We have a development environment that has this same issue but can easily be worked around. My best advice is to disable SSL on your host (either in Nginx or Apache) and serve the site on Port 80 instead of Port 443. Then run the the network update. If you still want SSL afterwards (without a valid cert) you can re-enable the site to run on Port 443.

    Thread Starter hallcp

    (@hallcp)

    I doubt we can alter our server config because a lot of other stuff runs on it, but this sounds like a really clever solution.

    Can you tell me what change I would need to make in WordPress to make it use 80 instead of 443? Or do I just add ‘sslverify’=>false to the call in wp-admin/network/upgrade.php?

    Although I still say this is a bug in WordPress. And I’m curious as to why it is surfacing now, since our SSL has been broken for ages. This particular upgrade.php file does not appear to have changed in recent updates.

    Thanks!

    To enable / disable the site running on port 443 (ssl) it should be server configuration for the domain the site is on and probably wouldnt affect other things on the server.

    Here is an example for Nginx – https://rtcamp.com/wordpress-nginx/tutorials/ssl/thawte/

    Hope this helps.

    Thread Starter hallcp

    (@hallcp)

    Your example is quite beyond me!

    Are you suggesting that we disable the current port 443 and instead have whatever is happening at port 80 also listen to 443? Simply disabling Port 443 would just cause a failure when WP attempts an SSL connection, wouldn’t it?

    This is a corporate intranet, and we really have no need for SSL within the company, so this solution seems to make sense to me, but is that what you are proposing?

    Thanks!

    Charles.

    Yes, I’m proposing to disable using Port 443 if you dont absolutely need and given you have SSL certificate issues.

    To disable it, you’ll probably want to replace Port 443 with Port 80 which is the default port most people use.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘SSL Problems when "Upgrading Network" w/4.2.3’ is closed to new replies.