Closed richard1017msig closed 1 year ago
2 first message received at 17h14 are exact same as above. The third one is a bit different. The fourth one is the same as 2 first.
Here is the 3rd one:
Surfaced: Telegram returned an RPC error: Timedout (-503) (Timedout), caused by phar:///var/www/html/lala/KevinBot/madeline-01b97c2aabc1e151c1232c2d2f72774db19ced6f-81.phar/vendor/danog/madelineproto/src/MTProtoSession/ResponseHandler.php:397<br>
Revision: 01b97c2aabc1e151c1232c2d2f72774db19ced6f-81<br>
<br>
TL trace:<br>
['updates.getChannelDifference']<br><br>
WrappedFuture.php(59): danog\MadelineProto\MTProtoSession\{closure}()<br><br>
CallHandler.php(106): await()<br><br>
CallHandler.php(47): methodCallAsyncRead()<br><br>
UpdateLoop.php(92): methodCallAsyncRead()<br><br>
Loop.php(135): loop()<br><br>
Loop.php(162): loopInternal()<br><br>
AbstractDriver.php(577): danog\Loop\{closure}()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(596): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(542): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(542): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(542): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(596): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(542): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(542): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(542): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(406): resume()<br><br>
AbstractDriver.php(596): invokeMicrotasks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(479): start()<br><br>
AbstractDriver.php(533): invokeCallbacks()<br><br>
Revolt\EventLoop\Internal\{closure}()<br><br>
AbstractDriver.php(86): resume()<br><br>
DriverSuspension.php(97): Revolt\EventLoop\Internal\{closure}()<br><br>
Future.php(251): suspend()<br><br>
Loop.php(129): await()<br><br>
AbstractAPI.php(92): loop()<br><br>
AbstractAPI.php(73): startAndLoopLogic()<br><br>
EventHandler.php(48): startAndLoopInternal()<br><br>
2-kevin.php(659): startAndLoop()<br>
MadelineProto.log for this one only contain "MTProto, KevinCryptoMaker: Reported!"
Note: after those 4 messages at same hh:mm Madeline continues to work just fine without any action from me.
If this can help...
Im using a completely different tool but getting the same issue the last two or three days. I think telegram might be messing with their api either changing it for some reason or actively blocking third party download tools
What do you mean by "completely different tool" ?
Fixed in the latest beta96.
since 1 week or so I got that in my Telegram Saved message.
For today I get it 4 times at 17h14. My MadelineProto is looking at specific from_id that match some criterias to insert infos in a MariaDB.
Full message in Saved massage is:
Find MadelineProto.log as attachement MadelineProto.log
Thanks