Lxc move error websocket: bad handshake

[TomvB (Tom)]

@tomp

I have at the moment is that LXD is trying to connect on all of the available IPs sequentially (which it does in some places, although I’m not certain this is one of them, although its a strong possibility given what we are seeing), and this can take time as some IPs are not listening (perhaps a firewall is blocking the request causing a timeout rather than connection refused). Previously it would have kept trying until it found the right one, but with the listener timeouts add…

If you have ipv6 addresses bound to the host lxd will try and use them. If the firewall is then dropping rathervthsn rejecting the request this could take longer than 10s and cause the web socket listeners to time out.

I was asking if you could setup some ipv6 reject rules to test that theory before we start thinking about a fix in Lxd. Does that make sense?

I understand. But it is hard for me to configure this test config right now.
Reminds me a bit of this: Lxc copy to internal IP instead of public IP