You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a service that we'd like to expose over https, we have an external marathon-lb set up (using DCOS), and we have an app which speaks https running inside the cluster (which needs to be exposed).
The service ports are mapped as follows:
80 --> 10080
443 --> 10443
We can see our service (called apiv01) on http:
$ curl http://marathon-lb.marathon.mesos:9091 -H "X-Marathon-App-Id: /apiv01"
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>
<hr><center>nginx/1.9.3</center>
</body>
</html>
$ curl https://marathon-lb.marathon.mesos:443 -H "X-Marathon-App-Id: /apiv01" -k
<html><body><h1>503 Service Unavailable</h1>
No server is available to handle this request.
</body></html>
finally, hitting the service directly works perfectly:
$ curl https://10.0.0.9:19920 -k
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
body {
width: 35em;
margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif;
}
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
The text was updated successfully, but these errors were encountered:
Hi All,
We have a service that we'd like to expose over https, we have an external marathon-lb set up (using DCOS), and we have an app which speaks https running inside the cluster (which needs to be exposed).
The service ports are mapped as follows:
We can see our service (called
apiv01
) on http:Trying the same w/ https fails
Trying to resolve the service port directly:
we get an 'unknown protocol' error:
additionally:
finally, hitting the service directly works perfectly:
The text was updated successfully, but these errors were encountered: