Subscription: getting a certificate expired

[danjac]

I'm getting this error for all superfeedr websub verification callbacks:

HTTPError: 422 Client Error: Unprocessable Entity for url: https://simplecast.superfeedr.com/

We could not verify your callback Error: certificate has expired

However, my LetsEncrypt certificate is valid for another 3 months, and this issue only occurs with superfeedr (e.g. pubsubhubbub.com domains are fine and SSL verification checks are working).

[danjac]

Update: issue was having "hub.verify=sync". Removing this (or changing to async) returns a 202, but the callback is never verified with any superfeedr domains, so unclear whether it's the same issue as above or some other problem.

[donggdeng]

@danjac Did you manage to solve this? I got the same problem. Got a 202 response when sending subscribe post with "hub.verify=async", but never got a verification back from superfeedr domains. And if using "hub.verify=sync", the callback Error "certificate has expired" will be returned.

[Alkarex]

I observed the same problem today while registering to https://feedpress.me/frandroid via hub http://feedpress.superfeedr.com/ from a FreshRSS instance using Let's Encrypt (I can provide the URL privately on demand but it is basically the same HTTPS settings than https://alexandre.alapetite.fr/ )

422 We could not verify your callback Error: certificate has expired

[Alkarex]

@julien51 Ping, just in case you did not see this (cf. comment below). I am happy to help debugging if you are available.

First of all, I am sorry about the delays here. I should be much better at looking at issues here. I will try to find a way to get > notifications in emails when they happen.

Originally posted by @julien51 in #151 (comment)

[danjac]

@donggdeng I just removed Superfeedr integration. It's clear it is no longer being maintained.

[julien51]

Sorry for the delays here!
@danjac I would love to learn more. Please send me more details about the issues you're seeing?

[Alkarex]

@julien51 Another example from today: https://medium.com/@jsoverson/feed and https://feedpress.me/frandroid and https://500ish.com/feed

WebSub subscribe to https://medium.com/@jsoverson/feed via hub http://medium.superfeedr.com/ with callback https://freshrss.example.net/api/pshb.php?k=?????: 422 We could not verify your callback Error: certificate has expired

WebSub subscribe to https://feedpress.me/frandroid via hub http://feedpress.superfeedr.com/ with callback https://freshrss.example.net/api/pshb.php?k=?????: 422 We could not verify your callback Error: certificate has expired

WebSub subscribe to https://500ish.com/feed via hub http://medium.superfeedr.com/ with callback https://freshrss.example.net/api/pshb.php?k=?????: 422 We could not verify your callback Error: certificate has expired

The test is done from that server https://alexandre.alapetite.fr/ , which is using a valid Let's Encrypt certificate. It has both IPv4 and IPv6. Details on https://www.ssllabs.com/ssltest/analyze.html?d=alexandre.alapetite.fr

Downstream issue: FreshRSS/FreshRSS#5822