-
-
Notifications
You must be signed in to change notification settings - Fork 64
Messages fail to send to facebook after prolonged bridge uptime #26
Comments
Whoops, looks like this actually uses a different Facebook library - fbchat. The only trace I found there was fbchat-dev/fbchat#175. |
I have the exact same problem, as well. That issue you linked to mentions that it could be caused by not sending any message at all for 3 days. Maybe an option to regularly re-login to FB? |
I've had the same happen to me today. I've started (well, continued / bumped) a chat from Facebook, expecting a portal room to be created for it on the Matrix side. This happened:
Previously (before doing anything active), only this kind of messages were logged:
I worked around it by restarting the bridge. It caught up and appears to continue to work okay. Perhaps the bridge can detect this problem and schedule its own "clean reconnection" or should we take this over to the fbchat side and have it handled there? |
Please re-open this. It is not solved with 547f00c on Jun 10,2019. All that did was bump a library version, however the issue persists today . |
This specific error doesn't even exist anymore and the new version of the error ( (also, bumping a library version is often enough to fix bugs) |
After a prolonged amount of uptime (few days), I get this error when trying to send messages:
This reminds me of Schmavery/facebook-chat-api#555 which is also experienced by matrix-puppet-facebook. The only solution they found was to create a supervisor script that restarts the bridge every ~8 hours.
The text was updated successfully, but these errors were encountered: