Plugin Download (Network Failure)?

[jabonline]

So something is seriously wrong on my unRaid. It was able to download the plugin, but it got network failure. The other issue is that overall it seems very slow. My SabNZBd docker is downloading at < 1Mb/s. Normally I can get around 200MB/s copying over SMB 10GB DAC to my cahce drive (SSD). Hopefully someone has some insight to what is going on here, diagnostics attached...

 

This is what I got downloading the plugin:

plugin: installing: https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg
plugin: downloading https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg
plugin: downloading: https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg ... failed (Network failure)
plugin: https://raw.githubusercontent.com/dmacias72/unRAID-NerdPack/master/plugin/NerdPack.plg download failure (Network failure)

Updating Support Links



Finished Installing. If the DONE button did not appear, then you will need to click the red X in the top right corner

tower-diagnostics-20210315-2145.zip

[Squid]

IPADDR[1]="192.168.0.99"
NETMASK[1]="255.255.248.0"
GATEWAY[1]="192.168.1.1"

You sure your network settings are correct?  Usually (but I'm not a network guy) the gateway would be on the same network as the IP address

[SimonF]

Hi @Squid is valid as not a standard class c mask. 

[jabonline]

So no one has suggestions from the diagnostics I posted?

[ChatNoir]

1 hour ago, jabonline said:

So no one has suggestions from the diagnostics I posted?

 

Not a networking pro either but the guys did suggest things to look at.

 

7 hours ago, Squid said:

IPADDR[1]="192.168.0.99"
NETMASK[1]="255.255.248.0"
GATEWAY[1]="192.168.1.1"

You sure your network settings are correct?  Usually (but I'm not a network guy) the gateway would be on the same network as the IP address

 

7 hours ago, SimonF said:

Hi @Squid is valid as not a standard class c mask. 

 

Maybe this is deliberate and they are wrong, maybe this is worth looking into.

[bonienl]

2 hours ago, jabonline said:

So no one has suggestions from the diagnostics I posted?

 

You have a routing conflict between eth0 (192.168.0.2 obtained by DHCP) and the static settings of eth1 (192.168.0.99).

 

Delete the default gateway setting for eth1, and it should work.