Thanks… but I actually have no plans to use Curl.
It was the only tool I had that I could test all the various connections with one common tool most folks have. To see what LXD servers I could or could not connect to. My core problem is I can connect to a single Public LDX rest server, But so far after hammering away for about a week now at finding out why I can't hit my local test LXD rest server? It's only my network and the port is open… but it keeps sending errors and alerts with the same calls to the public one that works. I have to assume both should responded the same way to the same calls. But one works the other not. -Kevin On May 22, 2015, at 9:51 PM, Janjaap Bos <janjaap...@gmail.com> wrote: > You should upgrade your local curl, so it uses TLS and not SSL which is no > longer secure, and therefore disabled at the server. I guess the images repo > still accepts SSL. > Op 23 mei 2015 02:14 schreef "Kevin LaTona" <li...@studiosola.com>: > > This past week or so I ran into an issue of not being able to connect a test > LXD rest server on my local network. > > I've tested this problem out from pretty much every angle I can think of. > > Every thing from fresh OS, server, SSL lib installs to upgrades of current > running apps on my machines. > > > Pretty much unless I am missing some small fundamental piece that is > preventing current shipping vivid server to allow connections to the LXD rest > server. > > My take is there is a bug . > > If this true, what is the best way to let the LXC team know about this to see > how to get to next step? > > > To sum it up I am able to connect to a public LXD rest server. > > # from vivid container --> public LXD server ( container > to public ) > curl -k https://images.linuxcontainers.org/1.0/images > # {"status": "Success", "metadata": ["/1.0/images/e7ae410ee8abeb6 > > > No matter how and from what angle I try connecting to a local test LXD rest > server it is having connections issues. > > # vivid container 10.0.3.5 --> 192.168.0.50:8443 ( container to host > machine ) > # this container can ping 192.168.0.50 > curl -k https://192.168.0.50:8443/1.0/images > # curl: (35) error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad > certificate > > > > # OS X term window --> vivid server (same 192.168.x.x network) > curl -k https://192.168.0.50:8443/1.0/images > # curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert > protocol version > > > > If any one has any ideas or suggestions please send them along. > > -Kevin > > > > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users