If your Gurbani stream generator and listener-facing server are both on the VPS being rebooted, listeners should expect an interruption. A process manager such as systemd can restart Liquidsoap after it stops, but it cannot keep that VPS online while the host reboots. To keep the public stream available, use a listener endpoint on an independent running host with a working source or fallback, or configure and test a standby with traffic failover. Even then, existing listeners may need to reconnect.
First identify what the update will do
“Update” can mean three different operations, with different effects on listeners:
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- Configuration reload: If the streaming server supports an in-place reload, it may apply changes without disconnecting sources and listeners.
- Application or service restart: Liquidsoap or Icecast stops and starts. A process manager can bring a stopped process back, but listeners may lose the connection.
- VPS reboot: The host and every service running only on it become unavailable until it returns. Restart policies do not provide availability during that gap.
Liquidsoap’s Icecast-compatible server documentation says a configuration reload can preserve connected sources and listeners, while some settings require a restart. Check the documentation matching your installed version and the specific setting before relying on reload behavior. The surfaced Liquidsoap reference is version 2.5.x development documentation, so confirm the equivalent stable reference for your release: Liquidsoap server documentation.
For a configuration change, reload if the relevant setting supports it
When the host does not need to reboot, prefer a supported in-place reload over restarting the server. Liquidsoap documents reload behavior for its Icecast-compatible server, including preservation of connected sources and listeners; not every setting takes effect this way. Confirm both the setting and your installed version in the server documentation.
#1 Best Overall
For a service update on one VPS
Run Liquidsoap in the foreground under a service manager rather than relying on an interactive shell. Liquidsoap’s project documentation advises: “In production, run liquidsoap in the foreground under a service manager, such as systemd on Linux or launchd on macOS.” Its production example uses Restart=always. That is process recovery after a stop, not protection from a VPS reboot or host outage. See the Liquidsoap production documentation.
- Identify the operation. Establish whether the change is configuration-only, will restart a service, or requires a host reboot. Check the VPS provider’s maintenance notice for host-level work.
- Save the current setup. Back up the Liquidsoap configuration and note the playlist and media references. Confirm the service is enabled to start at boot.
- Validate script edits. Before restarting after a Liquidsoap script change, run
liquidsoap --check /etc/liquidsoap/radio.liq. Use the correct configuration path for your installation. - Reload where supported. If the changed setting supports reload in your installed version, use that instead of restarting the server.
- Set listener expectations. For a necessary VPS reboot, announce a maintenance window unless an independent relay or tested standby will serve listeners.
- Verify the entire path afterward. Check the service manager, that Liquidsoap connects to the streaming server, the public mount URL, and that audio—not just a running process—is available. Check monitoring alerts too.
Exact service commands vary by operating system, service name, and installation. The command above is the documented validation example for the stated configuration path; do not assume that path or a particular restart command applies to every VPS.
Recommended Free Tools
Keep the listener endpoint on an independent relay
Liquidsoap’s documented architecture separates a stream generator from an Icecast server that relays audio to listeners. Hosting the listener-facing relay on another, independently running system can keep the public endpoint available during maintenance of the generator VPS—but only if the relay has a viable audio source or fallback while the generator is unavailable. Moving Icecast alone, while leaving the only generator on the rebooting VPS, does not ensure listeners hear audio.
Plan the source or fallback audio, how the relay behaves when the source disappears, and how listeners continue to use a stable public URL. The relevant architecture and server behavior are described in the Liquidsoap production documentation and server documentation.
Use a standby node when reduced interruption is worth the complexity
An active-standby setup can direct traffic to a ready second host when the primary becomes unavailable. It generally requires a second host, health checks, configuration and content synchronization where needed, and provider-supported traffic switching. AWS’s floating-IP example is specific to AWS architecture, not a feature you can assume on every VPS provider: AWS Elastic IP addresses.
Failover reduces dependence on one host; it does not guarantee zero downtime. Existing media sessions may be dropped and listeners may have to reconnect unless continuity is separately engineered. Liquidsoap also documents fallback mounts that can switch sources while listeners remain on a mount, but that helps with source loss within that server architecture—it does not make a VPS survive its own reboot. See the Liquidsoap server documentation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose the maintenance path by the availability you need
| Approach | Best fit | What it can protect | Important limitation |
|---|---|---|---|
| Supported in-place reload | A configuration change on a running server | May preserve connected sources and listeners | Setting- and version-dependent; does not cover a host reboot. |
| One VPS with a service manager | Recovering Liquidsoap or another service after a process stop | Automatic process restart, including after the VPS returns if enabled at boot | Cannot serve listeners while that single VPS is rebooting. |
| Independent listener relay | Keeping a public endpoint on a separate running host | Relay availability during generator maintenance, if it has a working source or fallback | A separate relay without audio to play does not maintain the stream. |
| Active-standby with traffic switching | Reducing interruption when a primary host fails or is maintained | Can move traffic to a ready standby | Requires tested failover; active listeners may disconnect and reconnect. |
Troubleshoot after an update
- The service is stopped after maintenance: Check the service manager’s status and logs, confirm the service is enabled at boot, and inspect configuration validation errors.
- The process is running but the public URL is silent: A running process does not prove the complete generator-to-server-to-listener chain works. Check the source connection, mount, and actual audio playback.
- Listeners disconnect during a reboot: This is expected if their endpoint was on the rebooting host. A restart policy cannot bridge host unavailability; use an independent relay or tested standby if continuity is required.
- A reload disconnects listeners or misses a setting: Confirm that the setting supports reload in your installed Liquidsoap version. Some settings take effect only after a restart.
- Failover sends listeners to an empty stream: Check that the standby or relay has a usable source or fallback, and that traffic switching and the public URL work as designed.
Cost and maintenance planning
There is no published general downtime estimate for a VPS update or reboot. Use the provider’s maintenance notice or your own measurements rather than promising listeners a specific outage duration. A separate relay or standby also adds another host and operational work; it does not by itself guarantee seamless playback.
For a Gurbani stream, plan updates around listener impact: tell listeners when a single-host reboot is expected, test reloads and failover before depending on them, and verify that the public URL carries audible audio once maintenance is complete.
Or let it run in the cloud
If your goal is an always-on YouTube stream of uploaded Gurbani recordings rather than a self-managed Icecast radio endpoint, StreamNeo is a different option: upload your recording or playlist, add your YouTube stream key, and go live. Nothing at home has to stay on; it streams the uploaded video as made, up to 4K 60fps, at one flat price per slot, and automatically recovers if YouTube drops the stream. The first day is free with no card. Monthly: $9.99 per month. StreamNeo is for YouTube video streams, not Icecast radio or camera broadcasts. Start the free day.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →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.
