Build recovery for the link that failed: make the source reconnect to its streaming server, keep a local backup audio source ready, and make the listener’s player retry after connectivity returns. These measures cover different parts of the chain. If the listener has no internet at all, no live stream can deliver new audio; only audio already buffered or stored locally can keep playing during the outage.
First identify where the outage happened
A sleep-sounds stream usually has three links: the source that generates or plays the audio, the server that relays it, and the listener’s device and network. Recovery on one link does not repair the others.
As an Amazon Associate I earn from qualifying purchases.
| Failure point | What stops working | Recovery to configure |
|---|---|---|
| Source to streaming server | The encoder cannot send audio to the relay, or the relay closes its connection. | Keep the source process running and configure its client to reconnect. Use a local backup source if the primary audio becomes unavailable. |
| Streaming server to listener | The server or its delivery path cannot provide the stream. | Check the server and delivery setup. A source-side fallback alone cannot fix a server outage. |
| Listener to network | The listener’s device cannot fetch the live audio. | Have the player detect stalled or failed media and retry after connectivity returns. For a longer outage, use audio stored on the device. |
Before changing settings, note whether the source is still producing audio, whether the server still has the stream, and whether the listener can reach other sites. Those observations help distinguish an upload failure from a relay or listener-network failure.
Make the source reconnect to the streaming server
Liquidsoap sending to Icecast
Liquidsoap’s 2.5.x development documentation for streaming to Icecast and Shoutcast says that if the connection fails or the server closes it, Liquidsoap logs the error and tries again after three seconds by default. It continues retrying while the script is running. Treat that as documented behavior for that version, not as a universal guarantee for every client or deployment.
#1 Best Overall
- 【Fast Wi-Fi 6, 3000M wireless speed】GL-X2000 provides reliable cellular networks for remote access and high speed internet in urban areas with up to 574Mbps (2.4GHz) + 2402Mbps (5GHz) Wi-Fi speeds.*Speed Tests conducted on a local network. Real world speeds may differ depending on your network configuration.
- 【Dual-SIM with Single Standby】Dual-SIM flexibility for selecting the stronger and faster ISP connection, AT&T & T-Mobile certificated while supporting Network Failover and the option to configure Failover priorities among multiple connection methods.
- 【Multi-WAN】Spitz Plus' cellular 4G router with multi-WAN technology lets users utilize multiple connection methods, including Ethernet, Repeater, Cellular, and Tethering; Load-balancing capabilities let users distribute bandwidth by custom proportion among multiple connection methods.
- 【VPN Tunnelling & Remote Access】Provides pre-installed OpenVPN and WireGuard to support 30+ VPN services and encrypts all network traffic within the connected network so that the network is secured when connecting to a public Wi-Fi. Max. VPN speed of 30 Mbps (OpenVPN); 190 Mbps (WireGuard) *Speed Tests conducted on a local network. Real world speeds may differ depending on your network configuration.
- 【Interchangeable SMA Connectors】The GL-X2000 features four SMA connectors, allowing for the integration of multiple external antennas to enhance the device's performance across various application scenarios.
The same development documentation gives a five-second default for connection_timeout, which controls how long connection establishment waits, and a 30-second default for timeout, which controls read/write waiting. Confirm these values against the Liquidsoap version you actually run before relying on them. Liquidsoap also offers connect, disconnect, and error callbacks that can log state changes; an error callback can choose a delay or stop retries. A callback that stops retries is inappropriate if unattended recovery is a requirement.
Keep the Liquidsoap script and its host process running. Automatic reconnection cannot help if the script exits, the host shuts down, or credentials and server configuration are invalid. Check source logs after a test interruption to verify that retries continue and that the stream returns to the expected Icecast mount.
Ices 2 source client
Ices 2.0.3 documents separate settings named reconnectdelay, reconnectattempts, and retry-initial. These are Ices settings, not Liquidsoap settings. In particular, a configured attempt limit can stop the instance once its retries are exhausted; choose it deliberately if the client must recover without an operator present. The documentation does not establish one best retry interval for every network and server.
Free tools Windows power users keep installed
One-click scans. No signup required.
Keep sleep audio playing if the primary source fails
A reconnecting encoder restores its connection, but it does not necessarily have usable audio to send while its primary source is unavailable. Prepare a locally accessible ambient loop or backup playlist and configure the source to switch to it when needed.
Liquidsoap’s Quickstart describes mksafe as making an unavailable source produce silence, and fallback as switching to an always-available backup source. For sleep audio, silence may be a worse fallback than another suitable ambient recording, so use a backup source if continued sound is the goal. This is a design choice, not a guarantee of seamless transitions.
Source fallback only helps while the source can still reach the streaming server. If the listener’s own internet is down, an upstream backup playlist does not make the server reachable.
Make a browser player retry after connectivity returns
A custom browser player can monitor the media element’s stalled, waiting, and error events. They indicate that fetching has stopped, playback is waiting for data, or a resource/network error occurred. Use those states to show a clear status and begin a controlled retry rather than assuming the browser will resume by itself.
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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #2
- Support Multiple Users: USB portable WiFi supports multiple terminals to access the Internet at the same time, and supports 10 devices, such as mobile phones,laptops, computers, smart TVs and other devices.
- USB Powered: Portable WIFI supports multiple 4G networks, sharing up to 10 wifi users, powered by devices with USB ports, such as mobile phone chargers, car chargers, power banks, etc.
- High Speed Stable: 4G USB portable WIFI provides fast and stable high speed Internet access, high speed 4G internet, stable signal, feel the wonderful internet life, and fast Internet access.
- Plug and play: 4G mobile WiFi is plug and play, enjoy 4G internet, convenient USB power supply method, connect power device, insert SIM card, use SIM card data to surf the Internet anytime, anywhere.
- Multiple Protection: WiFi router adopts multiple protection design, more secure, WPA/WPA2 WiFi encryption, effectively avoid internet squatting, support data control.
- Detect the failure. Record the relevant media events and, where useful, whether the browser appears online. An online indication does not prove that the stream server is reachable.
- Wait for a retry condition. Avoid repeatedly reloading a resource while the listener is still offline. Use a bounded delay or a connectivity change as a reason to attempt loading again.
- Reload the media source. MDN documents
HTMLMediaElement.load()as resetting the media element and starting source selection and loading again. It aborts ongoing operations; it is not a promise that playback will resume automatically. - Wait for readiness and handle playback failure. Request playback when the media is ready, and handle a rejected playback request or browser autoplay restrictions. If the browser requires a user gesture, show a resume control instead of repeatedly trying without user input.
- Tell the listener what to do. Show whether the player is reconnecting, waiting for network access, or needs a tap to resume. This distinguishes a recoverable stream interruption from a device that remains offline.
For a player built with Media Source Extensions, the application also owns segment fetching and buffering. It must handle failed chunk requests and re-establish its media pipeline; a generic media-element reload recipe is not enough to specify that recovery.
When segmented delivery is worth considering
Liquidsoap can produce HLS files for a web server to serve. The Liquidsoap book describes HLS and DASH as using rolling playlists of short segments and adaptive variants that can switch to a lower bitrate as connection quality changes. Its example describes a playlist with the last minute of audio split into two-second segments. Those figures are illustrative, not a universal configuration or guarantee.
Segmented adaptive delivery can help when bandwidth weakens, but it adds delivery and player behavior to maintain. It does not supply new audio during a complete loss of connectivity. A simple Icecast stream and HLS are different architectures; choose based on your existing server and player rather than treating one as a universal fix.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What can keep playing during a total listener-side outage?
A live stream cannot cross a completely unavailable listener internet connection. A player may continue for the duration of audio it already has buffered, but the buffer only covers that amount of time. For dependable listening through a longer outage, keep an offline audio copy on the playback device and use a local player. Do not mistake buffering for a reliable offline library.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Test recovery one link at a time
The exact server, host, browser, and outage duration determine what recovery looks like, so verify your own setup rather than assuming a retry setting guarantees continuity.
- Interrupt the source-to-server connection while leaving the source process running. Check logs for errors and retries, then confirm the source returns to the correct mount.
- Make the primary audio source unavailable while preserving the source-to-server connection. Confirm that the configured backup audio plays, rather than silence, if that is the intended behavior.
- Interrupt the listener’s network while leaving the stream server available. Observe the player’s events and status, restore connectivity, and confirm it reloads or presents a clear resume control.
- Test a longer listener-side outage with no network. Confirm the player’s actual buffer duration and test the local audio copy if offline continuity matters.
Troubleshooting common recovery failures
| Symptom | Likely cause | What to check or change |
|---|---|---|
| The source logs an error but never returns. | The source process stopped, retries are capped or disabled, or the server address or credentials are wrong. | Check that the process remains running, inspect client-specific retry settings and logs, and verify the server and mount configuration. |
| The stream reconnects but listeners hear silence. | The audio source is unavailable and the configuration inserts silence, or the backup is not reachable. | Check source availability and fallback behavior. In Liquidsoap, distinguish mksafe silence from a fallback source. |
| The stream is live, but one browser stays stuck. | The media fetch stalled or failed, and the player did not reload or playback was blocked by browser policy. | Inspect media events, retry loading after connectivity returns, handle playback errors, and offer a user-gesture resume control where needed. |
| The listener hears audio briefly and then it stops offline. | The existing buffer was exhausted; live audio cannot arrive without a network connection. | Use a local copy for longer offline playback. |
| Lowering bitrate does not restore playback during a complete outage. | Adaptive bitrate addresses weak bandwidth, not absent connectivity. | Restore connectivity or use audio stored locally. |
Or let it run in the cloud
StreamNeo is a YouTube-only service for keeping a channel live from uploaded videos; it is not a browser-player repair tool and does not provide live audio to a listener whose internet is down. To use it, upload a recording or build a playlist, add your YouTube stream key, and go live. StreamNeo loops the uploaded video in the cloud, so no home computer or connection has to stay on. It supports the uploaded quality up to 4K 60fps at one flat price per slot, automatically recovers if YouTube drops the stream, and includes a first day free with no card. Monthly service is $9.99 per month. Learn about StreamNeo, or start the free day.
Quick Recap
Sources and version notes
- Liquidsoap, “Streaming to Icecast and Shoutcast,” version 2.5.x development documentation: reconnect behavior, timeout defaults, and callbacks.
- Liquidsoap, “Quickstart,” version 2.5.x development documentation: source failure handling and HLS output.
- Icecast project, “IceS v2.0 Documentation: Configuration,” version 2.0.3: Ices reconnect settings.
- Apple Developer Documentation, “HTMLMediaElement,” and MDN, “HTMLMediaElement: error event”: browser media events and state.
- MDN, “HTMLMediaElement: load() method,” last modified 2025-04-10: media reload behavior.
- Liquidsoap project, “The Liquidsoap book”: HLS/DASH segmentation and adaptive-quality overview.
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.
