This is a common problem when working with EC2 or other cloud providers, where the machines have both external and internal IP. Mesos reports an internal IP interface in the user interface, so if you use the web interface outside of EC2, the URLs will not work.
The current Mesos host and latest 0.15 graduate fix these issues by adding the -hostname command-line option to set the host name that receives the message in the user interface. If you are running <0.15, you can fix the problem by adding all the hosts in your Mesos cluster to / etc / hosts as follows:
<private ip> <public fqdn> <machine hostname>
eg:
10.98.58.170 ec2-54-224-191-136.compute-1.amazonaws.com ec2-54-224-191-136
source
share