kfroment

BTW just been told that it should be possible to remove ‘https://’ and the browser should do the right thing, although I’ve not tested this.

Hi, Ok that works. I’ll look out for an update. While I was looking for an answer on the net someone said that WP have not provided a method to set the CA cert. Not sure that I believe that….

Thanks very much for your help.

Hi, I still seem to be getting the same problem:

Notice: wp_setcookie is deprecated since version 2.5! Use wp_set_auth_cookie() instead. in /var/www/html/wordpress/wp-includes/functions.php on line 3573
Error [ wp_cassify_do_ssl_web_request ] : Peer certificate cannot be authenticated with known CA certificates

I assume your change should just switch the cert verification off, rather like: curl –insecure would do?

I also tried restarting httpd just in case.

Thanks

Note that the recommended version of PHP for use with WordPress has just been changed to 5.6 or greater.

Just spent a few hours going around in circles on this issue so I thought it would help to post my solution.

I have built my own in-house server in order to develop an external site. We had the following setup:

Apache 2.2.15
CentOS 6.7
MySql 5.5
PHP 5.4.18
WP 3.4

We found that we were unable to upload some images to the media library, we were seeing the “HTTP Error” message. The issue didn’t seem to be related to file size, since I could upload some very large images.

We found after a bit of experimenting that the problem was only seen if the image included meta data, for instance “Author”. If this information was deleted the image could be uploaded.

Using the dev tools in the browser it could be seen that the server was not responding to the HTTP POST. So looking in the apache error log segmentation faults could be seen. This means that an apache process was trying to access memory it does not have permission to and is therefore killed. Hence the reason for the no response.

After a lot of searching and trawling thought PHP bug reports we decided that PHP was the cause of the problem. So bearing in mind that PHP 5.4 will soon be deprecated we decided the quickest thing to do was to upgrade to 5.5.28. This seems to have fixed the problem.

You may find that asking you hosting company to upgrade PHP may solve your problem, which looks very simular to mine.