Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

iocage fetch error: [Errno 65] No route to host

Joined
Sep 14, 2019
Messages
3
Thanks
0
#1
Hey there,

I recently installed freeNAS the first time - happy to be on board!

Sadly I'm encountering the first issue when I try to create a jail - iocage fetch return a "No route to host":

Code:
Traceback (most recent call last):
  File "/usr/local/bin/iocage", line 10, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/iocage_cli/fetch.py", line 127, in cli
    ioc.IOCage().fetch(**kwargs)
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/iocage.py", line 970, in fetch
    **kwargs).fetch_release()
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_fetch.py", line 228, in fetch_release
    eol = self.__fetch_eol_check__()
  File "/usr/local/lib/python3.6/site-packages/iocage_lib/ioc_fetch.py", line 113, in __fetch_eol_check__
    req = requests.get(_eol)
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 508, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 618, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/adapters.py", line 508, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='www.freebsd.org', port=443): Max retries exceeded with url: /security/unsupported.html (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x80ac85198>: Failed to establish a new connection: [Errno 65] No route to host',))


Also here is my ifconfig:

Code:
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 8c:ec:4b:57:fa:6d
        hwaddr 8c:ec:4b:57:fa:6d
        inet6 fe80::8eec:4bff:fe57:fa6d%re0 prefixlen 64 scopeid 0x1
        inet 192.168.178.41 netmask 0xffffff00 broadcast 192.168.178.255
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
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 0x2
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo


and my resolv.conf:

Code:
# Generated by resolvconf
search local fritz.box
nameserver 192.168.178.1
nameserver 8.8.8.8

Code:
# Generated by resolvconf

Somebody also encountered that problem? I already have created a Network Interface in the Web UI because it was not there.

Cheers,
Chris
nameserver 192.168.178.1
nameserver 8.8.8.8
 

dlavigne

Storage Engineering
Administrator
Moderator
iXsystems
Joined
May 24, 2011
Messages
11,637
Thanks
1,012
#2
The Realtek NIC may be the issue. Have you tried replacing it with a recommended Intel NIC?
 

Fredda

FreeNAS Experienced
Joined
Jul 9, 2019
Messages
114
Thanks
22
#3
Have you set a default route for your system?
What is the output of netstat -r?
 
Joined
Sep 14, 2019
Messages
3
Thanks
0
#4
Since my writing I tried nearly everything. Biggest things:

1. Reinstall FreeNAS
2. Changed whole computer to one that uses a INTEL Chipset NIC

All in all nothing helped. But nevertheless I found some workaround. Reading more of the error message (earlier errors that I didn't post) it seems that there is a problem with the https-connection.

So if I run iocage fetch --noverify fetching and downloading the desired versions worked like a charm.

It is just a workaround though so I would be very happy to solve this. Should I open a new Thread about it since no route to host is not really my problem here.
 

Fredda

FreeNAS Experienced
Joined
Jul 9, 2019
Messages
114
Thanks
22
#5
So if I run iocage fetch --noverify fetching and downloading the desired versions worked like a charm.
So there is a problem with the certificate verification. Do you have some kind of firewall/proxy involved with your setup, which
might mess with certificates? This is how the freebsd certificate looks for me:
Code:
openssl s_client -connect www.freebsd.org:443 < /dev/null |& openssl x509 -issuer -subject -fingerprint -dates -noout -in /dev/stdin
issuer= /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
subject= /CN=wfe0.nyi.freebsd.org
SHA1 Fingerprint=DF:DA:AA:E3:89:5E:CA:E6:FF:42:46:2F:9E:E4:74:E5:94:68:2D:2A
notBefore=Jul 31 20:20:15 2019 GMT
notAfter=Oct 29 20:20:15 2019 GMT
 
Joined
Sep 14, 2019
Messages
3
Thanks
0
#6
Not really - the only thing that is different is that I have a 4G connection to the internet. Here is the output of my certificate:

Code:
openssl s_client -connect www.freebsd.org:443 < /dev/null |& openssl x509 -issuer -subject -fingerprint -dates -noout -in /dev/stdin
issuer= /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
subject= /CN=wfe0.nyi.freebsd.org
SHA1 Fingerprint=DF:DA:AA:E3:89:5E:CA:E6:FF:42:46:2F:9E:E4:74:E5:94:68:2D:2A
notBefore=Jul 31 20:20:15 2019 GMT
notAfter=Oct 29 20:20:15 2019 GMT
 

Fredda

FreeNAS Experienced
Joined
Jul 9, 2019
Messages
114
Thanks
22
#7
Strange. So the certificate is the same. I don't see a reason, why it should work for me and not for you. Maybe a temporary failure?
 
Top