Well, this might come in handy if you are addicted to the damn thing called Emacs.
#linuxadmin #tool #emacs #gnu #opensource
https://emacsfr.org/2025/02/21/mastering-emacs-essential-tips-and-tricks-for-efficiency/
Well, this might come in handy if you are addicted to the damn thing called Emacs.
#linuxadmin #tool #emacs #gnu #opensource
https://emacsfr.org/2025/02/21/mastering-emacs-essential-tips-and-tricks-for-efficiency/
🚀 Sync-in 1.10 now supports Collabora Online - @CollaboraOffice
👉 Learn more:
https://sync-in.com/news/sync-in-collabora
👉 Try our demo to compare:
https://sync-in.com/docs/demo/
#documentmanagement #release #collabora #opensource #foss #selfhosting #selfhosted #security #linux #privacy #datasovereignty #logicielslibres #libre #collaboration #authentification #cybersecurity #freesoftware #privacytools #cloud #productivity #fediverse #linuxadmin #infosec #sysadmin #opensourcesoftware #selfhst #files #sync_in
I have a very weird issue with my #tailscale + #mumble server setup:
I have a murmur (mumble) server that binds to the tailscale interface on my server.
I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.
Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".
The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.
How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.
#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin
CC @tailscale
Please boost 
I have a very weird issue with my #tailscale + #mumble server setup:
I have a murmur (mumble) server that binds to the tailscale interface on my server.
I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.
Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".
The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.
How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.
#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin
CC @tailscale
Please boost
