XMPP Service Operators - 2024-12-06

  1. Wojtek

    @Martin I tried responding to you but I was getting s2s error on my end... something really weird is going on :)

  2. Wojtek

    as for issue tracking:

  3. Wojtek

    https://upload.tigase.tygrys.run:443/upload/8d2ff567-9d9a-4a25-8af0-2f17af3d2635/2024-12-06_11-23.jpg

  4. Martin

    Wojtek: Thanks.

  5. Martin

    > @Martin I tried responding to you but I was getting s2s error on my end... Maybe tigase and prosody trunk have some incompatibility.

  6. Wojtek

    Looking into it

  7. roughnecks

    edhelas: I removed the blocking rules in iptables and, after a bit of debug logs going crazy, it seems back to normal now.

  8. edhelas

    If you can give me a few full stanzas that would help me know if it was caused by the MAM loop I fixed

  9. roughnecks

    I can't, sorry. Maybe next week

  10. Menel

    I can join both tigase channels with trunk. But had to reconnect some times after it immediately threw me out. And if I change my nick in the "muc" version then it can't reconnect ✎

  11. Menel

    I can join both tigase channels with prosody trunk. But had to reconnect some times after it immediately threw me out. And if I change my nick in the "muc" version then it can't reconnect ✏

  12. Menel

    OK both kick me on changing nick

  13. roughnecks

    and, btw, do I need to enable this? https://prosody.im/doc/modules/mod_stanza_debug Is it still relevant now that the issue seems to be fixed?

  14. MattJ

    No, it forces Prosody to log stuff that we avoid logging by default (full stanza contents)

  15. MattJ

    So as the name implies, unless you need to debug something, it's best to disable it

  16. roughnecks

    edhelas asked for full stanzas. I haven't enabled anything yet