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 --
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
Expected Behaviour
The exit server creates a systemd service & enables it for
inlets-pro
with the LetsEncrypt configurationCurrent Behaviour
No systemd service is created and inlets-pro has to be started manually
Possible Solution
@alexellis suggested it was an issue with the https service not being included: https://github.com/inlets/inletsctl/blob/ed0bcc767eb9357bef75062dee746684b97eb0bf/cmd/create.go#L568
Context
Following this guide: https://docs.inlets.dev/#/tools/inletsctl?id=create-a-https-tunnel-with-a-custom-domain
Your Environment
Cloud provider and region being used: DigitalOcean and Vultr
Operating System and version (e.g. Linux, Windows, MacOS):
uname -a