Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

wget from within Putty keeps failing, using both telnet and ssh, how to fix?

Featured Replies

Hello, I'm trying to wget some files using a putty session, connecting to unRAID, but it just can't connect to any server.  I've tried with both an SSH connection, and a regular telnet connection; both fail the same.

 

I'm getting this error message...

 

root@media:~# wget http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/installer-amd64/current/images/netboot/xen/initrd.gz

--2014-04-28 13:20:36--  http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/installer-amd64/current/images/netboot/xen/initrd.gz

Resolving archive.ubuntu.com (archive.ubuntu.com)... failed: File exists.

wget: unable to resolve host address âarchive.ubuntu.comâ

 

It's the same error message for any address I try  >  unable to resolve host address

 

It shows an â before and after the address, I have no idea why.  I suspect it's something to do with the parenthesis, but that's just a guess.

 

Also, I cannot Ping any address.  I tried google.com and their IP address.  Either attempt just results in the window going blank until I hit ctl-c to break the effort.

 

I can ping google.com just fine from a cmd window in windows on the same machine.

 

Also, I can update programs, and install ubuntu from Putty, so I have an internet connection, I just can't wget or Ping.

 

Very strange to me, but maybe someone knows how to 'fix' this weird issue.

  • Author

anyone got any ideas?  I've tried changing the Gateway from my router IP to my modem IP, still doesn't work.

 

I've added 2 new DNS server addresses, from my ISP, and it still doesn't work.

 

What am I missing?  I'm out of ideas.

  • Author

for some unknown reason, wget works just fine in the Arch Virtual Machine, but still not in unRAID. 

 

[root@IronicsArchVM_v4 ~]# wget https://raw.githubusercontent.com/lonix/BUUX/master/Buux.sh && chmod +x Buux.sh
--2014-05-04 17:30:24--  https://raw.githubusercontent.com/lonix/BUUX/master/Buux.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 199.27.79.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|199.27.79.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7380 (7.2K) [text/plain]
Saving to: ‘Buux.sh’

100%[======================================>] 7,380       --.-K/s   in 0.02s

2014-05-04 17:30:25 (438 KB/s) - ‘Buux.sh’ saved [7380/7380]

 

