Skip to content
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

Unable to receive alerts on Telegram bot with Updated version 1.27.0 where it is working fine with 1.26.0 #432

Closed
deepuad opened this issue Dec 14, 2020 · 3 comments
Labels
bug Something isn't working next release Implemented but will be released with the next release

Comments

@deepuad
Copy link

deepuad commented Dec 14, 2020

Describe the bug
reportTelegram alerts are not working with an updated version: 1.27.0

Provide an example
-file: reportTelegram
channels:
- hijack
- newprefix
- visibility
- path
- misconfiguration
- rpki
params:
showPaths: 5 # Amount of AS_PATHs to report in the alert
botUrl: https://api.telegram.org/botXXXXXXX:AAE4pj84CHZ67Dc2nFSVzkphx-A4B3FdWoQ/sendMessage
chatIds:
default: -XXXXXXXXXXX

Are you using the binary or the source code?
Using Binary

Your information
Dileep ASN: 24309

@deepuad deepuad added the bug Something isn't working label Dec 14, 2020
@massimocandela
Copy link
Member

Hi @deepuad,

Version 1.27.0 sets two default groups default and noc during auto configuration.
If you started the auto-configuration with 1.27.0 but used an old config.yml, it could be you don't have the right user group set. If that is the case, try to add a line noc: -XXXXX in your reportTelefgram configuration

@massimocandela
Copy link
Member

I added a fix that allows reportTelegram to use the default user group if the user group specified in prefixes.yml is not available. It is currently in dev. In the meanwhile set the proper user group as in my previous comment.
Thanks for reporting.

@deepuad
Copy link
Author

deepuad commented Dec 15, 2020

Resolved.

Thankyou Sir.

@massimocandela massimocandela added the next release Implemented but will be released with the next release label Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working next release Implemented but will be released with the next release
Projects
None yet
Development

No branches or pull requests

2 participants