It looks same as the problem I’ve had with NetworkManager which don’t allocate a DHCP ipv4 address.
Endeavour site cannot be reach without ipv4.
To see if you have an ipv4
$ ip a
Summary
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether ff:ff:ff:ff:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.19/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0
valid_lft 42750sec preferred_lft 42750sec
inet6 9999:999:9999:aaa:bbbb:cccc:dddd:eeee/64 scope global dynamic noprefixroute
valid_lft 86357sec preferred_lft 86357sec
inet6 ffff::999:9999:aaaa:bbbb/64 scope link noprefixroute
valid_lft forever preferred_lft forever
If you don’t have inet allocation like “inet 192.168.0.19/24”, that is the problem.
Just run in a terminal dhcpd, and then you’ve got an ipv4.
$ dhcpd
The workaround is here : [Workaround] How to fix connection bug within NetworkManager 1.22.2