These answers start with the observable symptom. For changes to a running server, use the linked guides, identify the installed release and keep a recoverable configuration.
Why does the status page work while my stream returns 404?
The HTTP service can work without an active source. Check the exact mount path in administration, then the encoder’s output connection, credentials and source limit. A configured mount block does not start media. Also distinguish a missing stream from a wrongly formed playlist or alias URL.
Why is my source rejected despite the correct global password?
A mount-specific username or password can override the global source setting. Compare the encoder’s exact mount, protocol and identity with the effective configuration. Read the server error at the same time. An occupied mount or source limit is a separate cause and should not be “fixed” by weakening authentication.
Can a mount name create another bitrate or codec?
No. Icecast distributes the media supplied by a source or relay. A new suffix or MIME label does not re-encode audio. Generate the second representation in a source/processing workflow and send it to a separate mount if two qualities are needed. Test each representation with the intended players.
Does hidden or public=false protect the listening URL?
No. Those controls concern listing and directory publication. A directly requested stream may remain reachable. Use listener authentication and a suitable network policy when access must be restricted. Test the direct URL, aliases, intro and fallback paths with an unauthorised account as well as a valid one.
Why are JSON fields or sources missing?
The public JSON view exposes a subset of statistics. Fields depend on active sources and media format. Treat missing, single and multiple source cases explicitly in the consumer and handle reconnect resets. Do not scrape the status HTML or assume every example field exists at every moment.
Why does fallback switch the path but playback still fail?
The target must be available and its media compatible with the player’s current stream. Check codec/container, destination activity, authentication and the return policy separately. A fallback declaration does not create a source. Reproduce source loss and return on test mounts with actual listening rather than relying only on statistics.
Should I treat the latest documentation link as the current release?
No. At the editorial check, the download page offered 2.5.0 while the linked web documentation still labelled itself 2.4.1. Use the executable’s actual version and release-specific files. This portal records that boundary and labels 2.0.2 material as historical rather than silently promoting it to current guidance.
May I paste a complete configuration or access log for troubleshooting?
Review and redact it first. Configuration may include source/admin secrets, private callback endpoints and certificate paths; logs may contain listener addresses and requested URLs. Share only the relevant settings and time window, remove secrets and unnecessary personal data, and describe the installed version and observed symptom.