Unable to access update-master.ixsystems.com

[Adrian]

I recently switched ISP and have a new IP address in 81.187.179.*
FreeNAS is now unable to check for updates, timing out.
Example fetch (performed on a nearby FreeBSD machine).

Code:

[aw1@swelter /tmp]$ fetch -vvvv http://update-master.ixsystems.com/FreeNAS/FreeNAS-11-STABLE/LATEST
scheme:   "http"
user:	 ""
password: ""
host:	 "update-master.ixsystems.com"
port:	 "0"
document: "/FreeNAS/FreeNAS-11-STABLE/LATEST"
---> update-master.ixsystems.com:80
resolving server address: update-master.ixsystems.com:80
requesting http://update-master.ixsystems.com/FreeNAS/FreeNAS-11-STABLE/LATEST
>>> GET /FreeNAS/FreeNAS-11-STABLE/LATEST HTTP/1.1
>>> Host: update-master.ixsystems.com
>>> Accept: */*
>>> User-Agent: fetch libfetch/2.0
>>> Connection: close
>>>
fetch: transfer timed out

update-master is unpingable.

Code:

[aw1@swelter /tmp]$ ping update-master.ixsystems.com
PING update-master.freenas.org (64.71.187.3): 56 data bytes
^C
--- update-master.freenas.org ping statistics ---
39 packets transmitted, 0 packets received, 100.0% packet loss

Traceroute peters out here

Code:

 8  10ge3-2.core2.fmt2.he.net (184.105.222.142)  148.382 ms  192.448 ms  157.786 ms

I can check for updates at another site, different ISP with similar non-ping and traceroute.
My new ISP can also check for updates with similar non-ping and traceroute..

Looks like something, somewhere, does not like my IP address.
Would it be worth changing it, or would I do better to contact iXsystems or Hurricane Electric?

 

[BigDave]

can you ping an outside address like 8.8.8.8

 

[BigDave]

I tried to ping
64.71.187.3
and it says Request timed out.

The server might be down right now.

 

[KingJ]

It looks to be down from my end too. I can't ping update-master.ixsystems.com and my FreeNAS box can't load the mainfest from it either.

Code:

Update server could not be reached


Traceback
Traceback (most recent call last):
File "./freenasUI/system/views.py", line 1424, in update_check
train=updateobj.get_train(),
File "/usr/local/lib/freenasOS/Update.py", line 877, in CheckForUpdates
raise UpdateManifestNotFound("Manifest could not be found!")
freenasOS.Exceptions.UpdateManifestNotFound: Manifest could not be found!

Code:

Dec 15 23:21:56 hostname uwsgi: [freenasOS.Configuration:772] Unable to load http://update-master.ixsystems.com/FreeNAS/FreeNAS-11-STABLE/LATEST: timed out
Dec 15 23:21:56 hostname uwsgi: [freenasOS.Configuration:786] Unable to load ['http://update-master.ixsystems.com/FreeNAS/FreeNAS-11-STABLE/LATEST']: timed out
Dec 15 23:21:56 hostname uwsgi: [freenasOS.Update:874] Could not find latest manifest due to timed out

 

[Adrian]

Solved!:)
MTU size problem.:(
I had my firewall WAN port explicitly configured for a 1500 byte MTU, which was supported by my previous ISP.
Defaulting the size caused the firewall to negotiate a 1492 MTU size, and my FreeNAS box down here can now see the update.
Sorry about the noise, and my not knowing how to mark the thread solved.
I suspect that you can't normally ping or traceroute update-master.ixsystems.com.

 

[KingJ]

I'm still experiencing this. I can curl the URL (http://update-master.ixsystems.com/FreeNAS/FreeNAS-11-STABLE/LATEST) successfully from other machines in my network and from my FreeNAS box itself - it's just the updater that seems to have problems accessing it.

 

[KingJ]

I worked around this by manually upgrading, however I have instead hit the FreeNAS 11.1 hang issue and have downgraded back to 11.0-U4 for now.