You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a self-hosted RSSHub instance deployed on a cloud server and I use Folo along with other RSS readers to read it. After 2026-7-30 (the timestamp of the last subscription update being 2026-7-30 11:38 UTC 8), almost all of my self-hosted RSSHub feeds stopped getting updates in Folo. During troubleshooting, I found the following issues:
(Attached video) When I try to add a subscription from my self-hosted feed in Folo today, like https://xxx.vercel.app/mi/crowdfunding, the link I enter gets forcibly converted to the rsshub://mi/crowdfunding format in the pop-up preview, making it impossible to actually subscribe to my self-hosted feed. After exiting the preview and going back to the subscription link entry, I noticed an orange "Folo Flavored Feed Spec" label under the link.
(Attached image) The same self-hosted feed link behaves completely differently in Folo compared to other readers. Directly accessing the self-hosted feed URL in a browser works fine, so I suspect the problem is on Folo's side.
Only one or two previously subscribed self-hosted feeds could still get updates after 2026-7-30. However, when I checked them in Folo's “Edit” button and compared them with the ones that failed to update, I found that these “self-hosted” subscriptions also had their source links changed to the rsshub:// format. But I am sure that when importing these links, they were originally self-hosted and not the rsshub:// format provided by Folo. In other words, all links that actually used self-hosted feeds stopped updating after 7-30, and the only working updates were from rsshub format subscriptions that somehow got overwritten.
Interestingly, using some other RSSHub instances doesn't have this problem. For example, https://rsshub.rssforever.com/mi/crowdfunding still works fine. But my self-hosted vercel.app domain simply can’t be imported correctly.
Since Folo's last major update was Desktop v1.12.0 on 7-31, the timing coincides closely with the appearance of this issue, so I suspect this update may have caused the problem. If the developers need my complete self-hosted feed links for verification and troubleshooting, I’m glad to provide the full URLs via email or other methods.
Please check whether your instance has been registered in the RSSHub list. After registration, it will be converted automatically. If you do not want it converted, you can delete it here.
Thanks! It did solve this problem, the self-hosted sources can get update these days. I suggest that the related documents or instructions could be updated for potential similar issues.
Glad that removing the instance from the RSSHub list fixed it, thanks for confirming. Closing, since the conversion to rsshub:// happens because the instance was registered there.
Activity
MicrowaveOven1 commentedon Sep 3, 2026
I have a self-hosted RSSHub instance deployed on a cloud server and I use Folo along with other RSS readers to read it. After 2026-7-30 (the timestamp of the last subscription update being 2026-7-30 11:38 UTC 8), almost all of my self-hosted RSSHub feeds stopped getting updates in Folo. During troubleshooting, I found the following issues:
Since Folo's last major update was Desktop v1.12.0 on 7-31, the timing coincides closely with the appearance of this issue, so I suspect this update may have caused the problem. If the developers need my complete self-hosted feed links for verification and troubleshooting, I’m glad to provide the full URLs via email or other methods.
DIYgod commentedon Sep 3, 2026
Please check whether your instance has been registered in the RSSHub list. After registration, it will be converted automatically. If you do not want it converted, you can delete it here.
MicrowaveOven1 commentedon Sep 10, 2026
Thanks! It did solve this problem, the self-hosted sources can get update these days. I suggest that the related documents or instructions could be updated for potential similar issues.
DIYgod commentedon Sep 26, 2026
Glad that removing the instance from the RSSHub list fixed it, thanks for confirming. Closing, since the conversion to rsshub:// happens because the instance was registered there.