inlets/inlets-pro

[DigitalOcean] Unable to start v0.8.0 inlets server: move 0.8.0 tag

gabemeola opened this issue · 5 comments

gabemeola commented

The inlet server never starts up while provisioning using: inletsctl create or inlets-operator using version 0.8.0.

  1. cloud-provision downloads inlets-pro.service from gitlab artifact (https://github.com/inlets/cloud-provision/blob/master/provision/userdata.go)
  2. inlets-pro.service is using same content from v0.7.2. This breaks startup because --common-name is changed to --tls-san. See: https://github.com/inlets/inlets-pro/blob/0.8.0/artifacts/inlets-pro.service & https://raw.githubusercontent.com/inlets/inlets-pro/0.8.0/artifacts/inlets-pro.service

Possibly, cloud-provision could ping and wait for server to come online then surface error up through inletsctl and inlets-operator to make troubleshooting easier.

alexellis commented

I'm sorry to hear that you encountered an issue.

What project were you using when you saw the error and which version did you try?

How can I reproduce it the way you did it? (Exact instructions)

alexellis commented

I am seeing the flags updated in the Git repo - from 3 days ago for inletsctl which pins the version to 0.7.2. I made the change to prevent any issues with 0.8.0 vs 0.7.x.

cbf80ff

The inletsctl release is from 4 days ago, and was set to pre-release, so if you download that, it should fix the issue you're seeing. The operator had a similar release too.

https://github.com/inlets/inletsctl/releases/tag/0.8.1

Next, I'll create a new release of inletsctl pointing at 0.8.0, but first confirm that the latest inletsctl (0.8.1) works as expected.

Alex

alexellis commented

This should fix inletsctl for you - https://github.com/inlets/inletsctl/releases/tag/0.8.2

inlets-operator is just being validated now.

  • ❤️1
gabemeola commented

Thanks for the quick fix! For reference I was following this guide https://docs.inlets.dev/#/get-started/quickstart-caddy