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
{{ message }}
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
I have a setup where the marathon-lb is deployed at http://marathon.mesos:8080 while the public applications are deployed at http://user-marathon.marathon.l4lb.thisdcos.directory:5555 i.e. marathon-user.
letsencrypt-dcos needs to deployed to public to pass the /.well-known/acme-challenge challenge but it is unable to curl http://marathon.mesos:8080 from inside of marathon-user.
here is what i get in the logs (when i run it inside marathon-user)
stdout
...
Registered docker executor on 10.5.0.4
Starting task utilities_letsencrypt-dcos.e4efb618-e8ad-11e6-a7d4-70b3d5800004
stderr
#
Traceback (most recent call last):
File "<string>", line 1, in <module>
KeyError: 'app'
The text was updated successfully, but these errors were encountered:
I have a setup where the
marathon-lb
is deployed athttp://marathon.mesos:8080
while the public applications are deployed athttp://user-marathon.marathon.l4lb.thisdcos.directory:5555
i.e. marathon-user.letsencrypt-dcos needs to deployed to public to pass the
/.well-known/acme-challenge
challenge but it is unable to curlhttp://marathon.mesos:8080
from inside of marathon-user.here is what i get in the logs (when i run it inside marathon-user)
stdout
stderr
The text was updated successfully, but these errors were encountered: