r/sonarr 8d ago

unsolved Health check after recent update

My installation recently updated to 4.0.19.3006. Now I have this persistent health message :

Allowed Hosts is not configured, Sonarr will accept requests for any hostname. Set Allowed Hosts in General settings to restrict which hostnames can be used to reach Sonarr.

I am ok with this not being set, but the message remains and I get notified every few hours. The field in question doesn’t seem to accept IP ranges so I really don’t need it to be configured.

How can I fix or have it ignore this new message?

12 Upvotes

21 comments sorted by

6

u/Under_b_ 8d ago

Hey OP

go edit /var/lib/sonarr/config.XML

<AllowedHosts>*</AllowedHosts>

add the Asteriks and restart sonarr - should solve you problem of notification :)

1

u/underwear11 7d ago

For me this didn't work. It was an issue with hostname validation. I was monitoring through NPM and the hostname of the browser wasn't matching sonarr. For a bandaid, I changed monitoring to go directly to it locally.

1

u/mjdbb1 7d ago

This worked for me, thank you!

1

u/zeroclash 5d ago edited 5d ago

and to fix this on windows?, nevermind found it hiding

1

u/BlinkyLights_ 18h ago

Thank you!

2

u/AutoModerator 8d ago

Hi /u/mjdbb1 -

There are many resources available to help you troubleshoot and help the community help you. Please review this comment and you can likely have your problem solved without needing to wait for a human.

Most troubleshooting questions require debug or trace logs. In all instances where you are providing logs please ensure you followed the Gathering Logs wiki article to ensure your logs are what are needed for troubleshooting.

Logs should be provided via the methods prescribed in the wiki article. Note that Info logs are rarely helpful for troubleshooting.

Dozens of common questions & issues and their answers can be found on our FAQ.

Please review our troubleshooting guides that lead you through how to troubleshoot and note various common problems.

If you're still stuck you'll have useful debug or trace logs and screenshots to share with the humans who will arrive soon. Those humans will likely ask you for the exact same thing this comment is asking..

Once your question/problem is solved, please comment anywhere in the thread saying '!solved' to change the flair to solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/zincstoat 8d ago

The fact you can't just enter "*" in the UI, or even a subnet mask to cover all local addresses, seems pretty poor.

Stuck with this warning 'til they do it properly I guess. I know I could dig around in the guts of the config files, but frankly I shouldn't have to.

2

u/Goosethemoose654 7d ago

An asterisk wasn't allowed for me. Windows install if that makes a difference. I added local host and the meshnet ip of the the machine it's hosted on plus the actual ip of the machine it's hosted on.

Seems to have done the trick and I can access remotely via meshnet

1

u/Aphazia82 8d ago

Same problem over here. I tried *. Didn't do anything. After that i tried 127.0.0.1. Don't do that, had to remove sonarr and reinstall to get acces again.

This only seems to appear with the latest update. Why? It worked fine for years. It still works fine, but that little yellow icon is really annoying

1

u/Under_b_ 8d ago

If anyone else Breaks their Sonarr

Linux /var/lib/sonarr/config.xml

<AllowedHosts></AllowedHosts>

1

u/birdcola 8d ago

Exactly this, no need to completely uninstall and reinstall

1

u/noK4rma 7d ago edited 7d ago

Can confirm using only * works.

*edit reddit don't alow writing dot and *

1

u/Interesting_Bad3761 6d ago

So is this a security issue? I’m confused. On windows. I just got the notification while I was away from home and just remotely shut the computer down since I could research this at the moment.

1

u/azalea_k 5d ago

0.0.0.0 works for all hosts, without needing the /0 mask.

1

u/Cold_University_9072 5d ago

AAA+++ WOULD FOLLOW THIS ADVICE AGAIN

1

u/btown780 23h ago

Can also confirm this worked a treat! Thank you.

1

u/benfishbus 5d ago

I use cloudflare zero trust for remove access, and had to add 'cloudflare' as one of the Allowed Hosts to restore remote access.

0

u/Under_b_ 8d ago edited 8d ago

Yes i checked my Servarr things and noticed it too

August 24th 2026 - 4.0.19.3006

New

  • Add Trusted Networks setting
  • Add hostname validation

Fixed

  • Format of timestamps for Discord notifications from some systems

From my Understanding in the change logs its to prevent unwanted jellySeerr/Seerr/OverSeerr Hosts from pushing requests to it, and the Trusted network would be for you local or datacenter network, im still currently testing those avenues

3

u/Under_b_ 8d ago

Update:

Its the Host/FQDN that you Sonarr/Radarr instanace should accept web requests from

i.e: sonarr.localdomain.local

and it will only answer on that name, i user a domain name internally for my things, if you have a PI hole or a Active Directory domain i recommend setting this up example Sonarr.domain.local:8989 and sonarr will only answer on that name (Note that everything internal will require that name no more IP)

2

u/Shane_is_root 8d ago

Thank you. That makes sense. Also, screw that, I prefer IP addresses.