-
Notifications
You must be signed in to change notification settings - Fork 148
Runing bot #26
Comments
when i'm trying set admin i see that error : |
Did you manage to resolve this issue? |
Had the same problem, solution is to use the ID Number for TELEGRAM_ADMIN. Its just a numeric value, use userinfobot to get the id |
One of the possible reasons may be ISP blocks traffic to telegram. You may use the following command to check if your system have trouble with connectivity to the telegram api:
|
This is for CentOS7 system instruction:
This is ready Dockerfile, which i'm edited: In file alpineentrypoint.sh i write: Then we run image: Done. But, the next hope, run 'main' with key: ./main --alertmanager.url=localhost:9093 --listen.addr=localhost:10443 --store=bolt BOLT_PATH:/tmp/bot.db --telegram.admin=<id number, not text> --telegram.token= --template.paths=/root/alertmanager-bot/default.tmpl Stay one problem: Please, help. What binary-script want? |
@ihtiking you should pass BOLT_PATH in another way i think, like option. |
I'm having the following error using K8s deployment: Seems like a |
Oh, just found the solution at kubernetes/kubernetes#23404 (comment) ! |
Hello, when i'm trying to start bot with docker-compose file i see :
level=error ts=2018-08-20T15:21:44.274865Z caller=main.go:134 msg="failed to create bot" err="http.Post failed: Post https://api.telegram.org/bot678959762:AAHhfz2K-TSh_Ptij_k21iNFy4vTXQlDoIM/getMe: EOF"
compose file:
alertmanager-bot:
image: metalmatze/alertmanager-bot:0.2
environment:
ALERTMANAGER_URL: alertmanager:9093
BOLT_PATH: /data/bot.db
STORE: bolt
LISTEN_ADDR: 0.0.0.0:8080
TELEGRAM_ADMIN: '1234567'
TELEGRAM_TOKEN: "my token by botfather"
volumes:
- ./srv/monitoring/alertmanager-bot:/data
The text was updated successfully, but these errors were encountered: