RSS Fails after Security Certificate Renewal

Hi GL_Frothy,

Last year and this year, I was able to see the RSS feeds manually. However, the RSS readers I'm using cannot retrieve the information and are reporting the same errors.  The 3rd party systems that are having issues reading the feed are IFTTT and Zaiper.  Both of these separate systems are reporting the same issue with the the rss server certificate.

"ExternalHTTPSConnectionPool(host='drms.guildlaunch.com', port=443): Max retries exceeded with url: /feeds/news/?guild_display_id=2339585&gid=279736 (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])")))"

I went through this post history and the recent forms, it appears the guildlaunch site certificates recently expired as well.  However, that was corrected.  It still seems that whenever the site certificate expires and is renewed, the certificates for the RSS is no longer compatible with the server (this seems identical to what occurred in 2022). I have no idea if the RSS Certificate is looking for the old Guild Launch certificate before it expired or vice versa. However, I'll do more research on this area, so I can understand what's going on better and I'll let you know my findings.

I'm not sure how it was resolved by you last year but one thing is the same.  Both systems stopped reading the RSS feed in 2022 when our guidlaunch site certificate was renewed. The same appears to have happened this year.

Thank you for the info, this is helpful! Don't worry about spending a bunch more time researching it. I think we have everything we need to resolve this, I'll let you know as soon as we've got it worked out.

You're welcome and thank you, I'll update you on my end if I find out something too.

This is fixed! Sorry for the delay.

Ah it's alright, thank you for your help. I confirmed it's working for Zapier and iFTTT. It's no longer reporting an error, thank you so much :D

Was the solution the same as last year? 

I noticed additional script was added to the RSS feed that seems to disable certification check, was that the solution?

Want to make sure I and possibly others know, if they're experiencing the same issue now or next year.

Long story short, there's multiple ways to configure an SSL cert. Some older services require specific things to be configured that newer services don't require. So that's why it was all working in almost all contexts, except this.

That makes sense, thank you for the information and your help :)