#YunoHost devs are testing#Prosody as #xmpp#jabber replacement for metronome to get better integration with the system and better compliance with jabber standards. Also new default features as A/V calls.
#prosody trunk nightly build 1887 now supports systemd notifications via a pure #Lua implementation (it does not use libsystemd). Future builds, starting with 1888 will have this enabled when running under systemd. Could help with race conditions on startup of external components and other services, delaying them until Prosody is ready to accept connections.
Jitsi-Meet avec authentification par JWT : le chaînon manquant
J’essaye actuellement de faire fonctionner Jitsi-Meet avec une authentification par Json Web Token sur une Debian 12 et je suis tombé sur un truc que je n’ai vu documenté nul part.
Après l’installation du paquet jitsi-meet et le paquet jitsi-meet-tokens, ça ne fonctionnait pas. Jitsi ne m’envoyait pas péter mais les conférences ne fonctionnaient pas pour autant.
Les logs de prosody m’ont fourni la réponse :
Error initializing module 'auth_token' on 'jitsi.fiat-tux.fr': /usr/lib/prosody/util/startup.lua:203: module 'inspect' not found:
J’avais pourtant le paquet lua-inspect installé et je trouvais bien des fichiers inspect.lua en faisant find / -name inspect.lua. Mais aucun en lua 5.4, qui semblait être la version utilisée par prosody (no file '/usr/local/share/lua/5.4/inspect.lua' dans les logs).
@sven222@thomas#Slidge has a #Matrix puppeteering bridge. Of course it's better to have full protocol implementation, but still it's a solution that can be used with #Prosody.
Anyone know how to migrate to a different domain with Prosody? I would like to migrate without loosing my history or files, but its looking like that might not be possible.
@dwarf#Prosody works pretty well so far, but I've been told by Some Guy on #IRC that its more work to get file uploads and voice/video calls working compared to #ejabberd.
I haven't tried out ejabberd to confirm this, though.
@kubikpixel
Es hat extra Funktionen für Familie und kleine Gruppen von bekannten mitgebracht und für #prosody entwickelt, wie die super einfachen Einladungen, sodass man keine aufwendigen Anleitungen für nicht_nerds braucht. Es funktioniert praktisch, und sieht aus wie #Whatsapp vor einigen Jahren war.
Es ist nicht garantiert sicherer als #Signal, aber es ist #dezentral und föderiert, und die Daten der Kontakte auf dem eigenen Server bleiben bei dir. @mollyim@signalapp@snikket_im@blabber
For business reasons, I think I am stuck with figuring out a solution for traditional #email.
I share your sentiments about having and using viable replacements.
#xmpp seems like it has so much promise, but there's doesn't seem to be much movement toward it. We self-host a #prosody xmpp server, so have some experience with it, but not a lot.
In case anyone is wondering about how to "update" a valid certificate from #letsencrypt that for some reason #prosody states is already expired, just run:
Hey #Nixos people, I'm trying to run #prosody but it's having an issue with the TLS certificates.
I see that the key.pem file is owned by acme nginx, and it's set to group-readable. (Yes, I'm running nginx as well on this server and would like to keep it.)
Obviously, Prosody can't read that file... What's the "right" way to do that? Set Prosody's group to nginx? Or set up an extra group? Or...?
Okay so swtiching to english to reach more people.
I host a #Prosody server for my #XMPP use. Today my TLS certificates did renew.
On Conversations, I had to manually delete the certificate to start using the new one (maybe this is normal ? My girlfriend, who also use the app, didn't had to)
My server-to-server connection is not working anymore because of the TLS certificate being "expired".
I'm pretty sure this should be automatically done.
Yunohost Frage: Wenn ich Jitsi Meet installieren möchte, wird ja #metronome (#xmpp) deinstalliert. Mit Jitsi wird ja #prosody installiert, kann ich das dann auch als "normalen" xmpp server verwenden?
After several month of hard work we are pleased to announce that we just released Monal 6.0! 🥳
This version comes with new artwork by Ann-Sophie Zwahlen, support for Audio-Calls funded by the EU’s #NGIAssure via the NLnet Foundation and many, many other improvements and bugfixes. The full list of changes can be seen in the following posts.
Hey #xmpp folks, is Prosody still the easiest way to self-host a server?
Please, please, please say it isn't
EDIT: use case is I have an Ubuntu box from Hetzner hosting some websites and (soon) a nextcloud, this is what I had set up on my last dedicated server (except owncloud back then) and the new box has Plesk on it and after just a couple of weeks of pressing buttons in Plesk and having it Do It All For Me I've been completely spoiled
EDIT 2: the root of the issue is that Plesk hides your .cert and .key files. Scrambles their names, removes their extensions and dumps them all under /opt/psa/certificates/ not even in different folders for different domains, you'd expect mydomain.com.cert but instead you get scfLios3a, all mixed up in a bucket with the eggs on top, good luck telling Prosody where to look for those buggers
Alright anyone struggling to make #plesk and #prosody work together and making the 🙀 face when you see the Horrible Manglings that Plesk does to your .cert and .key files, don't worry - they're also in /usr/local/psa/var/modules/letsencrypt/etc/live/
(NOT THAT PLESK WILL TELL YOU THAT OF COURSE)
So you've just gotta do a prosodyctl --root cert import /usr/local/psa/var/modules/letsencrypt/etc/live/ and it'll find them and then All Is Well. Well you'll probably wanna set that up in cron to run just after whenever random time Plesk decides to renew your certs, because I haven't yet found a Plesk-Approved(TM) way to add a hook into certbot.
Pinging @mattj@zash too so they can add that to the docs for the benefit of people who want to run both Plesk and Prosody, so maybe three people in the next decade