Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To install Buzz on a VPS, deploy the production Docker Compose bundle from the official repository or use a provider’s Buzz one-click image, then connect the Buzz desktop app to the relay over HTTPS/WSS. A practical small-team starting point is 2 vCPUs, 4 GB RAM and 50 GB of disk; choose 8 GB RAM, 4 vCPUs and at least 100 GB when you expect heavier media, more concurrent agents or faster growth.
You also need a DNS name, TCP ports 80 and 443, Docker Engine with Compose, a securely generated Buzz identity, and backups stored outside the VPS. The relay—not the desktop client—stores channels, messages, users, agents and rules, so deployment, access control and data protection determine whether the installation is usable in production.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What does a Buzz VPS installation actually run?
Buzz is a self-hosted workspace built around a relay server. The relay stores the communities’ channels, messages, users, agents and rules. Relays are not federated: content created on one relay stays there and is not automatically shared with another relay.
A production installation is a multi-service stack rather than a single executable. The official deployment layout places the production Compose files in deploy/compose/. A typical bundle includes the Buzz relay, PostgreSQL for relational data, Redis for in-memory coordination, MinIO for object or media storage, Docker/Compose for orchestration and Caddy for HTTPS termination. The exact containers and environment variables can change with a release, so use the files shipped with the release you deploy.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
The Buzz desktop app is the client users need for chatting. A browser request to the relay’s HTTPS address may return relay metadata or a health response instead of a chat interface; that behavior does not by itself indicate a failed installation.
What do I need before installing Buzz?
Prepare every prerequisite before starting the containers. Missing DNS, TLS or persistent storage is the usual reason a technically correct container deployment is still unreachable.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →| Requirement | Small-team baseline | When to increase it |
|---|---|---|
| Linux VPS | 2 vCPUs, 4 GB RAM, 50 GB disk | Use about 4 vCPUs, 8 GB RAM and 100 GB or more for more users, agents, media or growth. These are documented 2026 guidance points, not a capacity guarantee. |
| Operating system and runtime | Linux with Docker Engine and Docker Compose | Keep the host and container images patched; choose a provider image only if you accept its supplied versions and layout. |
| DNS | A hostname whose A/AAAA record points to the VPS | Use a stable production name rather than an address that may change after a rebuild. |
| Network access | SSH plus TCP 80 and 443 | Permit only the ports your chosen deployment needs; do not expose database, Redis or object-storage administration ports publicly. |
| Identity | A Buzz identity/public key generated in the desktop app when your deployment workflow requires it | Keep the corresponding private key secret and maintain a secure recovery copy. |
| Accounts | A GitHub account or OAuth application if the selected access flow uses GitHub | Use an organization-controlled account for team administration rather than a departing employee’s personal account. |
| Backups | An external destination selected before launch | Use scheduled copies, retention and a tested restore location separate from the VPS. |
Before deployment, update the VPS, confirm that Docker and Compose are available, and verify that you can edit DNS. A public relay should use HTTPS and secure WebSockets (WSS); plan the hostname and certificate path before starting the application.
Should I use Docker Compose or a one-click VPS image?
Use the production Compose bundle when you need control over versions, volumes, environment variables and proxy configuration. Use a provider’s Buzz image when reducing manual setup is more important than controlling the underlying layout.
| Decision factor | Production Compose | Provider one-click image |
|---|---|---|
| Setup effort | Install Docker, clone the repository, configure secrets and start the services. | The image provisions the operating system and most services for you. |
| Control | Direct control of Compose files, image tags, persistent volumes and Caddy settings. | Faster initial setup, but the provider determines defaults and update workflow. |
| Included components | Those declared by the release in deploy/compose/. |
The documented DigitalOcean image includes Ubuntu 24.04 LTS, the Buzz relay, PostgreSQL, Redis, MinIO, Docker/Compose, Caddy, UFW and fail2ban. |
| Starting capacity | You choose the VPS; 2 vCPUs, 4 GB RAM and 50 GB disk is a reasonable small-team baseline. | The DigitalOcean image defaults to a 2-vCPU/4-GB Droplet and documents 50 GB as the small-team disk minimum. |
| Best fit | Operators comfortable reviewing configuration and maintaining containers. | Teams that want a guided provisioning path and accept provider-managed defaults. |
Do not use the repository root docker-compose.yml as a production deployment. The repository describes that file as a day-to-day development setup; the single-node production path is the bundle under deploy/compose/.
How do I install Buzz with the production Docker Compose bundle?
Install Docker and clone the repository on a clean Linux VPS, then configure the release’s environment and secrets before starting the stack. The commands below establish the documented directory and runtime; variable names and required secrets must come from the release you deploy.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
- Update the operating system.
sudo apt update && sudo apt upgrade -y - Install the Docker Compose plugin.
sudo apt install -y docker-compose-plugin - Verify the runtime.
docker --version docker compose versionBoth commands should return installed versions without a permission or socket error. If Docker requires elevated privileges on your distribution, run Compose with
sudoor add your deployment user to the Docker group and start a new login session. - Clone the official repository.
git clone https://github.com/block/buzz.git cd buzz/deploy/compose - Read the release configuration. Inspect the Compose files and accompanying environment documentation in this directory. Copy an example environment file only as a starting point; replace every placeholder secret with a newly generated value required by the current release. Never publish the file, paste secrets into tickets or reuse credentials from an example.
- Set the public hostname and service settings. Configure the relay’s externally reachable URL, database and object-storage persistence, authentication settings and any required OAuth values according to the release documentation. Keep persistent data on named Docker volumes or host paths that are included in your backup plan.
- Start the services.
docker compose up -dUse the Compose file supplied by the release if it requires an explicit
-foption. Follow startup output and confirm that every required service reaches a running or healthy state. - Review logs before opening access.
docker compose ps docker compose logs --tail=200Look for database migration failures, missing environment variables, certificate errors, binding conflicts and repeated container restarts. Fix those errors before proceeding to DNS or user invitations.
Keep the Compose directory and the exact image tags used for the deployment. Pinning and reviewing versions gives you a reproducible rollback point, while unreviewed floating tags can change behavior during a later restart.
How do I deploy Buzz with a provider’s one-click image?
A one-click image provisions more of the stack automatically, but you still must configure DNS, confirm the hostname, review credentials and test the relay. DigitalOcean’s documented Buzz 1-Click App uses Ubuntu 24.04 LTS and includes the relay, PostgreSQL, Redis, MinIO, Docker/Compose, Caddy, UFW and fail2ban.
- Create a new Droplet from the Buzz 1-Click App and select a size appropriate to your users. Its default is 2 vCPUs and 4 GB RAM; the documented small-team disk minimum is 50 GB.
- Record the public IPv4 address and connect over SSH using the provider’s instructions. Change any temporary credentials and confirm that the supplied firewall rules leave SSH, HTTP and HTTPS reachable as intended.
- Inspect the installed Compose files, environment settings, persistent volumes and certificate configuration. A prebuilt image saves time, but you remain responsible for updates, backups, secret rotation and data retention.
- Create the DNS record for your relay hostname, wait for it to resolve, then complete the Caddy or integrated proxy setup so the certificate can be issued.
- Open the relay URL over HTTPS, check the service logs and perform a desktop-client connection test before inviting users.
The image is convenient for a first deployment; Compose is preferable when you need to change service versions, storage locations or reverse-proxy behavior independently of provider defaults.
How do I configure DNS, HTTPS and WebSockets?
Point the relay hostname to the VPS before requesting a certificate, allow TCP 80 and 443, and verify that the proxy passes WebSocket upgrades. The desktop client should use wss://, not an insecure ws://, for a public relay.
- At your DNS provider, create an A record for
relay.example.compointing to the VPS IPv4 address. Add an AAAA record only when IPv6 is configured and firewalled correctly. - Wait for the record to resolve from outside your local network. Check both the hostname and the address returned; a stale record can send certificate requests to the wrong server.
- Allow inbound TCP 80 and 443 in the VPS firewall and provider firewall. Keep SSH restricted to trusted source addresses where practical.
- Configure Caddy or the provider’s integrated proxy with the exact hostname. Let it obtain and renew the certificate, then confirm that the certificate name matches the hostname users will enter.
- Test an HTTPS request and a WebSocket upgrade. A valid page or relay metadata response proves that the proxy is answering; a client connection test proves that the upgrade and authentication path also work.
If the desktop app asks for a relay address, enter the secure relay URL and replace the https:// scheme with wss:// as required by the client workflow. Do not append an arbitrary path unless the deployment documentation specifies one.
How do users connect from the Buzz desktop app?
Install the Buzz desktop app, add the relay’s WSS address, then join or create the community after the first owner account is ready. There is currently no browser-based chat interface, so a successful browser response is not a substitute for a desktop connection test.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
- Generate the Buzz identity/public key in the desktop app before deployment when your chosen workflow requests it. Protect the private key; anyone who obtains it may be able to act as that identity.
- In the desktop app, choose the option to add or connect to a relay and enter the WSS hostname, for example
wss://relay.example.com. - Authenticate through the configured identity or GitHub flow, depending on the release configuration.
- Create the first member or owner account, then create a community or accept an invitation.
- Send a test message and, if your deployment uses media or agents, perform one representative upload or agent action. Check the relay logs and object-storage volume when the test fails.
Keep the relay hostname stable. Changing it later requires updating every desktop client and may require certificate and OAuth callback changes.
How do I restrict registration and control access?
For a closed relay, disable open registration and allow only intended GitHub users. Configure these settings before invitations are sent:
BUZZ_ALLOW_REGISTRATION=falseprevents unsolicited account creation.BUZZ_ALLOWED_GITHUB_USERScan contain the specific GitHub usernames permitted by the deployment.
The official security behavior treats the allowlist as case-insensitive and evaluates it on every request, including requests made by existing sessions and deployment tokens. Therefore, removing a username has an immediate access effect; it is not merely a filter for new registrations.
Buzz is a small self-hosted service, not a complete isolation boundary for mutually untrusted tenants. If users or organizations cannot trust one another, place firewall, VPN or an upstream proxy policy in front of the relay and separate workloads rather than relying on application-level membership alone.
What should I back up, and how do I operate the VPS?
Back up every persistent data source used by the selected bundle and store copies outside the VPS. A database dump alone is insufficient when messages, uploaded media, identities or rules are distributed across volumes and services.
Back up the complete data set
- Identify PostgreSQL data, Redis data that the release treats as persistent, MinIO/object-storage data and Buzz application volumes.
- Schedule encrypted backups to an external destination with retention appropriate to your team.
- Record the Compose or image version, environment configuration location and secret-rotation procedure without placing private keys in the backup instructions.
- Restore to a separate test location periodically. Confirm that users, channels, messages, media and rules are present before trusting the backup.
Maintain the host and containers
- Monitor free disk space, especially object storage and uploaded media.
- Apply operating-system and container updates deliberately; review release notes and pin versions when you need reproducibility.
- Watch container health, restart loops, certificate renewal and firewall logs.
- Document how to replace a VPS, restore volumes, rotate secrets and reconnect clients.
Automatic snapshots can complement application-aware backups, but they should not be the only copy or the only tested recovery method.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
How should I choose VPS capacity and a provider?
Start with the documented small-team baseline, then size for concurrent agents, media volume, database growth and recovery headroom rather than CPU count alone.
| Workload signal | Capacity implication | Operational response |
|---|---|---|
| Few users, text-heavy channels | 2 vCPUs, 4 GB RAM and 50 GB disk may be an adequate starting point. | Monitor memory, disk and container health after launch. |
| Frequent uploads or media retention | Disk and object storage become the limiting resources first. | Choose at least 100 GB, define retention and move backups off-host. |
| Many simultaneous agents or background jobs | Additional CPU and RAM reduce contention with PostgreSQL and Redis. | Consider 4 vCPUs and 8 GB RAM, then observe actual usage. |
| High-latency distributed team | Distance to the VPS affects interactive response. | Select a region close to most users while retaining an independent backup location. |
When comparing providers, check documented Buzz image or template availability, CPU/RAM/disk headroom, included TLS and firewall defaults, control over Compose files and persistent volumes, snapshot and backup options, geographic latency, current pricing and support. The documented deployment guides establish capabilities and baseline resources, not a universal price or uptime commitment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What commonly goes wrong during installation?
The containers start, but the hostname is unreachable
Check the DNS record, provider firewall, local UFW rules and whether Caddy is listening on ports 80 and 443. A hostname that still resolves to an old address will fail before Buzz receives the request.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →HTTPS works, but the desktop app cannot connect
Confirm that the client uses wss://, that the certificate covers the exact hostname and that the reverse proxy permits WebSocket upgrades. Review relay and proxy logs for authentication, origin or path errors.
A service repeatedly restarts
Run docker compose ps and inspect the affected service with docker compose logs --tail=200. Missing secrets, invalid environment syntax, failed migrations, unavailable volumes and insufficient memory are more useful clues than repeatedly restarting the stack.
Users can register when the relay should be private
Verify BUZZ_ALLOW_REGISTRATION=false, check the exact spelling and reload or restart the service using the deployment’s documented method. Then confirm that BUZZ_ALLOWED_GITHUB_USERS contains only the intended usernames.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Messages work, but media or agents fail
Check MinIO or the configured object-storage volume, available disk space, credentials and the network path between the relay and that service. A text-only test does not validate every dependency in the multi-service stack.
A rebuild appears to erase data
Inspect whether the deployment uses named volumes or host-mounted paths and whether those paths were included in the backup. Recreating containers is safe only when persistent data is stored outside the disposable container layer.
What is the production-ready checklist?
- Production Compose files under
deploy/compose/or a documented Buzz one-click image are being used. - The VPS meets the selected workload’s CPU, RAM and disk requirements.
- DNS resolves to the correct VPS address.
- TCP 80 and 443 are open, while database and internal service ports remain private.
- Caddy or the integrated proxy serves a valid certificate for the relay hostname.
- The desktop app connects with the correct WSS address.
- The first owner is created and invitations are limited to intended users.
- Open registration is disabled when the relay is private, and the GitHub allowlist is reviewed.
- PostgreSQL, object storage and application volumes are backed up off-host.
- A restore has been tested separately and the procedure is documented.
- Version pinning, updates, disk monitoring and secret rotation have assigned owners.
Frequently Asked Questions
Does changing the GitHub allowlist remove access from people already signed in?
Yes. The documented allowlist is case-insensitive and is checked on every request, including existing sessions and deployment tokens. Removing a username therefore affects subsequent requests rather than only blocking future registrations.
Why does opening my relay URL in a browser not show a chat screen?
Buzz does not currently provide browser-based chat. The HTTPS endpoint may display relay metadata or another service response, while conversations are performed through the Buzz desktop app.
Do two Buzz relays automatically share communities or messages?
No. Relays are not federated, so a channel or message remains on the relay where it was created. Users on another relay will not see it unless you deliberately build a separate migration or sharing process.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat is the safest way to verify that my backups are usable?
Restore the database and persistent object-storage/application volumes to a separate test location, using the same or a compatible release. Confirm that accounts, messages, media and rules can be read before treating the backup as recoverable.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
