Suddenly telegram receiver node cannot connect

[brunialti]

I had to restore my flows from a previous backup
I have a bot named casa_brunialti
The server config seems to be ok, but the receiver node cannot connect (node status disconnected).
I'm sure the token is ok (i copied from botfather).
The bot name (casa_brunialti or casa_brunialti_bot) does not make any difference
Am I getting too old ?

Node-RED version: v4.0.0
node-red-contrib-telegrambot version: 16.10.0
update mode:polling
polling interval: 300
ip address family: any
all other fields are not filled (except of course bot name e token)

[windkh]

@brunialti
can you provide some more details please?
The console output?
Can you send me your flow?

[brunialti]

Da: Karl-Heinz Wind ***@***.***> Inviato: venerdì 27 settembre 2024 11:39 A: windkh/node-red-contrib-telegrambot ***@***.***> Cc: roberto brunialti ***@***.***>; Mention ***@***.***> Oggetto: Re: [windkh/node-red-contrib-telegrambot] Suddenly telegram receiver node cannot connect (Issue #392) @brunialti <https://github.com/brunialti> can you provide some more details please? The console output? Can you send me your flow? — Reply to this email directly, view it on GitHub <#392 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMAA3GKSRWLNALLUHLZPG3ZYURSNAVCNFSM6AAAAABO5XNLMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZYHA3TAMRYGE> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AAMAA3EMP545BWH6Z46NDQLZYURSNA5CNFSM6AAAAABO5XNLMCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUNZKXAS.gif> Message ID: ***@***.*** ***@***.***> >

[brunialti]

f.json

[windkh]

@brunialti why did you check the checkbox "Test Environment"?

[brunialti]

That was a random temptative, I unchecked the box and nothing changed

[windkh]

Did you try another bot token to check if it works at all?

[windkh]

Can you update the node and send me the console output of node red?

[brunialti]

I had to revoke the token in bot-father. With the new token the node worked as usual.
I checked the old token, It was correct. Nevermind. Now it is working
Thank for the support