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

At 5 o'clock am telegram is terminating #63

Closed
Marty56 opened this issue Jul 26, 2018 · 1 comment
Closed

At 5 o'clock am telegram is terminating #63

Marty56 opened this issue Jul 26, 2018 · 1 comment

Comments

@Marty56
Copy link

Marty56 commented Jul 26, 2018

I have to iobroker servers set up. On each of those servers I am receiving the following error message
`

host.raspberrypi | 2018-07-26 05:04:00.611 | info | Restart adapter system.adapter.telegram.0 because enabled
host.raspberrypi | 2018-07-26 05:04:00.610 | error | instance system.adapter.telegram.0 terminated with code 156 ()
telegram.0 | 2018-07-26 04:36:04.092 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway
telegram.0 | 2018-07-26 04:36:00.840 | error | polling_error:ETELEGRAM, ETELEGRAM: 500 Internal server error: restart
telegram.0 | 2018-07-26 04:21:44.415 | error | polling_error:ETELEGRAM, ETELEGRAM: 502 Bad Gateway

`
This occuring on both machine every day at the same time.

@Apollon77
Copy link
Member

The bad gateway error (different time!!) means that the telegram servers are offline. Happens from time to time.

Restart at 5am is default config. We had people that had problems with their daily internet reconnection. Can be changed in ioBroker Admin when you do not need the restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants