Self hosted Reply by Email stopped working after latest update

[RGJ (Richard - Communiteq)]

Your certificate chain is fine. The LetsEncrypt root certificate expiration led to many small issues worldwide. This is one of them. It’s up to FB to fix this, they are seeing a false negative.

[IAmGav (Gavin Perch)]

once you fix the ssl cert problem, get them to review the case and then they will enable your app again.

[RGJ (Richard - Communiteq)]

@IAmGav

once you fix the ssl cert problem

Problem is, there is nothing to fix on forum side of things.

[Paul_King]

Thanks guys!
I am throwing that SSL A+ report and explanation back at Facebook.

[pfaffman (Jay Pfaffman)]

@Paul_King

Facebook tech support are still saying the site landing page generates a ‘your connection is not private
NET::ERR_CERT_COMMON_NAME_INVALID’ security warning for them.

That sounds like an issue on their side with the update to the root certificate. And the people who check don’t have enough tech sense to know that.

[anon73664359]

This topic is also relevant.

Reply-by-Email was working, now broken

Our Reply-by-Email worked for two years, then stopped working 17 days ago for no apparent reason. I’ve searched the staff action logs for that time period and there were no relevant configuration changes. no upgrades, and no new plugins. What could have broken? No received emails after Sep 30: [image] They’re not being rejected either: [image] Nothing obviously related in the error logs, but there is this:

aws-sdk-core-3.112.1/lib/seahorse/client/plugins/raise_response_errors.rb:17:in…