creating exit server with letsencrypt fails to create & enable systemd service
bpmct opened this issue · comments
Expected Behaviour
The exit server creates a systemd service & enables it for inlets-pro with the LetsEncrypt configuration
Current Behaviour
No systemd service is created and inlets-pro has to be started manually
root@exciting-montalcini6:/var/log# sudo systemctl status inlets-pro
Unit inlets-pro.service could not be found.
root@exciting-montalcini6:/var/log# sudo journalctl -u inlets-pro
-- Logs begin at Mon 2021-07-26 11:23:08 UTC, end at Mon 2021-07-26 12:17:05 UTC. --
-- No entries --Possible Solution
@alexellis suggested it was an issue with the https service not being included:
Line 568 in ed0bcc7
Context
Following this guide: https://docs.inlets.dev/#/tools/inletsctl?id=create-a-https-tunnel-with-a-custom-domain
Your Environment
inlets-pro: Version: 0.8.6 - 18d8e239f940d8694532e332867c25f823439cc6
inletsctl: Version: 0.8.10
Git Commit: ed0bcc767eb9357bef75062dee746684b97eb0bf-
Cloud provider and region being used: DigitalOcean and Vultr
-
Operating System and version (e.g. Linux, Windows, MacOS):
uname -a
Darwin bens-macbook 20.4.0 Darwin Kernel Version 20.4.0: Fri Mar 5 01:14:14 PST 2021; root:xnu-7195.101.1~3/RELEASE_X86_64 x86_64- Link to your project or a code example to reproduce issue:
inletsctl create --provider digitalocean \
--access-token **** \
--region ewr \
--letsencrypt-domain dev.bpmct.net \
--letsencrypt-email **** \
--letsencrypt-issuer prod
Sorry for the inconvenience and thank you for flagging this.
I've added the artifact manually to the latest inlets pro release, and I'll be updating the CI for it so that it gets added to future releases properly