Thanks Carlos. So, even after you compiled Mesos with SSL it still did not work correctly over HTTPS? For me, recompiling is not an option as this a part of an automated cluster provisioning and we rely on a common repository to get the binaries from.
From: Carlos Sanchez [mailto:[email protected]] Sent: Monday, October 19, 2015 12:26 PM To: [email protected] Subject: Re: How to enable SSL for Mesos and Marathon? Joris mentioned back in August Mesosphere currently doesn't build packages with ssl enabled. I managed to get SSL working, recompiling Mesos, although had issues with certificates that never got solved, see this thread https://mail-archives.apache.org/mod_mbox/mesos-user/201509.mbox/%3CCALHFn6O5_t60H=rhhd1knka0u08_z_5uqh5f20axceaszdp...@mail.gmail.com%3E On Mon, Oct 19, 2015 at 7:19 PM, Nikolay Borodachev <[email protected]<mailto:[email protected]>> wrote: Hello, I’ve tried to enable SSL for Mesos communication following instructions in this document: http://mesos.apache.org/documentation/latest/ssl/ I verified that all environment variables were set correctly after the processes had started. I also confirmed that Mesos was built with SSL support: $ ldd /usr/sbin/mesos-master|grep ssl libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f7258af8000) However traffic on port 5050 is still unencrypted and there no other port that Mesos master would listen to. I am using version 0.25.0 from http://repos.mesosphere.io/ubuntu What am I missing? Thank you Nikolay
