When inlets-pro got its own Let's Encrypt features, it meant that we could set up a VM with a HTTPS certificate in a very short period of time. That process to setup the VM is still manual, as documented here
Expected Behaviour
Accept the flags from inlets pro http server and make them available for a HTTPS server created with inletsctl:
Consider updating the cloud-provision package and inletsctl itself. A new systemd unit file may also be required, to inject the new variables into the unit file.
When inlets-pro got its own Let's Encrypt features, it meant that we could set up a VM with a HTTPS certificate in a very short period of time. That process to setup the VM is still manual, as documented here
Expected Behaviour
Accept the flags from
inlets pro http server
and make them available for a HTTPS server created with inletsctl:Current Behaviour
Only creates TCP servers today.
Possible Solution
Consider updating the cloud-provision package and inletsctl itself. A new systemd unit file may also be required, to inject the new variables into the unit file.