What version are you running? Latest version works fine, but deb.slidge.im lags behind (admin is AWOL). You can grab a fresher deb as artifacts of these jobs: https://builds.sr.ht/~nicoco/slidge-debian/

Let me know if that was the issue.

I am closing this as this was probably caused by an outdated slidge-whatsapp.

Sorry for the delay.

I installed debian package build 0.0.0-dev+20240902-git32276f943f

And still have same issue.

sep 03 00:07:32 darkstone systemd[1]: Started slidge@whatsapp.service - Slidge XMPP whatsapp bridge.
sep 03 00:07:33 darkstone slidge[515195]: <frozen runpy>:128:RuntimeWarning:'slidge.__main__' found in sys.modules after import of package 'slidge', but prior to execution of 'slidge.__main__'; this may result in unpredictable behaviour
sep 03 00:07:33 darkstone slidge[515195]: INFO:slidge.util.db:Using existing slidge DB: /var/lib/slidge/whatsapp.jesuislibre.net/slidge.db
sep 03 00:07:33 darkstone slidge[515195]: INFO:slidge.util.db:Registered users in the DB: ['xxxxxxx@jesuislibre.net']
sep 03 00:07:33 darkstone slidge[515195]: INFO:root:Starting slidge version NO_VERSION
sep 03 00:07:34 darkstone slidge[515195]: INFO:root:Starting legacy module: 'slidge.plugins.whatsapp' version NO_VERSION
sep 03 00:07:34 darkstone slidge[515195]: WARNING:slidge.core.gateway.base:IQ privileges not granted for pubsub#owner namespace, we cannot listen to the MDS events of xxxxxxx@jesuislibre.net
sep 03 00:07:35 darkstone slidge[515195]: INFO:slidge.core.gateway.base:Slidge has successfully started
sep 03 00:07:40 darkstone slidge[515195]: ERROR:slidge.plugins.whatsapp.gateway:Client outdated (405) connect failure (client version: 2.2412.50)
sep 03 00:07:40 darkstone slidge[515195]: ERROR:slidge.plugins.whatsapp.gateway:Error reading from websocket: websocket: close 1006 (abnormal closure): unexpected EOF

Hum, Maybe I fixed it by fixing the "IQ privileges not granted for pubsub#owner namespace" in the Prosody config file. I was missing one line that was maybe a new requirement compared to the moment I did the service setup.

Sorry for the delay.

C'EST UN SCANDALE !

fixed it by fixing the "IQ privileges

That sounds very unlikely. Most likely the log you sent was still with the previous version for some reason. Debian packages show "NO_VERSION" on startup which sucks… Anyway I'm glad it now works. :-)