XMPP Service Operators - 2025-03-15

anyone kowns if sure.im has mod block strangers enabled?

I have a person complaining that my Biboumi doesn't work and that annoying module is my current guess.

hmm or maybe some other incompatibility? Seems to run Tigrase server?

> xmpp-dns -sft joinjabber.org > failure in xmpp-server lookup: lookup _xmpp-server._tcp.joinjabber.org on 192.168.178.66:53: no such host > failure in xmpps-server lookup: lookup _xmpps-server._tcp.joinjabber.org on 192.168.178.66:53: no such host > Trying fallback ports. > > xmpp-server joinjabber.org 5269 > Priority: 0 Weight: 0 > IP: 2a0c:f040:0:8::3b > Test: [Not OK] > tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2025-03-15T16:38:34+01:00 is after 2025-03-13T11:36:53Z > IP: 77.83.247.19 > Test: [Not OK] > tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2025-03-15T16:38:35+01:00 is after 2025-03-13T11:36:53Z

I was just kicked from joinjabber as well due to a cert expiration issue

Automating certbot is hard. :)

When it's crappy software, yeah.

Actually I never used anything sophisticated. Just put the certbot call in my crontab and had no issues so far. :)

The big issues are wildcard domains personally. I can't use certbot beyond my own personal preference for that very reason.

I personally use uacme, but even that has issues because letsencrypt doesn't like remaining consistent.

Highly recommend setting up scheduled email notifications on your server if you can't automate it.

a calendar reminder also work flawlessly

but as in email reminders, everything depends on procrastination's levels

Considering https://joinjabber.org has a current cert, I'm guessing it didn't get exported to the jabber service correctly and the jabber side is still working off the older cert. I don't think they would have a reason to have completely separate certs for http and xmpp

yes, they were still connected until I rebooted my server a few minutes ago