Categories: WordPress

About the ca-bundle.crt of WordPress3.7.x.

Update information Edit(2014.Jan.30) Edit2(May.6) Edit3(Jun.22)

I wrote something about the ca-bundle.crt of WordPress3.7.x on the post.

About it, Oiram gave me A useful information. If you get the same issue “Warning! Problem updating https://SITENAME. Your server may not be able to connect to sites running on it. Error message: SSL certificate problem: self signed certificate in certificate chain.“, read the article “Error upgrading WordPress (SSL)”, and do his workaround.

Thinking back now, in my case, there were some differences from his case. Even now, I do not use his workaround. My SSL certificate system works well after updating to WordPress3.7.1. This time updating did not give me any warnings.

My server environment is very unique, so, I might have got the issue was slightly different from his.

Still now, I have two questions.

Why did WordPress ver.3.7 give me the warning about one site only in spite of there were a parent and three child sites on the same WordPress multisite?
About the setting of the ca-bundle.crt, I found out in the class-http.php. This should have the same effect on all of my sites. Why did one site only have the warning?
Do I need to use Oiram’s workaround though my SSL system works well?

Edit(2014.Jan.30):
Since January 3rd, I cannot access to the Oiram’s site. For a few people googling by the word “ca-bundle.crt” and reaching here, I uploaded the PDF version of Oiram’s workaround. 「Error upgrading WordPress (SSL)」

Edit2(May.6):
Today, I can access to the the Oiram’s site after a very long interval.

Edit3(Jun.22):
I wrote an article The solution of “SSL3_READ_BYTES:sslv3 alert handshake failure” on WordPress.

o6asan

Next Mantises on Warm Window Screens. »

Previous « Tried Windows8.1 Pro on the laptop PC (NJ2100), and failed.

View Comments

Oiram says:

2013-Nov-06 at 8:59 AM

All my sites were working just fine without workaround but I think autoupdate is the key in this situation, of course if you want it.

1. In my case I have 7 sites but I was getting this warning in 3.7 (and 3.7.1 as well) only for the first one. So I expect that to be typical (by design) behavior when WP does not have valid SSL chain for your certificate.

2. Personally I would advise to apply thinking of autoupdates of WP.
- o6asan says:
  
  2013-Nov-06 at 9:42 AM
  
  Hi Oiram.
  
  > I have 7 sites but I was getting this warning in 3.7 (and 3.7.1 as well) only for the first one.
  
  In my case, I was getting the warning in 3.7 only for the last one. It wasn't in 3.7.1.
  
  > So I expect that to be typical (by design) behavior when WP does not have valid SSL chain for your certificate.
  
  I see. By the way, I want to apply autoupdates about minor updates. I intended to update to 3.7.1 automatically, but I forgot it and clicked the button (^_^;). Next time, I will check the issue up again.