Event JSON
{
"id": "208426b1528437795a06b4bd9757733d386865fb969b8b8a52c0ac6254bfb003",
"pubkey": "c12e2f8b222a7d23ef2b80d7ea4f5ae79a07b47b2a067a8dddc6a8f10dc26622",
"created_at": 1773601258,
"kind": 1,
"tags": [
[
"proxy",
"https://metalhead.club/@holger/116234732082184278",
"web"
],
[
"t",
"letsencrypt"
],
[
"t",
"jabber"
],
[
"t",
"debian"
],
[
"t",
"xmpp"
],
[
"t",
"ejabberd"
],
[
"proxy",
"https://metalhead.club/users/holger/statuses/116234732082184278",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://metalhead.club/users/holger/statuses/116234732082184278",
"pink.momostr"
],
[
"-"
]
],
"content": "In case you're using the official ejabberd packages on Debian stable: They're affected by a recent CA policy change (e.g., Let's Encrypt), causing ejabberd to reject newly issued certificates and thereby breaking federation with some remote servers. Deploy this update to fix the issue:\n\nhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128568#23\n\nYou may also want to consider enabling mod_s2s_dialback to deal with remote servers that haven't been updated yet.\n\n#ejabberd #XMPP #Jabber #Debian #LetsEncrypt",
"sig": "57e80721a319dba1bb7bfc20fbc9f8ec2e17ffeeea8697b5d682209849026deb91b436af1179faf6ec8734a6f1fc863bb282dc139ee80c2a20b868412d5a8f04"
}