add HTTPS support and let'sencrypt cert generation via duckdns #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is still a WIP, i've opened the PR to have some suggestion (sorry for the cascading-promises in lecerts i was just too noob to implement
await
in coffeescript)@BoLaMN can you suggest a way to intercept and send our IP to a DNS query via the module you already made?
actual usage:
create and store in key.key and cert.cert file an SSL valid certificate (PC must be online)
--acsurl="https://xxxx.duckdns.org" --certonly --duckdnstoken="xxxx"
than normal start with an server HTTPS server using the stored key.key and cert.cert
--acsurl="https://xxxx.duckdns.org" --https