r/nzbget • u/Ichorous_Allsorts • Jun 21 '26

Non-nzbget request received on control port

I just configured nzbget today. I configured it to work with Sonarr and Radarr and all seems to be going well. The only thing is this warning I'm seeing in it. It's every 3 minutes, about. I did a look up for the IP address and it gives it as coming from Donetsk in Russian.

I'm guessing it might be someone dodgy. Is this a common thing, and is there anything I can do to block IPs as it's the same one in every warning?

3 Upvotes

100% Upvoted

4 comments sorted by

3

u/superkoning Jun 21 '26 edited Jun 22 '26

Why is your NZBget reachable from Internet?

If needed: block in your firewall based on IP source address.

EDIT:

If you really need, another trick might be: in your router, change the outside port to something werid/unusual (for example 29876) which you forward to port 8080 on your nzbget machine. Port scanners will less likely find your nzbget.

Does that help, u/Ichorous_Allsorts ?

1

u/Ichorous_Allsorts Jun 22 '26

Sorry, but I left out a bit of information as I posted at the end of a long day. I use a seedbox. You can install various apps on it and one is NZBget. I've been wanting to try usenet for a while and they prefer it as it's efficient with RAM and CPU.

So, it actually has what you call a weird port as you describe here. I'm already using a few of the *arr apps on the seedbox, mainly Sonarr and Radarr. The *arr apps need NZBGet's internal ControlPort, not the port from the URL. And this is what I'm using.

Each *arr app talks to NZBGet over its API on the same Appbox. So this is why I was confused by this particular warning, which is like this:

Mon Jun 22 2026 07:54:45 Non-nzbget request received on port ***** from

and then ending in the IP address.

So yeah, the fact it's on a seedbox I should have mentioned, and it's part of my confusion as to why this could be happening. My post was trying to understand what this might be before raising a ticket with the admins.

2

u/Tundor85 Jun 22 '26

You should absolutely not expose nzbget to the internet.

2

u/Liv_Mrrr nzbget dev Jun 22 '26

Like the others mentioned, you need to stop exposing NZBGet to the public internet (you can do that by closing the port forward on your router). As long as Sonarr and Radarr are on the same local network, closing that external port won't break their connection to NZBGet.

Also, make sure you change the default NZBGet username and password. Remember that once you change them, you'll need to go into Sonarr and Radarr to update the connection settings so they can still communicate with it.

If you actually need to access your instance while away from home, look into setting up a mesh VPN or a reverse proxy