Unable to connect to: images.linuxcontainers.org:443

1

Would really like to get a look at incus but really can’t get past the 1st hurdle. Following a getting started tutorial I’m right at the begging and when I try “incus launch images:ubuntu/22.04 first” I get the error message quoted in the heading. I’ve searched the forum for it but could not find any reference. Googling implies that https://images.linuxcontainers.org might not be still supported. Further googling tells me that
https://us.lxd.images.canonical.com (us and uk) might be available.

I’m sure this is a very easy thing to fix as I assume there are many, many people that have progressed past this point. Can anyone help me.

The system is Debiam 11 (bullseye)
Thank You

2

Maybe you can use your browser or curl command to test the https conn to images.linuxcontainers.org at first. Then you may need an available mirror repo instead of the official one.

3

Well, I can certainly pull up the website in a browser, if that’s what you mean ??

4

Hi @RogerTunnicliffe,
Can you share the output of the command? incus remote ls and have you ever tested remote end with that command.
nc -zv images.linuxcontainers.org 80 or 443
Regards.

5

I’ll do that 1st thing tomorrow morning.
Thankyou

6

incus remote ls

[sudo] password for roger:
±----------------±----------------------------------------------------------±--------------±------------±-------±-------±-------+
| NAME | URL | PROTOCOL | AUTH TYPE | PUBLIC | STATIC | GLOBAL |
±----------------±----------------------------------------------------------±--------------±------------±-------±-------±-------+
| images | https://images.linuxcontainers.org | simplestreams | none | YES | NO | NO |
±----------------±----------------------------------------------------------±--------------±------------±-------±-------±-------+
| local (current) | unix:// | incus | file access | NO | YES | NO |
±----------------±----------------------------------------------------------±--------------±------------±-------±-------±-------+
| roger | https://us.lxd.images.canonical.com/streams/v1/index.json | simplestreams | none | YES | NO | NO |
±----------------±----------------------------------------------------------±--------------±------------±-------±-------±-------+

nc -zv images.linuxcontainers.org 80 or 443

images.linuxcontainers.org [45.45.148.8] 80 (http) open
invalid port or

7

Hi,
Can you try with, nc -zv images.linuxcontainers.org 443, you should specify just one port at a time.
Regards.

8

Both ports report as open

[45.45.148.8] 80 (http) open
[45.45.148.8] 443 (http) open

9

Everything looks good, so what is the output of the following command.
incus launch images:debian/12/cloud test
Regards.

10

Error: Failed instance creation: Failed getting remote image info: Failed getting image: Failed parsing stream: Get ~s://images.linuxcontainers.org/streams/v1/index.json": Unable to

connect to: :443~images.linuxcontainers.org ([dial tcp [2602:fc62:a:1::8]:443: i/o timeout])

Strangely the forum thinks I’m spamming when I paste a URL. (https becomes ~s)

11

Strange, here is my simple incus remote ls output.

+-----------------+------------------------------------+---------------+-------------+--------+--------+--------+
|      NAME       |                URL                 |   PROTOCOL    |  AUTH TYPE  | PUBLIC | STATIC | GLOBAL |
+-----------------+------------------------------------+---------------+-------------+--------+--------+--------+
| images          | https://images.linuxcontainers.org | simplestreams | none        | YES    | NO     | NO     |
+-----------------+------------------------------------+---------------+-------------+--------+--------+--------+
| local (current) | unix://                            | incus         | file access | NO     | YES    | NO     |
+-----------------+------------------------------------+---------------+-------------+--------+--------+--------+

What is your host operating system and make sure you dont use any firewall, even check with the curl https://images.linuxcontainers.org command to communicate to the destination repo.
Regards.

12

My operating system is Debian 11 (bullseye)
The result of curl ~://images.linuxcontainers.org is a html document that’s probably too long to post here (unless you are looking for something particular in it) but starts with

DOCTYPE html>
html lang=“en”>
head>
meta charset=“utf-8”/>
meta name=“viewport” content=“width=device-width, initial-scale=1.0”/>
link rel=“canonical” href=“https://images.linuxcontainers.org”/>
link rel=“icon” href=“~://linuxcontainers.org/static/img/favicon.ico”/>
title>Linux Containers - Image server

The firewall for Debian 11 I believe is iptables but I have never touched it since the install but it shows the following with --list

sudo iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp – anywhere anywhere multiport dports 4000,mdns
ACCEPT tcp – anywhere anywhere multiport dports 4000
ACCEPT udp – anywhere anywhere multiport dports mdns

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

13

This is something related to networking. Probably your own networking.

While earlier you were trying to connect through IPv4, here Incus is trying to connect through IPv6. It should work with IPv6, unless your router does not support it.