I tried entering the actual IP instead of the address, but still no luck :(

 

root@media:/boot#   cd /boot && wget https://raw.githubusercontent.com/lonix/BUUX/master/Buux.sh && chmod +x Buux.sh
--2014-05-04 17:39:46--  https://raw.githubusercontent.com/lonix/BUUX/master/Buux.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... failed: File exists.
wget: unable to resolve host address ‘raw.githubusercontent.com’
root@media:/boot#   cd /boot && wget https://199.27.79.133/lonix/BUUX/master/Buux.sh && chmod +x Buux.sh
--2014-05-04 17:41:37--  https://199.27.79.133/lonix/BUUX/master/Buux.sh
Connecting to 199.27.79.133:443... failed: Network is unreachable.
root@media:/boot#   cd /boot && wget https://199.27.79.133:443/lonix/BUUX/master/Buux.sh && chmod +x Buux.sh
--2014-05-04 17:41:43--  https://199.27.79.133/lonix/BUUX/master/Buux.sh
Connecting to 199.27.79.133:443... failed: Network is unreachable.

Type

ifconfig

and see if the VM is getting assigned an IP address. 

 

Also as a hint, to check network connectivity I always ping "8.8.8.8", its Google's DNS servers and is up about 99.9% of the time.

  • Author

ifconfig is not a valid command in the ArchVM, but ifconfig gives this in unRAID, via Putty...

 

root@media:/boot# ifconfig
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.20.150  netmask 255.255.255.0  broadcast 192.168.20.255
        ether 00:1b:21:c6:e2:c6  txqueuelen 0  (Ethernet)
        RX packets 3596  bytes 323222 (315.6 KiB)
        RX errors 0  dropped 305  overruns 0  frame 0
        TX packets 1856  bytes 394650 (385.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether bc:5f:f4:bc:17:55  txqueuelen 1000  (Ethernet)
        RX packets 5089  bytes 950866 (928.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6386  bytes 1311286 (1.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf0b00000-f0b20000

eth2: flags=4355<UP,BROADCAST,PROMISC,MULTICAST>  mtu 1500
        ether 00:1b:21:c6:e2:c6  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  memory 0xf0ac0000-f0ae0000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 268  bytes 26100 (25.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 268  bytes 26100 (25.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif1.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
        RX packets 2060  bytes 186920 (182.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3058  bytes 521718 (509.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

from unRAID via putty, I get this...

 

root@media:/boot# ping 8.8.8.8
connect: Network is unreachable

 

and from the VM, also via putty, I get this...

 

[root@IronicsArchVM_v4 ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8. 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=48 time=85.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=48 time=86.7 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=48 time=86.5 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=48 time=86.9 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=48 time=86.5 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=48 time=86.9 ms

 

I can't figure out why it works from the VM, but not from unRAID directly, since they share the same network bridge, as far as I understand.

 

Well clearly unRAID has no internet, unfortunately I don't know very much about unRAID 6.0 and its bridge.  So I can't really help here, sorry about that.

 

I had a problem awhile back with bridges and DHCP, my router was getting confused and assigning wrong address' so I had to create static leases. 

 

Just as an FYI for Arch the "ifconfig" equivalent is "ip addr"

  • Author

Well clearly unRAID has no internet

 

It would seem so, but how does the VM have internet, if it's subordinate to unRAID?

I had the same problem back when I was running Arch as a Xen host, the bridge wasn't working properly, or wasn't being assigned a proper IP.  The VM's would work, but the host lost internet.  I don't remember what I did to fix it, and I no longer run Xen so I can't check.

 

It probably won't work, but when in doubt.  I'd disable the bridge, stop the array, reboot.  Enable the bridge, and hope it works.  Also if you can, I'd go to your routers config page, and release the DHCP leases.  That way everything gets assigned a shiny new IP address.  It may not work, but I suppose it's worth a shot.

Are both ArchVM and UnRAID provided with static address, or DHCP?

 

Can you run the ip addr command from your VM so we can compare the IP, subnet and gateway addresses.

 

If you are getting internet from the VM and not from the UnRAID host then it's most likely you've manually set a gateway on the host that is incorrect.

 

You mention that your UnRAID host is 192.168.20.150. Can you ping that from another machine on your network (i.e. preferably not a VM on the UnRAID host). If it's pingable then it's definitely a gateway address.

 

See what gateway you get from the VM and apply it to the UnRAID host (if you can ping from within your network) and also confirm the DNS settings between VM & Host.

  • Author

Are both ArchVM and UnRAID provided with static address, or DHCP?

 

Yes, I have a static IP setup for unRAID 192.168.202.150) from the unRAID GUI settings area.  I have a static IP assigned to the VM (192.168.20.145) from within my router, since I couldn't find any place to assign an IP from within the VM itself.

 

Can you run the ip addr command from your VM so we can compare the IP, subnet and gateway addresses.

 

Yes, see below...

 

[root@IronicsArchVM_v4 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:16:3e:a2:b2:c2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.20.145/24 brd 192.168.20.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:fea2:b2c2/64 scope link
       valid_lft forever preferred_lft forever

 

 

If you are getting internet from the VM and not from the UnRAID host then it's most likely you've manually set a gateway on the host that is incorrect.

 

Certainly likely.  I think I had it set for my router's IP address, but when I tried to change it to the modem IP, it no longer saves.  I have tried to change it several times, and after stopping NFS and SMB, the GUI settings screen just continues to show grey boxes, and won't let me change anything, and the apply and done boxes are gone.  I've tried many times, and have rebooted the server a few times, still cannot make any changes to the settings.  I've also tried making changes in the network.cfg file directly, but even though it seems those changes stick, they are not visible in the settings dialog.  Every time I go into network settings, the Gateway box is blank.  I've reported this as a bug in the v6b5a release thread, but no response there yet.

 

You mention that your UnRAID host is 192.168.20.150. Can you ping that from another machine on your network (i.e. preferably not a VM on the UnRAID host). If it's pingable then it's definitely a gateway address.

 

See what gateway you get from the VM and apply it to the UnRAID host (if you can ping from within your network) and also confirm the DNS settings between VM & Host.

 

Yes, I can ping both unRAID and the VM from my laptop (which is where I'm trying to use Putty).

 

C:\Users\Chris>ping 192.168.20.150

Pinging 192.168.20.150 with 32 bytes of data:
Reply from 192.168.20.150: bytes=32 time=28ms TTL=64
Reply from 192.168.20.150: bytes=32 time=9ms TTL=64
Reply from 192.168.20.150: bytes=32 time=14ms TTL=64
Reply from 192.168.20.150: bytes=32 time=14ms TTL=64

Ping statistics for 192.168.20.150:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 28ms, Average = 16ms

 

C:\Users\Chris>ping 192.168.20.150

Pinging 192.168.20.150 with 32 bytes of data:
Reply from 192.168.20.150: bytes=32 time=28ms TTL=64
Reply from 192.168.20.150: bytes=32 time=9ms TTL=64
Reply from 192.168.20.150: bytes=32 time=14ms TTL=64
Reply from 192.168.20.150: bytes=32 time=14ms TTL=64

Ping statistics for 192.168.20.150:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 28ms, Average = 16ms

 

I don't see where the Gateway is shown in the VM, so I can't confirm what it's using for a Gateway.  I don't see it in the ip addr readout.  Is there another command to get the Gateway info from the VM?

Okay, so the fact you can ping around inside your network tells you it's definitely the gateway issue.

 

I don't know how to confirm the gateway on the ArchVM, however you can open a Command Prompt on your Windows machine (assuming that is where you are running Putty from) and type ipconfig /all. It is going to give you the default gateway and DNS servers your PC is using, which you should be able to add to UnRAID network via GUI (or cfg file if needed).

 

I haven't seen the issue you report of not being able to modify network settings. You should be able to update it, Apply, then done. Worst case scenario is manually editing the network.cfg as you mention, but I don't see why it wouldn't stick. Try manually updating the network.cfg file, reboot and see what results you get. The GUI issue may be something unrelated, but at least if you can get to the internet your primary issue is resolved.

  • Author

hmmm...

 

ipconfig /all from a cmd prompt on my laptop provides this...

 

Default Gateway . . . . . . . . . : 192.168.20.1

DHCP Server . . . . . . . . . . . : 192.168.20.1

 

Do, I stopped SAB and SB in the VM, shut down the vm and tried to save this as the Gateway in the GUI settings again.  It acted the same (all grey, never looked to have completed), but when I navigated away, then came back, it now shows this as the gateway in the settings.  Progress.

 

I tried to wget, but it still fails :(

 

Now, it gets strange again.  I changed it to the IP of my modem (192.168.1.254), and it acts the same, but if I browse away and back, the Gateway is blank.  It's as if it just won't accept 1.254 as the Gateway address.  I can't imagine why that would be, but I'm ready to part out this machine and stop messing with Linux :(

  • Author

I figured I'd try turning off the bridge, and see if that helped.  When I did that, I also changed the Gateway back to 1.254, and when I hit apply, it stayed grey, but now I can't navigate the GUI at all.  it's as if the server is frozen now.

 

Yep, frozen.  I can't even connect with Putty.

 

I'm taking 2 steps back and no steps forward.

  • Author

Turning off the bridge, resulted in the whole system needing to be hard booted.  I booted into safe mode, and still have the same issues.  i did discover that changing "Enable STP:" from yes to no at least allows the settings page to come back to useful after apply, but I still cannot get 192.168.1.254 to save.  I can edit the network.cfg file, or put it into the settings box, but regardless, it will NOT save that as the gateway IP.  No idea why.

  • Author

if the gateway is blank, I get this when I ping...

 

root@media:~# ping 8.8.8.8

connect: Network is unreachable

 

If I enter 192.168.20.1, that also will not save (it's the IP of my router on this subnet)

 

if I enter 192.168.10.1, that will save just fine, and when I ping, I get no response at all.  I have to ctl-c to get the window to do anything.

 

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

^C

--- 8.8.8.8 ping statistics ---

9 packets transmitted, 0 received, 100% packet loss, time 8003ms

 

weird, right?

If your IP address is 192.168.20.150 and subnet is /24 (or 255.255.255.0) then 192.168.20.1 would be the correct gateway, not 10.1. Your computer needs to understand how to get off of it's specific network, so 20.1 is the only address that makes sense.

 

Once you've done that try and ping 192.168.20.1, which should work. Then try and ping 192.168.10.1. If that works then you are successfully moving from your subnet to your modem. If you can do that, you should hopefully be able to ping 8.8.8.8.

 

Confirm this, and then you need to work on DNS. You can likely set 192.168.20.1 for DNS as well as it should be able to route requests outside of your network.

 

This should work regardless of whether you are using the bridge or not - it's just a different interface (either eth0 or br0).

  • Author

I know, but 192.168.20.1 will not save. I've tried a dozen times, including editing the cfg file directly, turning off the bridge, rebooting, and every combination I could think of.  Unraid will not save that, nor 192.168.1.254.  Either address results in the gateway box being blank next time I enter the GUI.

 

I'm thinking I may have to downgrade to beta 4

  • Author

Run check disk on the flash in a Mac or PC.

 

I assume I cannot pull the drive while unRAID is running, so it's going to be a while before I can do this.  Family is watching TV on the drive right now.

  • 4 weeks later...
  • Author

I finally circled back to this issue, and still can't ping anything useful.  Here is where I am right now.

 

Enable bonding:        No

 

Bonding mode:       

 

Setup bridge:        Yes

 

Bridge name:        br0

 

Enable STP:        No

 

Obtain IP Address Automatically:        No

 

IP Address:        192.168.20.150

 

Netmask:        255.255.255.0

 

Gateway:        192.168.20.1

 

Obtain DNS Server Address Automatically:        No

 

DNS Server 1:        192.168.20.1  (also tried 192.168.1.254 - the address of my router)

 

DNS Server 2:        200.23.242.155

 

DNS Server 3:        200.23.242.161

 

I cannot ping 192.168.20.1, and wget still fails.  I had bonding enabled, that didn't work either.  I'm not sure what else can be going wrong here.  I can wet from my archVM just fine, and can access internet from my windowsVM just fine.  it just seems to be an issue from inside putty connected to unRAID.

 

ideas?

I've had this problem too.  I had a static ip in the router for the server and I manually setup the ip in unraid.  I was testing different network settings and bonding and had a situation like you have.  To fix it I set unraid to automatically obtain ip address.  Also make sure you're using the correct mac of the bridge in your router and not one of the network cards. 

 

Right now I have no bonding since I disabled a nic anyway, bridge yes and automatic yes.

  • Author

You are officially my new hero!!!

 

All is working again; thank you!

 

I left bonding enabled, but updated my router with the mac of the bridge (it still had the MAC of one of the cards)

 

I changed it to automatically obtain IP address and also the DNS.

 

I rebooted, pinged 8.8.8.8 and it worked.  I then tried a wget, and it also worked.

 

thank you again!

 

Now, to try to 'fix' the remaining half-dozen niggling issues I'm having with my setup :)

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.