Cannot add feeds to Django Community Blog

[ndunn219]

There seems to be an issue adding feeds to the Django Community Blog. My feed (https://www.webucator.com/articles/django/feed/) was approved in October by @adamchainz, but hasn't been added. Adam thought there might be an issue with https://superfeedr.com/, which he said was sending out some obscure certificate errors.

[carltongibson]

From time to time we see an error here, but I'm at a loss as to how to debug.

I'm wondering if superfeedr.com is a reliable dependency here? 🤔

[adamchainz]

I tried to approve another feed yesterday and it also failed - is that the error you saw? Could you share a stack trace?

[sentry-io]

Sentry issue: DJANGOPROJECT-J8

[carltongibson]

SubscriptionError: ('Error during request to hub https://push.superfeedr.com/ for topic https://carrick.eu/feeds/django.atom.xml: We could not verify your callback Error: certificate has expired', <Subscription: Subscription object (1010)>, <Response [422]>)
  File "django-admin.py", line 21, in <module>
    management.execute_from_command_line()
  File "django/core/management/__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "django/core/management/__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "django/core/management/base.py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "django/core/management/base.py", line 398, in execute
    output = self.handle(*args, **options)
  File "aggregator/management/commands/update_subscriptions.py", line 33, in handle
    subscription.unsubscribe()
  File "django_push/subscriber/models.py", line 94, in unsubscribe
    return self.send_request(mode='unsubscribe')
  File "django_push/subscriber/models.py", line 135, in send_request
    raise SubscriptionError(

We could not verify your callback Error: certificate has expired

Now is that them saying our certificate has expired... 🤔

[carltongibson]

Error is being raised in Django-push here:

https://github.com/brutasse/django-push/blob/ee83ff553aa4bdf2ff969f5443971450cdd25eb5/django_push/subscriber/models.py#L136

Hitting the callback URL (the URL on our site) there doesn't raise the SSL error — our certificate is fine AFAICS.
🤔

[carltongibson]

(We don't have a lot of feeds. Fetching them each once a day ourselves might be better than a flaky dependency...)

[adamchainz]

Superfeedr looks like a useful service since it can normalize between the different feed types. But perhaps there is something up with the requests django-push is making, or perhaps our credentials have expired? Can you double check that?

[carltongibson]

@adamchainz I think this is Superfeedr reporting an error when trying to send a request to our callback URL. (Not us making a request to them.)

AFAICS they’re reporting a certificate issue, where testing the same thing manually none exists.

[adamchainz]

Yeah that is what it is, I just wanted to be sure. I found their support is on GitHub and that there's this issue open since November covering the same problem. No reply from them, so I guess they aren't maintained.

To be sure, I've emailed the support address, but I would guess it's time to try migrate off indeed. That is not a trivial amount of work though.

[carltongibson]

Might be good for the DjangoCon sprints if we don't make it before.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[carltongibson]

Again, this isn't stale. Rather we need to work out how to replace the super feeder service

(A cron job with feedparser may be enough here 🤔)