<p>Just checked 2 upgraded sites of me and to me it's working..</p>

CC BY-SA 3.0
2015-12-02T18:13:53.403Z
I upgraded 6 sites and all 6 show none of the feed. Weird.
Bryan Garrant
CC BY-SA 3.0
2015-12-02T18:09:42.553Z
2015-12-02T18:09:42.553Z
iDzine
<p>I will work with support on this directly as it appears to be an issue with our environment.</p>

CC BY-SA 3.0
2015-12-03T21:41:05.623Z
2015-12-03T21:41:05.623Z
Bryan Garrant
<p>Not a major thing but I just noticed the Craft News Feed on the dashboard is not showing.  It is still looking for <a href="https://craftcms.com/news.rss" rel="nofollow">https://craftcms.com/news.rss</a>.  Any ideas what is up with that?</p>

CC BY-SA 3.0
2015-12-02T19:58:25.127Z
Can you check your `craft/storage/runtime/logs` files for any feed related error messages?
Brad Bell
CC BY-SA 3.0
2015-12-02T20:42:58.147Z
I dont see any errors in PHP log
Bryan Garrant
CC BY-SA 3.0
2015-12-02T20:49:12.273Z
Same issue is happening on all sites we upgraded.  Both on local and production servers.  Weird
Bryan Garrant
CC BY-SA 3.0
2015-12-02T20:52:14.333Z
The widget is there but it is just not getting any values.  Can I send you the craft.log Brad?
Bryan Garrant
CC BY-SA 3.0
2015-12-02T20:58:00.383Z
Found issue: 2015/12/02 20:55:56 [warning] [application] There was a problem parsing the feed: cURL error 60: SSL certificate problem: unable to get local issuer certificate.  How can I resolve this?
Bryan Garrant
CC BY-SA 3.0
2015-12-02T22:44:23.803Z
Looks like it's a SSL certificate problem on your box: https://www.google.com/search?q=SSL+certificate+problem%3A+unable+to+get+local+issuer+certificate
Brad Bell
CC BY-SA 3.0
2015-12-02T23:07:41.270Z
@BradBell this site is just setup on local DEV environment. How can I resolve this issue?
Bryan Garrant
CC BY-SA 3.0
2015-12-02T23:10:00.943Z
@BradBell is the issue with your SSL for https://craftcms.com or some issue as we are in development mode?
Bryan Garrant
CC BY-SA 3.0
2015-12-02T23:13:17.370Z
All traffic to craftcms.com is done over SSL now (including the feed).  The error your getting is saying that the root CA on your box is outdated and your cURL can't validate that it's connecting to craftcms.com over SSL, so you or your host will need to update it.
Brad Bell
CC BY-SA 3.0
2015-12-02T23:15:19.047Z
I will look to get that updated. Just odd that it is happening in 4 completely different hosting environments.
Bryan Garrant
CC BY-SA 3.0
2015-12-03T14:34:42.643Z
Hi Brad.  On another box Craft is showing this in the craft.log: 

"2015/12/03 14:21:55 [warning] [application] There was a problem parsing the feed: cURL error 51: SSL: no alternative certificate subject name matches target host name 'craftcms.com'"
Bryan Garrant
CC BY-SA 3.0
2015-12-03T14:59:55.510Z
This worked on my local dev box:

Use this certificate: http://curl.haxx.se/ca/cacert.pem

Copy this certificate on your disk. And use this on php.ini

curl.cainfo = "path_to_cert\cacert.pem"
Bryan Garrant
CC BY-SA 3.0
2015-12-03T17:04:56.057Z
Would you mind adding that as an official answer?
Brad Bell
CC BY-SA 3.0
2015-12-03T19:28:19.900Z
It fixes the code 60 issue but not the code 51.  STill getting this error and no RSS feed.

2015/12/03 19:27:09 [warning] [application] There was a problem parsing the feed: cURL error 51: SSL: no alternative certificate subject name matches target host name 'craftcms.com'
Bryan Garrant
CC BY-SA 3.0
2015-12-03T19:41:59.990Z
Can you check this Brad? Your cert is for *.craftcms.com and you are then trying to use it with http://craftcms.com which is not correct according to wildcard rules in RFC 2818 as it is missing a subdomain. If you want to use it for just plain old craftcms.com without a subdomain, you need to add a Subject Alternative Name in the wildcard.  I am not sure if you have done this, but this may explain it better: http://stackoverflow.com/questions/4445934/wildcard-ssl-certificate-generates-error-when-no-subdomain-is-used.
Bryan Garrant
CC BY-SA 3.0
2015-12-03T19:48:13.323Z
You guys probably have it correct but I just wanted to have you check as that is what the error 51 means.  No idea why we are still getting that one.
Bryan Garrant
CC BY-SA 3.0
2015-12-03T20:47:01.910Z
I see the news feed was change from http://feeds.feedburner.com/blogandtonic to https://craftcms.com/news.rss so that explains why the 2.4 sites are working and not the 2.5 sites.
Bryan Garrant
CC BY-SA 3.0
2015-12-03T21:26:45.933Z
I have tried many fixes found online and I still get this error and the News Feed is not displaying:
 
