NodeRSSBot Status
@noderss_bot is down for maintenance now. Some user may have see lots of "lookup timeout" message in recent days. It may be the issue of the infrastructure provider(the demo is running on Oracle Cloud) since I have not updated the running docker image for…
Demo is back to normal now. A cron job is there to reduce the pressure of the server. Any subscribes to a feed which error count greater than 1350 (around 14 days because the fetch interval of the demo is 15min) will be deleted.
NodeRSSBot Status
Recently, many of the new subscriptions in the demo came from a git repository called wechat-feeds that is mirrored at gitee. However this repository has been out of sync with the original GitHub repository for many days. All gitee subscriptions from this…
All (1654) wechat-feeds subscribes are removed. https://github.com/hellodword/wechat-feeds/issues/3882
@noderss_bot itself is still working as usual.
@noderss_bot itself is still working as usual.
GitHub
停止服务 · Issue #3882 · hellodword/wechat-feeds
抱歉让各位失望了，本项目经历 278 天，在此要和各位说再见了。 也没有什么别的原因，就是单纯成本激增（原本在我一番操作后每月成本已经为 0），这一点我也曾多次预料到，只是没想到来得这么快。 决定暂时 archive，后面如果能恢复还是会继续服务（对本项目来说很渺茫）。 #3824 #2471
A downtime occur from 2021-07-28T17:56 to 2021-07-28 18:16:08, everything should return to normal now.
NodeRSSBot Status
@noderss_bot will be down for maintenance now. Will recover soon
Service are being gradually restored
The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the bot restores to normal. The detailed reasons are still under investigation.
NodeRSSBot Status
The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the…
Recoved after switching the pooling config to session mode in supabase dashboard.
NodeRSSBot Status
The demo uses Supabase. Since Supabase has closed IPv4 connections, the demo has switched to an IPv6 network and testing shows that it can connect normally. However, recently there have been frequent errors of "relation 'xxx' not found," but restarting the…
Supabase charge for Egress bandwith. Recently Demo comsure over 8G per month which exceeded their free plan. So I just increase the fetch gap for the demo. I may consider some alternatives for supbase when I have some free time from my job. The database is a PostgreSQL which a pg_cron extension to fixes some dead feed. It is around 50MB but read bandwidth is around 8G per month. Any suggestion?
The bot demo will be temporarily suspended for operating system and VPS maintenance. It will be restored as soon as possible.