XMPP Service Operators - 2026-02-06

A problem has been detected on the hypervisor of which this server resides on. Some downtime is expected today to migrate to different healthy hypervisor. No action is required.

tom: which provider if I may ask?

It is a specific cluster node not a provider-wide issue.

asking because I had issues with Vultr recently.

it may be possible to migrate without any downtime. It is just procedure to send a message expecting downtime with a hypervisor indicates a unhealthy bit.

> asking because I had issues with Vultr recently. Vultr is one of the shadiest summiest VPS providers I have ever had to deal with, I would highly suggest NOT using them for anything. ↺

> Vultr is one of the shadiest summiest VPS providers I have ever had to deal with, I would highly suggest NOT using them for anything. didnt they recently decide to start selling data about vm activity? lol ↺

Vultr is one of the only vps providers that would offer a vps in hawaii, but Ive gone with Hetsner instead, a lot of people say negative things but ive yet to run into issues

I'm unfamilar with that but that only time I ever had to revoke a TLS key under the 'key compromised' reason was when I used Vultr because they tried to hold a VPS for ransom until I suggested what they were doing was illegal.

They are also one of the only hosting providers owned by "domains by proxy" which is a huge red flag.

jokerte@conversations.im <--- Morph

Might need to set the channel to moderated this is getting annoying

Published a new blog post about the upcoming Let's Encrypt changes: https://blog.prosody.im/2026-letsencrypt-changes/

No action required for Prosody operators, ejabberd operators need to upgrade to 25.08 or later

ij, I think you are the admin of hookipa.net/xmpp.social? These domains are affected.

uhm? need to have look at it…

Some other domains affected include 5222.de and chatterboxtown.us

Jabbim will be affected too, maybe they finally update from ejabberd 17.11 and Linux 4.4.19 now

Yes, around the same time as jabber.ru

MattJ: Preparing to unpack ...ejabberd-mod-cron_0.2025.01.11~dfsg0-2+deb13u1_amd64.deb … - seems an easy fix… :)

Good :)

Let me know if you want me to test it again

yeah, would be nice to have confirmation :)

Is it deployed already? I still see issues

yes, installed & upgraded

Looks like still ejabberd 24.12?

25.08 or later is needed

manually restarting it… I assumed needrestart would have done it…

MattJ: ah, weird… all modules have been upgraded, but the server package itself is still 24.12… for whatever reason…

morph jid: jokerte@conversations.im