d2iq-archive / letsencrypt-dcos

Let's Encrypt DC/OS!
38 stars 27 forks source link

certbot not working anymore #13

Closed bert2002 closed 7 years ago

bert2002 commented 7 years ago

Hi, we have 1.0.3 running and it seems that the certbot is not working anymore. It used to work before and I dont know since when this state is. The only thing that I can see in the log file is:

root@b764ac84fdd9:/var/log/letsencrypt# tailf letsencrypt.log
2017-05-19 09:43:38,992:DEBUG:certbot.plugins.selection:Requested authenticator standalone and installer None
2017-05-19 09:43:39,036:DEBUG:certbot.plugins.selection:Single candidate plugin: * standalone
Description: Automatically use a temporary webserver
Interfaces: IAuthenticator, IPlugin
Entry point: standalone = certbot.plugins.standalone:Authenticator
Initialized: <certbot.plugins.standalone.Authenticator object at 0x7eff90068f50>
Prep: True
2017-05-19 09:43:39,036:DEBUG:certbot.plugins.selection:Selected authenticator <certbot.plugins.standalone.Authenticator object at 0x7eff90068f50> and installer None
2017-05-19 09:43:40,153:DEBUG:root:Sending GET request to https://acme-v01.api.letsencrypt.org/directory. args: (), kwargs: {}
2017-05-19 09:43:40,157:INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org

In DCOS I can see that it installed all the packages, but no more logs and then the container gets destroyed.

Configuration:

{
  "id": "/letsencrypt-dcos",
  "cpus": 0.05,
  "mem": 512,
  "instances": 1,
  "container": {
    "type": "DOCKER",
    "volumes": [
      {
        "containerPath": "/etc/letsencrypt",
        "hostPath": "data",
        "mode": "RW"
      },
      {
        "containerPath": "data",
        "mode": "RW",
        "persistent": {
          "size": 500
        }
      }
    ],
    "docker": {
      "image": "mesosphere/letsencrypt-dcos:v1.0.3",
      "network": "BRIDGE",
      "portMappings": [
        {
          "containerPort": 80,
          "servicePort": 10001,
          "protocol": "tcp"
        }
      ]
    }
  },
  "env": {
    "MARATHON_LB_ID": "marathon-lb",
    "MARATHON_URL": "http://marathon.mesos:8080",
    "LETSENCRYPT_EMAIL": "my@email.com"
  },
  "labels": {
    "HAPROXY_0_VHOST": "real-host-in-marathon-lb.example.org",
    "HAPROXY_GROUP": "external",
    "HAPROXY_0_PATH": "/.well-known/acme-challenge"
  },
  "backoffSeconds": 5,
  "upgradeStrategy": {
    "minimumHealthCapacity": 0.5,
    "maximumOverCapacity": 0
  }
}

Any idea or hint where I could keep diggin?

Thanks

bert

bert2002 commented 7 years ago

not sure why or what happened, but when I forcePullImage and download the docker new. Its working again.