SOLVED After fresh install of 9.3- Nightlies, "Update server could not be reached" error

[Bobbyg387]

Hello, hopefully this is the right spot for this. I have recently wiped my system after I initially got this error. I later found out it seemed to be a nightlies issue and could be resolved by updating to the next one.

Well, that didn't work for me, so I wiped my HDD, wiped both usb drives, loaded the newest Nightlies onto the update stick and left the 16gb stick empty to be written by the new update.

Install goes smooth, but when I get into the GUI, I still can't access the update page. I get an error that says "Update server could not be reached".

Is this a network related issue? I have rolled back my router settings and reset DHCP and still nothing.

Right now I can see this in the console footer:

Feb 12 09:41:49 freenas ntpd_initres[8333]: host name not found: 0.freebsd.pool.ntp.org
Feb 12 09:41:49 freenas ntpd_initres[8333]: host name not found: 1.freebsd.pool.ntp.org
Feb 12 09:41:49 freenas ntpd_initres[8333]: host name not found: 2.freebsd.pool.ntp.org

 

[dlavigne]

First, unless you're testing a fix, you want to track STABLE, not NIGHTLIES.

Post the output of ifconfig.

 

[Bobbyg387]

Here is the output:

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLA
N_HWTSO>
ether 6c:0b:84:04:2a:40
inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
nd6 options=9<PERFORMNUD,IFDISABLED>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
nd6 options=9<PERFORMNUD,IFDISABLED>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

 

[Bobbyg387]

I also had the latest Stable, but was getting this error, so I switched to Nightlies. That could be part of my problem, but not sure. I thought a fresh install could solve this, but it appears to have not.

 

[dlavigne]

You have an IP address. Can you ping an Internet domain name?

 

[Bobbyg387]

ping: cannot resolve https://forums.freenas.org: Host name lookup failure

That's the error I'm getting when I try to ping this site.

 

[dlavigne]

ping: cannot resolve https://forums.freenas.org: Host name lookup failure

That's the error I'm getting when I try to ping this site.

Try pinging forums.freenas.org (without the http). If that fails, put 8.8.8.8 as Nameserver 1 in Network -> Global Configuration.

 

[Bobbyg387]

Excellent, thank you for your help! I know handling all the noob questions can be tough, but I know I certainly appreciate it!