search

ventureoo / jabagram

Fully functional bridge between Telegram and XMPP
GNU General Public License v3.0
12 stars 1 forks source link

Jabagram does not bridge after a timeout #3

Open n4ch0m4n opened 3 months ago

n4ch0m4n commented 3 months ago

Jabagram sometimes does not bridge after a timeout

I'm seeing in the logs that after a timeout, jabagram reconnects to xmpp (I see this because I'm an admin of the xmpp server) and apparently they send the xmpp <-> telegram msg according to the jababram log, but in practice it doesn't happen.

This doesn't happen very often and restarting jabagram makes it work again.

Have you had the same issue?

ventureoo commented 3 months ago

Yes, it's a known issue. Unfortunately I don't fully understand the causes yet, maybe it's related to slixmpp or server side which rejects connection due to a lot of messages from the bridge side.

n4ch0m4n commented 3 months ago

I don't think it's because of the amount of requests, I have groups that have very little activity.

ventureoo commented 3 months ago

I don't think it's because of the amount of requests, I have groups that have very little activity.

I mean, Jabagram can "flood" with reconnect requests as in the case of jabagram_bot@jabb.im at night.

n4ch0m4n commented 1 month ago

I just noticed that this keeps happening, but unlike before it now works in some groups and not in others. I restart the service and it works again in all of them.

ventureoo commented 1 month ago

I just noticed that this keeps happening, but unlike before it now works in some groups and not in others. I restart the service and it works again in all of them.

Sorry, but there's no progress so far. I've also noticed that after a while XML streaming from some MUCs starts to just disappear for some unknown reason. I'm not sure if it's really about jabagram or slixmpp library.

n4ch0m4n commented 1 month ago

I just noticed that this keeps happening, but unlike before it now works in some groups and not in others. I restart the service and it works again in all of them.

Sorry, but there's no progress so far. I've also noticed that after a while XML streaming from some MUCs starts to just disappear for some unknown reason. I'm not sure if it's really about jabagram or slixmpp library.

Have you checked XEP-0030 and XEP-0199?

https://xmpp.org/extensions/xep-0199.html https://xmpp.org/extensions/xep-0030.html

There's also discussion about this on https://github.com/louiz/slixmpp.

maybe too sending logouts: https://slixmpp.readthedocs.io/en/latest/getting_started/sendlogout.html

n4ch0m4n commented 1 month ago

I just noticed that this keeps happening, but unlike before it now works in some groups and not in others. I restart the service and it works again in all of them.

Sorry, but there's no progress so far. I've also noticed that after a while XML streaming from some MUCs starts to just disappear for some unknown reason. I'm not sure if it's really about jabagram or slixmpp library.

Have you checked XEP-0030 and XEP-0199?

https://xmpp.org/extensions/xep-0199.html https://xmpp.org/extensions/xep-0030.html

There's also discussion about this on https://github.com/louiz/slixmpp.

maybe too sending logouts: https://slixmpp.readthedocs.io/en/latest/getting_started/sendlogout.html

Could the issue be related to the rate limits of the server where the MUC is hosted?

ventureoo commented 1 month ago

To help this issue I added workaround to auto re-join inside the room (https://github.com/ventureoo/jabagram/commit/1cf734cd864f2bfc4468273696b9e86a7eb44685), since I have suspicions that it was due to accidental kicking the boot from room. Please check to see if it has any effect for you.

n4ch0m4n commented 1 month ago

image this error is ok?

ventureoo commented 4 weeks ago

image this error is ok?

Yes, it's quite normal. You need to copy these lines to our config:

https://github.com/ventureoo/jabagram/blob/master/config.example.ini#L16-L34