More news on the previously announced bridge for support MUC: we got another bridge set up. This time around, IRC joins the ballet, so matterbridge is now bridging @wpn support MUC for 3 different protocols.. XMPP and MATRIX being the previous other two.
https://health.woodpeckersnest.space/
On this matter I was thinking about making a "tombstone" of the current XMPP MUC, which is called status and move to wpn - In fact that's the name of the MATRIX and IRC rooms. This is not really something I want to do soon, though, because it implies changing several things.
Last, but not least, I have also set up an anonymous VirtualHost in Prosody. You can now login to anon.woodpeckersnest.space with a disposable account (whose data gets deleted from the server as soon as the account is not connected anymore) and participate/discuss in @wpn MUCs - access to external servers is not permitted to anonymous users, for obvious security concerne.
You can follow the steps in this GIF to connect anonymously with Gajim; Dino should also support it but I don't know how it's done.. Finally if you want to join via Android, these are the instructions provided by Daniel Gultsch, from Conversations IM:
you can just add the account something@anon.woodpeckersnest.space with an empty password to #Conversations_im and it will login anonymously.
Anonymous logins don't require registration. When I say 'something@anon...' you can use anything as that username. Doesn't matter (it's only used to get through the client side jid validation check)
TIP: If the server tells you can't join a MUC, make sure you have added a nickname in your profile's details (Android).
It's been a few days now that I'm experiencing downtimes at night, early mornings.
When I wake up, connect to the VPS and attach to tmux, I am welcomed by these messages in console:
Message from syslogd@pandora at Nov 3 05:37:13 ...
kernel:[1586232.350737] Dazed and confused, but trying to continue
Message from syslogd@pandora at Nov 3 05:37:24 ...
kernel:[1586235.049143] Uhhuh. NMI received for unknown reason
30 on CPU 1.
Message from syslogd@pandora at Nov 3 05:37:24 ...
kernel:[1586235.049145] Dazed and confused, but trying to continue
Message from syslogd@pandora at Nov 3 05:37:55 ...
kernel:[1586273.642163] watchdog: BUG: soft lockup - CPU#2 stuck
for 27s! [dockerd:526408]
Message from syslogd@pandora at Nov 3 05:38:00 ...
kernel:[1586278.545172] watchdog: BUG: soft lockup - CPU#1 stuck
for 24s! [systemd-journal:257]
Message from syslogd@pandora at Nov 3 05:38:02 ...
kernel:[1586281.187611] watchdog: BUG: soft lockup - CPU#3 stuck
for 35s! [lua5.4:1702]
There's no need to say that when this happens, the server is completely frozen and doesn't respond to anything.
I already contacted support, but they didn't investigate at all, I believe. They manually restarted my VPS once and did some pings and connection tests (VNC, SSH) afterwards.. "everything is working fine!"
This last Saturday I was up when it happened, so I did a mtr from my PC to the VPS's IP and logged it, then I sent another email with the output to support.. Still waiting for them to reply, I guess tomorrow (Monday).
Friends like lorenzo and shai are having difficulties too, with the same provider, so I'm not imagining things.
Well, that's all I got to say, will keep you posted if any news.
Last evening, at around 22:00 CET, Contabo migrated my VPS from old Hub at Nuremberg to the newly built "Hub Europe".
They rebooted it and everything came back up as usual.. I wasn't at home when it happened, didn't even notice anything until I connected and found no tmux session running. Even my phone which was connected to wireguard, quietly continued working and sending notifications 😎
Meanwhile, my friends and I watched "The Creator" on Disney+
Can't really say I do recommend it, but for some casual evening/entertainment, it wasn't half bad.
gemlog
