SOLVED: SABnzbd Connection failed!
Posted: Mon Feb 20, 2017 9:58 am
My status is returning:
This is entirely my own fault and I can rollback if the problem is not resolvable.
I've provisioned two HDAs in network @ 192.168.0.100 and the other at 192.168.0.10. I turned DHCP/DNS serving off on ...10 which is more of a NAS server really: it has webmin and miniDNLA only installed. ...100 has SABnzbd, CouchPotato and Sickrage deployed and it serves DHCP. This setup worked fine (so why mess with it?!)
I had delay issues with web browsing so I switched off the DHCP/DNS services on ...100 and turned then on for ...10. Web browsing performance seems smoother so I like to keep DNS resolving on ...10 if possible.
I manually created DNS Aliases on ...10 for the applications installed on ...100. Wordpress, for example, works fine and my blog resolves from inside and outside the LAN. I can access all apps from the LAN including SABnzbd.
The only issue in my non-standard set up is SABnzbd connectivity. I'm running iptables (on both servers) and this is the entry I added to ...10:
563 is the port I access my news service on. I'm not sure that this is a useful entry, but if I opened WAN access to 25915 I'd be able to access SABnzbd from outside the LAN which is not what I want. I have port forwarding setup on my router for torrents and suspect I need the same for SAB... but which port?
I realise this is not a normal Amahi setup, so the support I can expect is very limited. However, some generic pointers should get this resolved for me I hope.
Code: Select all
Local IPv4 address 192.168.0.100
Public IPv4 address Connection failed!
IPv6 address None
Nameserver/DNS Lookup Connection failed!
I've provisioned two HDAs in network @ 192.168.0.100 and the other at 192.168.0.10. I turned DHCP/DNS serving off on ...10 which is more of a NAS server really: it has webmin and miniDNLA only installed. ...100 has SABnzbd, CouchPotato and Sickrage deployed and it serves DHCP. This setup worked fine (so why mess with it?!)
I had delay issues with web browsing so I switched off the DHCP/DNS services on ...100 and turned then on for ...10. Web browsing performance seems smoother so I like to keep DNS resolving on ...10 if possible.
I manually created DNS Aliases on ...10 for the applications installed on ...100. Wordpress, for example, works fine and my blog resolves from inside and outside the LAN. I can access all apps from the LAN including SABnzbd.
The only issue in my non-standard set up is SABnzbd connectivity. I'm running iptables (on both servers) and this is the entry I added to ...10:
Code: Select all
## Open access to SABnzbdPlus server
-A INPUT -m state --state NEW -p tcp --dport 563 -j ACCEPT
-A INPUT -m state --state NEW -p udp --dport 563 -j ACCEPT
I realise this is not a normal Amahi setup, so the support I can expect is very limited. However, some generic pointers should get this resolved for me I hope.