LXD Remote Add Hangs

OS & Version:

redacted@redacted:~$ cat /proc/version
Linux version 4.4.0-96-generic (buildd@lgw01-10) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017
redacted@redacted:~$ lxd --version
2.0.10
redacted@redacted:~$ lxc remote add redacted redacted --password=redacted --accept-certificate --debug
DBUG[10-17|15:26:01] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"api_extensions":["id_map"],"api_status":"stable","api_version":"1.0","auth":"untrusted","public":false}}

DBUG[10-17|15:26:01] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"api_extensions":["id_map"],"api_status":"stable","api_version":"1.0","auth":"untrusted","public":false}}

DBUG[10-17|15:26:01] &{sync Success %!s(int=200)  %!s(int=0)  {"api_extensions":["id_map"],"api_status":"stable","api_version":"1.0","auth":"untrusted","public":false}}
DBUG[10-17|15:26:01] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":{"api_extensions":["id_map"],"api_status":"stable","api_version":"1.0","auth":"untrusted","public":false}}

DBUG[10-17|15:26:01] &{sync Success %!s(int=200)  %!s(int=0)  {"api_extensions":["id_map"],"api_status":"stable","api_version":"1.0","auth":"untrusted","public":false}}
DBUG[10-17|15:26:01] POST {"password":"redacted","type":"client"}
 to https://redacted:8443/1.0/certificates
DBUG[10-17|15:26:02] Raw response: {"type":"sync","status":"Success","status_code":200,"operation":"","error_code":0,"error":"","metadata":null}

The communication is clearly happening. The trust certificate is also in the remote LXD server during execution, however this command just hangs here.

There are proxies in the environment, but the general domain is set to be ignored in both system and lxc config.

config:
  core.https_address: redacted:8443
  core.proxy_ignore_hosts: redacted-ip,redacted-hostname
  core.trust_password: true

Any thoughts?

Might be worth running under strace to see what’s going on.

My guess is that it’s getting stuck when doing the next API call. Could be some kind of MTU issue on the network (since the next packet to be received will be quite large).

Thank you for the response!
We have determined that it was an MTU issue on a switch in path. Networking is fun…