http://<master-ip>:5050 and the Marathon console athttp://<master-ip>:8080 (where <master-ip> is any of the master IP addresses)."Hi.
Is marathon running on every master and in ha-mode? The way marathon works is that if you hit the non-leader, it will proxy the requests to the leading instance. You should be able to see this redirect on the non-leaders in the marathon logs, like this:
INFO Proxying request to GET http://<leader>:8080/api/v2.0/spec?type=docker&recursive=true from <non-leader>:8080 (mesosphere.marathon.api.JavaUrlConnectionRequestForwarder$:qtp49485418-64408)
Hope that helps,
Jeremy
Hi
How your certificates looks like? Are they trusted by marathon and has proper CN values? Maybe proxy fails becouse host can't validate leaders certificate. More info should be in logs. Try with --leader_proxy_ssl_ignore_hostname.
Best
Tomek
--
To unsubscribe from this group and stop receiving emails from it, send an email to marathon-framework+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to marathon-framew...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "marathon-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to marathon-framew...@googlegroups.com.
My bad, --leader_proxy_ssl_ignore_hostname was introduced in Marathon 1.2.0-RC1. Glad you solve your problem.
pon., 25.07.2016 o 19:27 użytkownik Douglas Nelson <itsb...@gmail.com> napisał:
I think the flag to ignore hostname might be having issues? In the logs I get the following message:
Jul 25 17:24:06 ip marathon[32629]: [scallop] Error: Unknown option 'leader_proxy_ssl_ignore_hostname'
And when I set that flag the web UI shows nothing for any node I set it with.
On Friday, July 22, 2016 at 9:54:18 AM UTC-6, Tomek Janiszewski wrote:Hi
How your certificates looks like? Are they trusted by marathon and has proper CN values? Maybe proxy fails becouse host can't validate leaders certificate. More info should be in logs. Try with --leader_proxy_ssl_ignore_hostname.
Best
Tomek
pt., 22.07.2016, 17:40 użytkownik Douglas Nelson <itsb...@gmail.com> napisał:
I still haven't found a solution. Has anyone else run into this issue? According to https://open.mesosphere.com/getting-started/install/ the UI should be accessible at any of the master IP addresses:
"If the packages were installed and configured correctly, you should be able to access the Mesos console athttp://<master-ip>:5050and the Marathon console athttp://<master-ip>:8080(where<master-ip>is any of the master IP addresses)."
Is that not the case with https? Or could I be missing a necessary config flag? I'm currently running mesos 1.0.0 and marathon 1.1.2. Let me know if any other info would be helpful and I'll pass it your way. :)--
On Tuesday, July 19, 2016 at 1:43:26 PM UTC-6, Douglas Nelson wrote:I don't remember running into this issue before. Maybe it's related to the SSL/authorization I've set up?I have SSL/authorization for mesos and marathon running on three different nodes. Marathon successfully registers with mesos and the web UI for mesos redirects if I'm not hitting the leader's IP. I can only hit the marathon UI at the leader's IP. The other two IPs display a blank screen after I enter in the username/pass.Any help would be appreciated. Thanks!
You received this message because you are subscribed to the Google Groups "marathon-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to marathon-framework+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "marathon-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to marathon-framework+unsub...@googlegroups.com.