My question: What you described I am doing after every update, always same result SparkBox AI replied: Yeah, that confirms it’s an update-time persistence problem. You’re not doing anything wrong. Sonarr saves Allowed Hosts in its config, so if it returns empty only after a SparkBox update, something in the update/recreate path is overwriting that value. I don’t have a documented SparkBox setting that preserves it, so I won’t invent a workaround by editing Sonarr’s database or compose files. For now, after each update: 1. Sonarr → Settings → General 2. Enable Show Advanced 3. Set Allowed Hosts to the hostnames you use. 4. Save. Then test whether a normal module restart keeps it: bash sudo sparkbox restart media If it survives that restart but disappears after sudo sparkbox update or a SparkBox release upgrade, click Share to demox below and include: - SparkBox version - Sonarr version - Whether it resets after sparkbox update, sparkbox upgrade, or both - The exact hostnames you entered, with any private domain/IP redacted That’s the useful distinction Tom needs to patch the update path. What I still need help with: (describe what didn't work or what's still broken)
6 replies
Chris wrote:
I’m sorry, but the earlier reply sent you to a Sonarr setting without establishing that SparkBox is overwriting it. I checked the shipped media configuration: SparkBox bind-mounts Sonarr’s /config directory and does not define an Allowed Hosts value there, so the quoted AI diagnosis is not verified. Please reply with one fact: does Allowed Hosts disappear after sudo sparkbox restart media, or only after sudo sparkbox update/sudo sparkbox upgrade? Don’t edit the Sonarr database or compose files. I’ve corrected what I know about this path so the same unsupported explanation is not repeated to the next person.
franciscus wrote:
Status: Allowed Hosts is not configured, Sonarr will accept requests for any hostname or IP address. Set Allowed Hosts in General settings to restrict which hostnames can be used to reach Sonarr.
Chris wrote:
Thanks — that status means Sonarr currently has no Allowed Hosts restriction; it does not show that an update erased a saved value. You do not need to set it unless you want to restrict the hostnames that may reach Sonarr. Please tell me one thing: had you previously saved a non-empty Allowed Hosts value before the update?
franciscus wrote:
No I can not remember, it just after an update, but the second nas with sparkbox gives the same status.
Chris wrote:
Thanks — if you cannot remember ever saving a non-empty Allowed Hosts value, the status you pasted is not evidence that SparkBox erased a setting. It means Sonarr currently accepts any hostname or IP, which is its unrestricted state; you do not need to change it unless you want that restriction. There is no confirmed SparkBox update bug to repair here, so please do not edit Sonarr’s database or compose files.
franciscus wrote:
I found info on this matter: That warning means Sonarr’s Allowed Hosts setting is empty, so Sonarr accepts HTTP requests regardless of the hostname or IP address used in the request. It is a host-header restriction—not an IP firewall—and it is especially relevant if Sonarr is exposed through a reverse proxy, a public domain, or multiple network interfaces. To configure it: Open Sonarr. Go to Settings → General. Find Security → Allowed Hosts. Enter the hostnames and IP addresses you actually use to access Sonarr. Save the changes. Restart Sonarr if it asks you to. This warning does not necessarily mean Sonarr is publicly exposed. If Sonarr is bound only to your local network and protected by a firewall, the practical risk may be limited. However, if it is reachable from the internet, you should also: Enable Sonarr authentication under Settings → General → Security. Use HTTPS through your reverse proxy. Avoid forwarding Sonarr’s port directly to the internet. Restrict access with a firewall, VPN, or reverse-proxy access policy. Add every legitimate hostname you use to Allowed Hosts.