What snug supports

What supported means

snug calls a system supported only after the released server or app passes its tests there. The versioned support matrix is the machine-readable record, including how far checking has gone on the release you are running.

Servers

To run a supported server, use snug's server download; source checkouts and host-side builds are for development.

• Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, Debian 12 (Bookworm), or Debian 13 (Trixie)
• amd64 or arm64
• Linux kernel 6.1 or newer
• Docker Engine 28.5.2 or newer
• Docker Compose 2.24.4 or newer
• 1 logical CPU, 2 GiB of memory, and 20 GiB of free disk
• 5 GiB default total uploads, with 512 MiB per file

There is no native bare-metal server package.

Networks

The ordinary setup needs a directly reachable public IPv4 address, and a domain pointed at it if you want a name rather than the address:

• TCP 80 and 443 for the app
• UDP and TCP 40000-40400 for calls

Two setups work but count as advanced: a private network, because browsers still require a trusted HTTPS certificate; and dual-stack hosting, because live media still needs public IPv4. Hosts behind carrier-grade NAT without inbound reachability, and networks that need a relay, are unsupported.

Browsers and desktop apps

Desktop browsers target the current and previous major versions of Chrome, Edge, Firefox, and Safari, covering messages, files, voice, cameras, and screen sharing. Screen audio and background media depend on the browser and operating system.

The desktop app targets:

• macOS 13 or newer on Apple silicon and Intel, with DMG and ZIP packages
• Windows 11 x64, with an NSIS installer
• Ubuntu 24.04 x64, with AppImage and Debian packages on Wayland and X11

The installed app keeps calls running while minimized. macOS and Windows offer updates in snug, with a manual download when the updater cannot finish. AppImage updates in place; Debian uses its guided package path.

The installed app carries its own copy of snug and works with every server release since 3.0.0. A server admits apps released in the past 12 months, and an older one asks you to update it before joining.

Phones and tablets

Current iOS Safari and Android Chrome support foreground messages, files, voice, cameras, and receiving a screen share.

Not supported: starting a screen share from a phone, background calls, an installable home-screen app, and native iOS or Android apps.

Notifications

snug says nothing while it is closed. Browser notifications, operating-system notifications, Web Push, and native mobile push are unsupported. The settings guide covers the choices available while it's open.

Plans get through by another route. Subscribe a calendar app to your own snug calendar and that app does the reminding, on whatever schedule it keeps. The settings guide sets it up.

Who to ask

An admin runs the group inside snug: names, channels, roles. The server operator runs the Linux host behind it: backups, updates, the domain. In many groups that's one person; when it isn't, in-app questions go to an admin, and "the server is down" goes to the operator.

Ask for help

Members: use send feedback in the footer. It goes to the admins here and stays on this server, with your name on it so they can come back to you. Do not include sign-in codes, private messages, or files; nobody helping you needs them. For call problems, start with fix calls and sharing.

Admins: what people send you waits in Settings → Admin → Feedback. A note stays on that list until you clear it.

Reaching snug itself: write to snugchatadmin@gmail.com, or find @snug_chat on X. Feedback written in the app never travels to snug, so anything you want us to see needs to come through one of those. If the app has just gone wrong, include the error shown in the same window.

When the desktop app offers connection details, open it, then press copy details. The report includes the server address, app and system versions, timing, and local network results, but no sign-in or message content. It stays on your computer until you choose to copy it.

Operators: include the release, host system, browser, network shape, what the person tried, and what happened. ./snug-ops license status is safe to share. Never send state/.env, a backup, the .lic file, or signed license state. If the server is down or an operation was interrupted, start with recover the server.