[Support] BoKKeR - RSSTT - RSS to Telegram

[BoKKeR]

 

Overview: Support for Docker image RSSTT in the bokker/rss.to.telegram repo.

Application: RSS-To-Telegram - http://deluge-torrent.org/

Docker Hub: https://hub.docker.com/r/bokker/rss.to.telegram

GitHub: https://github.com/BoKKeR/RSS-to-Telegram-Bot

 

PS: Icon was made in PS under 10 minutes

 

Edited August 23, 2020 by BoKKeR

[m0ngr31]

I just discovered this yesterday, and it does everything I need. Except one thing. Is there a reason it only grabs the most recent item in the list?

 

For example, I'm grabbing an RSS feed for a subreddit that has a sticky message. So I never get any notifications for it. Can you bump it to like 20 or something?

[BoKKeR]

Hey! sure I will look what I can do about it!

[BoKKeR]

if you preset new like https://www.reddit.com/r/funny/new/.rss it should give you the newest submissions without the stickies. By default it uses top afaik.  Does this work for you? @m0ngr31

[m0ngr31]

That did work thanks!

[mugennas]

somehow the RSS I added get cleared when the container is restarted, does anyone know how to get them to be persistent?

[BoKKeR]

I can look into this, can you share your docker run command that you get after adding the container?

[mugennas]

29 minutes ago, BoKKeR said:

I can look into this, can you share your docker run command that you get after adding the container?

it's installed straight from CA

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='RSSTT---RSS-To-Telegram' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TOKEN'='my_token' -e 'CHATID'='my_bot' -e 'DELAY'='600' --net=container:OpenVPN-Client 'bokker/rss.to.telegram:latest'

I removed the token and id. I also passed this through a OpenVPN container so network is set to none if that matters.

[BoKKeR]

can you try adding a mounted config folder and reproduce the problem? 

 

-v /path/to/host/config:/config 

 

[mugennas]

I added a path from /config to /mnt/user/appdata/rsstt, and that worked! Thanks for the help. Also I think you should update the CA app with default path for this.

[BoKKeR]

thanks I will do that, if you have a chance can you star the docker hub repo.

[Arndroid]

Thank you so much for taking the time to create this!

[BoKKeR]

thanks for commenting!

[Joeri1594]

This is awesome, thankyou

[Nicooo76]

Hello all,
I installed the dokker and it seems to work.
My question is: How do I get the bot to post to a channel now?
The bot itself posts, but it should post in a channel.
Thanks for your assistance and very cool project! 👍

[BoKKeR]

Add the bot to your chat, get the chatID and pass it to the container! @Nicooo76

Edited February 4, 2022 by BoKKeR

[Nicooo76]

So you mean the chatID of the bot itself or the one of the group I added the bot to?
When I run /help in the group the following message appears in the log.

 

 

telegram.error.BadRequest: Can't parse entities: character '-' is reserved and must be escaped with the preceding '\'
2022-02-04 15:55:49,270 - telegram.ext.dispatcher - ERROR - No error handlers are registered, logging exception.
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/telegram/ext/dispatcher.py", line 432, in process_update
handler.handle_update(update, self, check, context)
File "/usr/local/lib/python3.7/site-packages/telegram/ext/handler.py", line 156, in handle_update
return self.callback(update, context)
File "telegramRSSbot.py", line 126, in cmd_help
"\n\nIf you like the project, star it on [DockerHub](https://hub.docker.com/r/bokker/rss.to.telegram)")
File "/usr/local/lib/python3.7/site-packages/telegram/message.py", line 655, in reply_markdown_v2
return self.bot.send_message(self.chat_id, *args, **kwargs)
File "<decorator-gen-2>", line 2, in send_message
File "/usr/local/lib/python3.7/site-packages/telegram/bot.py", line 135, in decorator
result = func(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/telegram/bot.py", line 466, in send_message
api_kwargs=api_kwargs,
File "/usr/local/lib/python3.7/site-packages/telegram/bot.py", line 281, in _message
result = self._post(endpoint, data, timeout=timeout, api_kwargs=api_kwargs)
File "/usr/local/lib/python3.7/site-packages/telegram/bot.py", line 245, in _post
return self.request.post(f'{self.base_url}/{endpoint}', data=data, timeout=timeout)
File "/usr/local/lib/python3.7/site-packages/telegram/utils/request.py", line 354, in post
**urlopen_kwargs,
File "/usr/local/lib/python3.7/site-packages/telegram/utils/request.py", line 272, in _request_wrapper
raise BadRequest(message)
telegram.error.BadRequest: Can't parse entities: character '-' is reserved and must be escaped with the preceding '\'

 

The bot successfully fetches the feed but posts it only in its own chat but not in the group.

But /list and /add works in the group...

Something I have not quite understood 🤔

[BoKKeR]

That must be some unresolved bug that got introduced by a package update. You need to get the chat-id of the chat where you want the bot to post to. Then you set that as an environmental variable in the container @Nicooo76

Edited February 5, 2022 by BoKKeR

[Blacksus]

Used this for quite a while now, but believe a recent update broke it. Docker dies shortly after start:

 

          

RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at new NodeError (node:internal/errors:363:5)
    at validatePort (node:internal/validators:208:11)
    at lookupAndConnect (node:net:988:5)
    at Socket.connect (node:net:964:5)
    at connect (node:net:193:17)
    at /app/node_modules/ioredis/built/connectors/StandaloneConnector.js:54:66
    at processTicksAndRejections (node:internal/process/task_queues:78:11) {
  code: 'ERR_SOCKET_BAD_PORT'
}
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "rss_bot_database.db" at "file:./../config/rss_bot_database.db"

4 migrations found in prisma/migrations


No pending migrations to apply.

 

This docker has served me well, would appreciate any help on this

Edited June 9 by Blacksus

[BoKKeR]

Sorry I forgot to update the template, the container now uses a redis queue and it is much more reliable. With support for multiple chats . Check the docker page 

[BoKKeR]

On 6/9/2023 at 2:49 AM, Blacksus said:

Used this for quite a while now, but believe a recent update broke it. Docker dies shortly after start:

 

          

RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at new NodeError (node:internal/errors:363:5)
    at validatePort (node:internal/validators:208:11)
    at lookupAndConnect (node:net:988:5)
    at Socket.connect (node:net:964:5)
    at connect (node:net:193:17)
    at /app/node_modules/ioredis/built/connectors/StandaloneConnector.js:54:66
    at processTicksAndRejections (node:internal/process/task_queues:78:11) {
  code: 'ERR_SOCKET_BAD_PORT'
}
Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "rss_bot_database.db" at "file:./../config/rss_bot_database.db"

4 migrations found in prisma/migrations


No pending migrations to apply.

 

This docker has served me well, would appreciate any help on this

I updated the template with the redis env variables

Edited June 10 by BoKKeR