search

dkumor / acmewrapper

Automated wrapper to add let's encrypt support to go servers
MIT License
248 stars 13 forks source link

New Certificate isn't generated after domain change. #8

Closed chespinoza closed 8 years ago

chespinoza commented 8 years ago

How can I remove an existing certificate for a server?

I tested a server with one domain, and then I tried with another domain, but the old domain certificate is alive yet , are there a way to force a domain change? I did the change into the code but doesn't work.

ie: first run with: Domains: []string{"example.com","www.example.com"} then Domains: []string{"example2.com","www.example2.com"}

and the server remains showing the example.com domain certificate and doesn't generate a new certificate for the new domain.

chespinoza commented 8 years ago

Sorry, I just fix the problem simply deleting the key and cert (reg and pem) files and running again my app.

dkumor commented 8 years ago

This is a bug - acmewrapper only checks for existence of certificates on startup, but not the domain. I'll see if I can fix it some time today.

dkumor commented 8 years ago

@chespinoza Can you confirm that the issue is now fixed?

chespinoza commented 8 years ago

Ok let me check again, thanks

chespinoza commented 8 years ago

Confirmed! Thanks and sorry for the delay.

dkumor commented 8 years ago

:)