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
OS: Fedora Linux Server, Node: v18.17.1, Docker: 24.0.2
Additional info
Error message: getaddrinfo EAI_AGAIN warp-socks: target website might be blocking our access, you can [host your own RSSHub instance](https://docs.rsshub.app/install/) for a better usability.
This is not a duplicated issue
I have searched existing issues to ensure this bug has not already been reported
The text was updated successfully, but these errors were encountered:
/telegram/channel/:username/:routeParams?: Route not found
To maintainers: if you are not willing to be disturbed, list your username in scripts/workflow/test-issue/call-maintainer.js. In this way, your username will be wrapped in an inline code block when tagged so you will not be notified.
如果所有路由都无法匹配,issue 将会被自动关闭。如果 issue 和路由无关,请使用 NOROUTE 关键词,或者留下评论。我们会重新审核。
If all routes can not be found, the issue will be closed automatically. Please use NOROUTE for a route-irrelevant issue or leave a comment if it is a mistake.
Routes
Full routes
Related documentation
https://docs.rsshub.app/routes/social-media#telegram-channel
What is expected?
it should show the json file for the telegram channel
What is actually happening?
it throws an error.
weirdly sometimes it works, but mostly doesn't
also duplicates #13155 as this issue was closed instantly cause it couldnt find a maintainer, which it should:
https://github.com/DIYgod/RSSHub/blob/master/lib/v2/telegram/maintainer.js
Deployment information
Self-hosted
Deployment information (for self-hosted)
OS: Fedora Linux Server, Node: v18.17.1, Docker: 24.0.2
Additional info
Error message: getaddrinfo EAI_AGAIN warp-socks: target website might be blocking our access, you can [host your own RSSHub instance](https://docs.rsshub.app/install/) for a better usability.
This is not a duplicated issue
The text was updated successfully, but these errors were encountered: