Test with LXD 2.0 about lxd-webgui HOT 3 CLOSED

No issues till now. Yay.

from lxd-webgui.

I may be having an lxd 2.0 issue. Not totally sure:

Apr 23 08:09:09 arch-anywhere lxd[29972]: 2016/04/23 08:09:09 http: TLS handshake error from 127.0.0.1:51054: EOF
Apr 23 08:09:12 arch-anywhere lxd[29972]: 2016/04/23 08:09:12 http: TLS handshake error from 127.0.0.1:51074: EOF
Apr 23 08:09:15 arch-anywhere lxd[29972]: 2016/04/23 08:09:15 http: TLS handshake error from 127.0.0.1:51082: EOF
Apr 23 08:09:18 arch-anywhere lxd[29972]: 2016/04/23 08:09:18 http: TLS handshake error from 127.0.0.1:51090: EOF
Apr 23 08:09:21 arch-anywhere lxd[29972]: 2016/04/23 08:09:21 http: TLS handshake error from 127.0.0.1:51098: EOF
Apr 23 08:09:21 arch-anywhere lxd[29972]: 2016/04/23 08:09:21 http: TLS handshake error from 127.0.0.1:51110: EOF
Apr 23 08:09:24 arch-anywhere lxd[29972]: 2016/04/23 08:09:24 http: TLS handshake error from 127.0.0.1:51124: EOF
Apr 23 08:09:27 arch-anywhere lxd[29972]: 2016/04/23 08:09:27 http: TLS handshake error from 127.0.0.1:51132: EOF
Apr 23 08:09:30 arch-anywhere lxd[29972]: 2016/04/23 08:09:30 http: TLS handshake error from 127.0.0.1:51140: EOF
Apr 23 08:09:33 arch-anywhere lxd[29972]: 2016/04/23 08:09:33 http: TLS handshake error from 127.0.0.1:51148: EOF

(from systemctl status lxd)

the TLS does seem to work at some point though:

from lxd-webgui.

Yes i have the same error.

But i think it's because lxd-webgui tries to access the LXD rest service via ajax, but the user did not yet accept the (not really valid) certificate of the rest service. I'll research some more.

from lxd-webgui.