RSSNext / RSSNext/Folo

Self-hosted RSS feeds fail to auto-update after 2 days, affecting usability

Open
#4,550 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug platform: desktop platform: mobile
Dominant language
TypeScript
Stars
39k
Forks
2.1k
Avg merge
1d 4h
Merged PRs (30d)
10

Description

Platform

Desktop - macOS, Desktop - Windows, Desktop - Linux, Desktop - Web, Mobile - iOS, Mobile - Android, Mobile - Web

Describe the bug

Hi, I encountered a persistent issue with self-hosted RSS feeds in Folo.

Description

I deployed an RSS service using we-mp-rss (for parsing WeChat public accounts) and exposed it through a public URL.
The feed is hosted on a private cloud server and is automatically updated daily.

During the first and second days, Folo correctly detected and loaded the updated content.
However, starting from the third day, Folo stopped updating the feed — even though the RSS source itself continued to refresh daily.

For example:
If I subscribed to the feed on October 7, Folo automatically updated on October 7 and October 8,
but from October 9 onward, no new content appeared, even though the feed itself had changed.

If I unsubscribe and then re-add the same RSS link, Folo immediately recognizes and displays the latest entries again.

Evidence
  1. The RSS feed has already updated content
Image
  1. Folo remains stuck at October 8
    (Note: In a previous test, it stayed stuck at September 25. When I reloaded the subscription on October 7, it started updating properly for October 7–8 again.)
Image
  1. After unsubscribing and re-adding the feed, Folo correctly loads the new content
Image

I’ve tried several approaches, including rebuilding the self-hosted RSS service,
but the problem persists — Folo always stops updating automatically after about two days.

Could you please look into this issue? It would greatly improve the experience for users relying on self-hosted RSS feeds.
Thank you for your time and your great work on Folo!

Entry ID

No response

Relevant Information

No response

Reproduction Video

No response

Environment

No response

Validations
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • This issue is valid
Contributions
  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Reproduce the issue with the described self-hosted we-mp-rss feed and compare feed updates before and after the two-day point. Done means the existing subscription continues displaying newly published entries without being removed and re-added.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.