Question SSL certificate problem

Hi all,
I have recently installed the Kunena component for joomla, and today when i logged in as administrator I saw an extention upgrade for kunena. I did so and I ended up in the following message:

SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

this is a know issue, we are investigate how to fix this.

For the mean time, download kunena, and install it by the joomla installer

Hello,

You need to ask your host to have a SSL certificate to let CURL get HTTPS connection from github to download packages

When I tried to update to Kunena 3.0.7 I get the following message:

0 SSL certificate problem: unable to get local issuer certificate

Is the same issue?

Yes, this is the same issue reported in the following topics:

1. Auto-upgrade problems with K 3.0.7
2. 3.06 to 3.07 update fails Joomla 2
3. Failed upgrade to Kunena 3.0.7
4. Illegal characters found in URL
5. Know K3.0.7 bugs/issue's (sic)

In my opinion, all of these topics should be merged together so that people will find all of the information in one place instead of having to read six separate topics.

I would be interested to know if the moderators have any intention of merging these topics so that they will assist the community better by collecting the information in one place.

Like said in my previous message here : www.kunena.org/forum/k-3-0-general-quest...icate-problem#162051

"It's a server issue with some servers. Those same servers in theory would have issues pulling the Joomla core updates (3.3.6 is using GitHub)." Like said here : groups.google.com/d/topic/joomla-dev-gen...ifc_thFlE/discussion

xillibit wrote: .... it's not an issue in Kunena

Technically-speaking, the "issue" was created by an untested, unannounced change by the Kunena developers when they moved hosting of the installation packages at Sourceforge to GitHub.

xillibit wrote: It's a server issue with some servers. Those same servers in theory would have issues pulling the Joomla core updates (3.3.6 is using GitHub) ...

In effect, this says it's an end-user problem. Technically-speaking, this may be correct; however, it is not helpful to lay the blame on the end users for mistakingly trusting the auto-upgrade process when the problem was caused by an untested, unannounced change created by the Kunena developers in the first place.

What is needed here is less finger pointing and more empathy for the end users and, I'm sorry to say, there seems to be a lot more of the former attitude that seems to be on display here in recent times.

Some people has no issues to upgrade to Kunena 3.0.7 others encounter the issue described above.

Just look around on the web, you will see plenty of issues with SSL and curl:

• stackoverflow.com/questions/6400300/http...rify-failed-ca-is-ok
• serverfault.com/questions/449599/ssl-cer...l-issuer-certificate
• gis.stackexchange.com/questions/132647/s...ate-with-gdal-and-cu

xillibit wrote: Some people has no issues to upgrade to Kunena 3.0.7 others encounter the issue described above.

I searched this forum for "SSL certificate problem" and I can find no reference to this problem — in connection with the Joomla "auto-upgrade" procedure for Kunena — until the release of K 3.0.7.

xillibit wrote: .... it's not an issue in Kunena

Since this was written (in msg #6 of this topic) the message has been changed. Is this a Kunena issue or is it not?

I have some questions:

1) If people are currently using K 3.0.6 on their websites and they see the message on their Joomla dashboard: what should they do?

2) What if people see the message on their Joomla dashboard that there is an update available for Kunena?

3) If there is a "SSL certificate problem", where does this problem come from?

4) Did the problem originate because of something that has changed between K 3.0.7 and K 3.0.6?

5) If the answer to question 4 is yes, what has changed and who was responsible for the change?

6) If the answer to question 5 is that the Kunena developers were responsible for making a change, what are the Kunena developers doing about resolving the issue so that it does not occur in future?

7) In msg #5 above, I asked if the moderators have any intention of merging together the five other topics on this "auto-upgrade" issue" so that they will assist the community better by collecting the information in one place?

When the developers say that "some people" may have this problem, do you know how many people may have this problem; is it a small number or is it a significant number of people?

I think that the problem is all the add-on developers, who transferred or keep their packages for download on GitHub... same problem is also a self Joomla! Project, as they consider the place where the packages are loaded(eg. language packs, extensions etc.)... It all started here in my opinion --> developer.joomla.org/news/602-joomlacode-is-closing.html

EDIT: I think Kunena Developers find solution soon...