Scheduled renewal date later than expiration date for existing certificates

[lgleim]

When i upgrade the rancher-letsencrypt node and the certificate already exists, I get the following behavior:

31.1.2017 09:42:17level=info msg="Starting Let's Encrypt Certificate Manager v0.4.0 3c41d73"
31.1.2017 09:42:17level=info msg="Generating private key (P384) for user@domain."
31.1.2017 09:42:18level=info msg="Creating Let's Encrypt account for user@domain"
31.1.2017 09:42:18level=info msg="Using Let's Encrypt Production API"
31.1.2017 09:42:18level=info msg="Found locally stored certificate 'domain'"
31.1.2017 09:42:18level=info msg="Found existing certificate 'domain' in Rancher"
31.1.2017 09:42:18level=info msg="Managing renewal of certificate 'domain'"
31.1.2017 09:42:18level=info msg="Certificate renewal scheduled for 2017/03/19 21:00 UTC"

This looks fine, however my certificate is actually expiring on 2017/03/10. Is this a bug or wanted behavior? I definitely do not think it's a great UX...

[lgleim]

Nevermind. Misconfigured host binding.

[N1v0k]

I have the same issue (#102) can you tell me what configuration was wrong?