Receiving Server address news_newshosting_com:563 is not valid. on multiple servers
Posted: May 9th, 2025, 11:00 am
I have been using SABnzb docker with news_newshosting_com for years with zero issues. The other day, I had to switch ISPs. In my haste, I forgot to pause my queue and simply switched out cables. Since then, SABnzb has been receiving Server address news_newshosting_com:563 is not valid. I have also tried this using port 119 with the same results. I initially thought I had too many connections because of the switch but that's not the error I was getting back for that. When I hit the wrench for status and interfaces, I get a never-ending loading status. Now as a test I loaded NZBGet docker as a test and everything connects fine and resolves. So this tells me its an issue with SABnzb docker. I also loaded the SABnzb Windows program and it connected fine as well.
Does anyone have a clue? I have tested this on two separate machines on two different ISPs on two different networks with the same results. I get the resolve issue on SABnzb docker, but it works fine with NZBGet, both Windows and Linux Docker. I can also ping and do NSLookups with no issues from the machines themselves. I can also do pings and nslookups inside the docker itself with no issue as well.
One other piece of info is that I am using SABnzbd dockers. One on a Seedbox and the other on an UNRaid Linux server.
**I had to put _ instead of dot for the newshosting address because of board restrictions for new users**
Does anyone have a clue? I have tested this on two separate machines on two different ISPs on two different networks with the same results. I get the resolve issue on SABnzb docker, but it works fine with NZBGet, both Windows and Linux Docker. I can also ping and do NSLookups with no issues from the machines themselves. I can also do pings and nslookups inside the docker itself with no issue as well.
One other piece of info is that I am using SABnzbd dockers. One on a Seedbox and the other on an UNRaid Linux server.
**I had to put _ instead of dot for the newshosting address because of board restrictions for new users**