search

inlets / inletsctl

Create inlets servers on the top cloud platforms
https://docs.inlets.dev/
MIT License
457 stars 63 forks source link

Civo: update Ubuntu version due to deprecation of 16.04 (bionic) #99

Closed dirien closed 3 years ago

dirien commented 3 years ago

Description

Update Ubuntu images to 18.04 for the Civo provider

How Has This Been Tested?

Create Inlets exit node

go run main.go create -p civo --access-token $CIVO_TOKEN
Using provider: civo
Requesting host: trusting-bose1 in , from civo
2021/07/07 06:02:22 Provisioning host with Civo
e9ac240f-fef1-4aaf-b622-5490dab688b7
Instance ID: c4732871-3b1d-4357-a1df-b6f826c054c7
Host: c4732871-3b1d-4357-a1df-b6f826c054c7, status: 
[1/500] Host: c4732871-3b1d-4357-a1df-b6f826c054c7, status: building
[16/500] Host: c4732871-3b1d-4357-a1df-b6f826c054c7, status: active
inlets PRO TCP (0.8.3) server summary:
  IP: 
  Auth-token: U2NsCrrNVWQ5uSx5d9NhebOPcXYsGZAcMkRboOsov61w1CJDCOQ7qTaGVdp8OHm8

How are existing users impacted? What migration steps/scripts do we need?

none

Checklist:

I have:

dirien commented 3 years ago

@alexellis: Done

alexellis commented 3 years ago

CI is now running, please can you run an e2e test now with the license key that I sent you over Slack DM?

alexellis commented 3 years ago

You can bring in the new package now via go mod:

https://github.com/inlets/cloud-provision/releases/tag/0.3.1

dirien commented 3 years ago

During e2e tests i found out, that the IP adress for the certifiacte is not the same as the public ip from the server.

this could be due to a different egress router they use... 

  ~ inlets-pro tcp client --url "wss://74.220.16.178:8123" \
  --token "T3JN2qYveppvKKkEeAhx0IZmKuxIE9hFvERmf1OfjE4ctRNH5vDApK8G60ncmjVH" \
  --upstream $UPSTREAM \
  --ports $PORTS

image

dirien commented 3 years ago

Looks like we run into the know issue https://github.com/inlets/inletsctl/issues/78 thanks @jsiebens for the hint

dirien commented 3 years ago

fix from Civo was implemented.

➜  ~ inlets-pro tcp client --url "wss://74.220.19.102:8123" \
  --token "8EflECGMZEEmjKny2rh0OQteOoDt7wZp50woVR7kCGmkMS99BtD8NXQaHYFguCyb" \
  --upstream $UPSTREAM \
  --ports $PORTS
2021/07/07 14:38:35 Starting TCP client. Version 0.8.5 - 8db64ded51b1455cf4ad027c52bc9cfbeb55c4b3
2021/07/07 14:38:35 Licensed to: Free trial <contact@openfaas.com>, expires: 30 day(s)
2021/07/07 14:38:35 Upstream server: localhost, for ports: 8080
inlets-pro client. Copyright Alex Ellis, OpenFaaS Ltd 2020
INFO[2021/07/07 14:38:35] Connecting to proxy                           url="wss://74.220.19.102:8123/connect"
INFO[2021/07/07 14:38:35] Connection established.. OK.
alexellis commented 3 years ago

Approving the CI now. Did you connect a tunnel and test that it worked?

dirien commented 3 years ago

Yes, did start a nginx conainer locally:

➜  ~ curl 74.220.19.102:8080
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
alexellis commented 3 years ago

Thank you 👍