Discussion
Loading...

#Tag

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Sync-in
Sync-in
@sync_in@mastodon.social  路  activity timestamp last week

馃殌 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

Sync-in

Live Demo 路 Sync-in

Want to explore Sync-in without installing anything?
Sync-in

Collabora Online Integration 路 Sync-in

As part of an approach focused on openness and technological neutrality, we wanted to enhance Sync-in with an open office alternative.
  • Copy link
  • Flag this post
  • Block
David Vasandani boosted
musicmatze :rust: :nixos:
musicmatze :rust: :nixos:
@musicmatze@social.linux.pizza  路  activity timestamp 6 months ago

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 boost_ok

  • Copy link
  • Flag this post
  • Block
musicmatze :rust: :nixos:
musicmatze :rust: :nixos:
@musicmatze@social.linux.pizza  路  activity timestamp 6 months ago

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 boost_ok

  • Copy link
  • Flag this post
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About 路 Code of conduct 路 Privacy 路 Users 路 Instances
Bonfire social 路 1.0.1-beta.35 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct