RBK0228W - Telegram not reachable #657
Closed
PatrickGlatz
started this conversation in
Questions
Replies: 1 comment
-
raspiBackup assumes a working network connection when telegram is used. There exists a plugpoint Maybe it's just sufficient to execute a sleep for some time until all networking services are up and running again. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
i just noticed, that from my 3 raspis i only get two Telegram notifications back. The one which i am missing is with pihole as a DNS server in my network. Somewhen back, it was working but since a while i believe not. I have exactly the same configuration on my rasperry pi's, despite the START and STOP services. With the "networkPi", it is
But in the log, i can find only the following:
I have now cross checked and did the exact same curl call (replaced the token and chatid with the ones of the config of course) and i received immediately my telegram message.
So imho, this could be due to the services (e.g. pihole-FTL) are not completely up and running and so does the network itself (or the router (UniFi DreamMachine Pro) has not reconnected to the DNS service). Do you also think this might be the case and do you have a solution for that? Precheck whether network is available? Or is there another reason?
Thanks for your suggestions.
Patrick
Beta Was this translation helpful? Give feedback.
All reactions