2015/12/03 21:24:08 [warning] [application] There was a problem parsing the feed: cURL error 51: SSL: no alternative certificate subject name matches target host name 'craftcms.com'
Bryan Garrant
<control-panel><dashboard-widgets>
Craft News Feed not working after 2.5 Update
# Craft News Feed not working after 2.5 Update

(Asked by: username_0 on 2015-12-02)

Not a major thing but I just noticed the Craft News Feed on the dashboard is not showing. It is still looking for <https://craftcms.com/news.rss>. Any ideas what is up with that?

**Tags:** control-panel, dashboard-widgets

> **Comments:**
> **username_1**: Can you check your `craft/storage/runtime/logs` files for any feed related error messages?  
> **username_0**: I dont see any errors in PHP log  
> **username_0**: Same issue is happening on all sites we upgraded.  Both on local and production servers.  Weird  
> **username_0**: The widget is there but it is just not getting any values.  Can I send you the craft.log Brad?  
> **username_0**: Found issue: 2015/12/02 20:55:56 [warning] [application] There was a problem parsing the feed: cURL error 60: SSL certificate problem: unable to get local issuer certificate.  How can I resolve this?  
> **username_1**: Looks like it's a SSL certificate problem on your box: https://www.google.com/search?q=SSL+certificate+problem%3A+unable+to+get+local+issuer+certificate  
> **username_0**: @BradBell this site is just setup on local DEV environment. How can I resolve this issue?  
> **username_0**: @BradBell is the issue with your SSL for https://craftcms.com or some issue as we are in development mode?  
> **username_1**: All traffic to craftcms.com is done over SSL now (including the feed).  The error your getting is saying that the root CA on your box is outdated and your cURL can't validate that it's connecting to craftcms.com over SSL, so you or your host will need to update it.  
> **username_0**: I will look to get that updated. Just odd that it is happening in 4 completely different hosting environments.  
> **username_0**: Hi Brad.  On another box Craft is showing this in the craft.log:   "2015/12/03 14:21:55 [warning] [application] There was a problem parsing the feed: cURL error 51: SSL: no alternative certificate subject name matches target host name 'craftcms.com'"  
> **username_0**: This worked on my local dev box:  Use this certificate: http://curl.haxx.se/ca/cacert.pem  Copy this certificate on your disk. And use this on php.ini  curl.cainfo = "path_to_cert\cacert.pem"  
> **username_1**: Would you mind adding that as an official answer?  
> **username_0**: It fixes the code 60 issue but not the code 51.  STill getting this error and no RSS feed.  2015/12/03 19:27:09 [warning] [application] There was a problem parsing the feed: cURL error 51: SSL: no alternative certificate subject name matches target host name 'craftcms.com'  
> **username_0**: Can you check this Brad? Your cert is for *.craftcms.com and you are then trying to use it with http://craftcms.com which is not correct according to wildcard rules in RFC 2818 as it is missing a subdomain. If you want to use it for just plain old craftcms.com without a subdomain, you need to add a Subject Alternative Name in the wildcard.  I am not sure if you have done this, but this may explain it better: http://stackoverflow.com/questions/4445934/wildcard-ssl-certificate-generates-error-when-no-subdomain-is-used.  
> **username_0**: You guys probably have it correct but I just wanted to have you check as that is what the error 51 means.  No idea why we are still getting that one.  
> **username_0**: I see the news feed was change from http://feeds.feedburner.com/blogandtonic to https://craftcms.com/news.rss so that explains why the 2.4 sites are working and not the 2.5 sites.  
> **username_0**: I have tried many fixes found online and I still get this error and the News Feed is not displaying:   2015/12/03 21:24:08 [warning] [application] There was a problem parsing the feed: cURL error 51: SSL: no alternative certificate subject name matches target host name 'craftcms.com'  

---

## 2 answers

### Answer by username_2 on 2015-12-02. Score: 1

Just checked 2 upgraded sites of me and to me it's working..

> **Comments:**
> **username_0**: I upgraded 6 sites and all 6 show none of the feed. Weird.  

---

### Answer by username_0 on 2015-12-03. Score: 0

I will work with support on this directly as it appears to be an issue with our environment.


---

