Upgraded to SSL and now Feedburner isn't Working!

[Craig Vanderslice]

I've let this go on too long!  A month or so ago I finally updated my site (cigarcraig.com) to SSL. I hadn't seen the need since I didn't sell anything or store any user data, but I was told it would give my readers a "safer" feeling to have that lock there in the address bar. Ever since I did that Feedburner hasn't been sending the e-mails out to my subscribers when I publish new blog posts. Feedvalidator gives a 404 and Ping gives me this error: Your Ping resulted in an Error "We were unable to process your ping. You must ping with a URL that exactly matches the channel link (RSS) or alternate link (Atom) in your top level feed element pointing back to your website (e.g http://myblog.blogspot.com/), or use your feed URL (e.g. http://feeds.feedburner.com/myuri)."  I even tried another mail service and got the. same issue. I put my RSS feed in a browser and it seems up to date (https://www.cigarcraig.com/feed/), so I don't know what's going on. I have users that are asking, so I want to get this back on track. Anyone know whats up and how to fix it?  Bluehost wasn't any help other than making sure my certificates are up to date.

Thanks, 

Craig

[Maks Verver]

Hi Craig,

Have you updated the source feed URL for your FeedBurner feed?

You should be able to do so on the FeedBurner dashboard at https://feedburner.google.com/, by clicking on your feed title, then "Edit Feed Details", and changing the "Original Feed" URL to your new HTTPS URL.

  - Maks.

[Matti nescio]

On Tuesday, 2 February 2021 at 18:31:40 UTC+2 craigvan...@gmail.com wrote:

 Feedvalidator gives a 404 [...] I put my RSS feed in a browser and it seems up to date (https://www.cigarcraig.com/feed/)

The http version of the feed is valid : https://validator.w3.org/feed/check.cgi?url=http://www.cigarcraig.com/feed/ 

, but the https version can't even be processed : https://validator.w3.org/feed/check.cgi?url=https://www.cigarcraig.com/feed/ 

, because there's something wrong with your SSL certificate. 

Both https://www.digicert.com/help/ and https://www.geocerts.com/ssl-checker give more details on exactly what's wrong. 

 

[Craig Vanderslice]

Of course I tried doing this. When I change it I get An error occurred connecting to the URL: internal error.  and it reverts back to the http version which, of course, isn't updating.

It did take me a while to think of that though!   

[Craig Vanderslice]

So I need to go back to Bluehost and have them do something, is what I'm gleaning from the two sites you provided?  Thanks!  I'll work on that. Your help is most appreciated!

Craig

[Craig Vanderslice]

Looking at https://validator.w3.org/feed/check.cgi?url=http://www.cigarcraig.com/feed/, it says "This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 15, column 92: Self reference doesn't match document location [help]

  Line 15 is: 
• <atom:link href="https://www.cigarcraig.com/feed/" rel="self" type="application/rss+xml" />

How and where do I look at this and/or fix it? 

Thanks, 

Craig

On Tuesday, February 2, 2021 at 12:18:03 PM UTC-5 Matti nescio wrote:

[Maks Verver]

Hi Craig,

Matti is right and the immediate problem is with your certificate. If you enter "cigarcraig.com" at https://www.digicert.com/help/ (one of the links Matti provided) it will show you what's wrong.

More concretely, it seems like you're missing an intermediate Let's Encrypt certificate. The reason the site still works in the browser is that Let's Encrypt is so common that browsers usually have intermediate certificates cached, but you cannot rely on that.

I can speculate a bit more about the root cause of the problem: your site is using Let's Encrypt. Let's Encrypt generates three output files: cert.pem (containing the server certificate), chain.pem (containing the Let's Encrypt intermediate certificates), fullchain.pem (containing both). It looks like the server is serving cert.pem but it needs to serve fullchain.pem. So it's a simple configuration error on the server. If the above is all Greek to you, please show this thread to whoever configured SSL for you, and they should be able to fix it.

 

 - Maks.