Test the IPv6 by visiting https://test-ipv6.com/

14

I pretty sure I have never setup IPv6 but the router appears to be able.
You are saying that Incus is “exclusively” IPv6 or is there a parameter somewhere to direct it to use IPv4. Either way I can set my machine to also use IPv6 so will do that 1st thing tomorrow.
Fingers crossed.
Cheers
Roger

15

Your Linux distribution supports IPv6. I think all mainstream Linux distributions are IPv6-ready.

The apps on your Linux distribution will use what is presented to them as available. Therefore, there’s no setting individually to Incus. Perform the test tomorrow
and if IPv6 is not fully working on your computer, you can disable it in your Linux distribution.

16

Sadly, still the same errors

eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.4 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::47a5:45f9:9a65:6ae0 prefixlen 64 scopeid 0x20
ether 00:23:24:b0:c1:cc txqueuelen 1000 (Ethernet)
RX packets 9281 bytes 11087890 (10.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5790 bytes 733179 (715.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xdf000000-df020000

incusbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 10.220.113.1 netmask 255.255.255.0 broadcast 0.0.0.0
inet6 fd42:1757:6f71:6218::1 prefixlen 64 scopeid 0x0
ether 00:16:3e:c5:dd:19 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

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 400 bytes 33139 (32.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 400 bytes 33139 (32.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

PING ~images.linuxcontainers.org (45.45.148.8) 56(84) bytes of data.
64 bytes from ~images.linuxcontainers.org (45.45.148.8): icmp_seq=1 ttl=51 time=254 ms
64 bytes from ~images.linuxcontainers.org (45.45.148.8): icmp_seq=2 ttl=51 time=253 ms
64 bytes from ~images.linuxcontainers.org (45.45.148.8): icmp_seq=3 ttl=51 time=252 ms
64 bytes from ~images.linuxcontainers.org (45.45.148.8): icmp_seq=4 ttl=51 time=252 ms

17

Can you show:

  • ip -4 route show
  • ip -6 route show
  • incus config show
  • incus image info images:debian/12/cloud
18

ip -4 route show
default via 192.168.0.1 dev eno1 proto static metric 100
10.220.113.0/24 dev incusbr0 proto kernel scope link src 10.220.113.1 linkdown
192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.4 metric 100

ip -6 route show
::1 dev lo proto kernel metric 256 pref medium
fd42:1757:6f71:6218::/64 dev incusbr0 proto kernel metric 256 linkdown pref medium
fe80::/64 dev eno1 proto kernel metric 100 pref medium
default via fe80::1af1:45ff:feb0:338 dev eno1 proto ra metric 100 pref low

incus config show
config:
core.https_address: :8443

roger@UPSTAIRS-LENOVO:~$ incus image info:debian/12/cloud
Error: unknown command “info:debian/12/cloud” for “incus image”

incus image info debian/12/cloud
Error: Image not found

19

Right, so you do have a default gateway for IPv6 on your system which if you don’t actually have IPv6 working on your network could probably be causing some issues.

Can you show ip -6 r get 2602:fc62:a:1::8 ?

20

The last few lines of my reply are the most telling (Can’t ping Google)

ip -6 r get 2602:fc62:a:1::8

2602:fc62:a:1::8 from :: via fe80::1af1:45ff:feb0:338 dev eno1 proto ra src fd42:1757:6f71:6218::1 metric 100 pref low

cat /sys/module/ipv6/parameters/disable
0

ip -6 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 fe80::47a5:45f9:9a65:6ae0/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: incusbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 state DOWN qlen 1000
inet6 fd42:1757:6f71:6218::1/64 scope global
valid_lft forever preferred_lft forever

netstat -tunlp| grep “tcp6”
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp6 0 0 :::8443 :::* LISTEN -
tcp6 0 0 :::4000 :::* LISTEN -
tcp6 0 0 :::1716 :::* LISTEN 1590/kdeconnectd
tcp6 0 0 fd42:1757:6f71:6218::53 :::* LISTEN -
tcp6 0 0 ::1:631 :::* LISTEN -
tcp6 0 0 ::1:7001 :::* LISTEN 1856/nxnode.bin

ping -6 localhost
PING localhost(localhost (::1)) 56 data bytes
64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.042 ms
64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.086 ms

ping -6 2001:4860:4860::8888
PING 2001:4860:4860::8888(2001:4860:4860::8888) 56 data bytes
— 2001:4860:4860::8888 ping statistics —
22 packets transmitted, 0 received, 100% packet loss, time 21483ms

ping -6 google.com
PING google.com(mel05s02-in-x0e.1e100.net (2404:6800:4015:803::200e)) 56 data bytes
6 packets transmitted, 0 received, 100% packet loss, time 5104ms