-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telegram failed with: Unable to find channel. The channel is non-existing or non-public. #4272
Comments
I can reproduce this issue locally but not on the official instance or when using the docker image. How are you running rss-bridge? I recommend switching a docker based setup if possible. See the link below for how. |
I am currently running rss-bridge using the rssbridge/rss-bridge:latest docker image. I am able to reproduce with the official instance here as well as local: |
Looks like the channel can't be viewed or previewed outside of telegram's app. |
I had the same thought, but I tried five different public channels, and they all produced the same result. Have you been able to get it working with any channel? I use RSS-Bridge with multiple channels, and they all stopped working around the same time, so I suspect something may have changed on Telegram’s side that is causing this issue. |
Yes. with |
Recently been receiving the below error with all public telegram channels.
Maintainer: @VerifiedJoseph
The text was updated successfully, but these errors were encountered: