diff --git a/README.html b/README.html index 6e3c304..e1ae4dd 100644 --- a/README.html +++ b/README.html @@ -241,10 +241,10 @@ It features background tasks and interactive chats, and can serve as an interfac source ./bashbot.sh source # send me a test message -send_message "$(cat "$BOTADMIN")" "test" +send_message "$(getConfigKey "botadmin")" "test" # send me output of a system command -send_message "$(<"$BOTADMIN")" "$(df -h)" +send_message "$(getConfigKey "botadmin")" "$(df -h)"
For more information see Expert Use
This may happen if to many wrong requests are sent to api.telegram.org, e.g. using a wrong token or not existing API calls. If you have a fixed IP you can ask telegram service to unblock your ip or change your IP. If you are running a tor proxy on your server you may uncomment the BASHBOT_CURL_ARGS
line in 'mycommands.sh'
Since Version 0.98 bashbot can recover from broken connection to Telegram (aka blocked). therefore you must provide the function bashbotBlockRecover()
in mycommands.sh
. There you can check e.g. if your connection is working, change IP or simply wait some time.
If everything seems OK return 0 for retry or any non 0 value for abort.
+# called when bashbot sedn command failed because we can not connect to telegram
+# return 0 to retry, return non 0 to give up
+bashbotBlockRecover() {
+ # place your commands to unblock here, e.g. change IP or simply wait
+ sleep 60 && return 0 # may be temporary
+ return 1
+ }
+
@Gnadelwartz
If you feel that there's something missing or if you found a bug, feel free to submit a pull request!
-