How to Self-Host Samba
Samba open-source SMB file and print services for interoperable network shares, Windows-compatible authentication, and Active Directory roles. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Samba is a good fit
Choose Samba when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Install the operating-system package, define only the required shares in smb.conf, validate the file, and restrict SMB to trusted network interfaces.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Back up share data, Samba configuration, and identity databases. Preserve file ownership, ACLs, and extended attributes during recovery.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Never expose SMB directly to the public internet; patch promptly and require modern protocol versions and strong credentials.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
