techize
September 26, 2023, 7:56am
1
Hi.
Trying to install on Ubuntu 20.04 (or 22.04) as a headless client. Before even getting to the stage where I can run the installer, I have trouble getting the package installed.
In my /etc/apt/sources.list.d/twingate.list I have the following
deb [trusted=yes] https://packages.twingate.com/apt/ /
Running apt update -yq
I get
it:1 http://gb.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://gb.archive.ubuntu.com/ubuntu focal-updates InRelease Ign:3 https://packages.twingate.com/apt InRelease Hit:4 http://gb.archive.ubuntu.com/ubuntu focal-backports InRelease Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Err:6 https://packages.twingate.com/apt Release Could not handshake: The TLS connection was non-properly terminated. [IP: 2406:da00:ff00::23ae:647f 443] Reading package lists... E: The repository 'https://packages.twingate.com/apt Release' does not have a Release file.
Any advice?
Thanks
techize
September 26, 2023, 1:41pm
2
OK, so after digging, (and turning off IPV6, just incase that is causing issues) seems that packages.twingate.com is failing with a 408 error.
Arthur
September 26, 2023, 2:26pm
3
Hey Techize,
408 is normally a request timeout error, which is odd.
If you run curl https://packages.twingate.com
do you get any response? how about curl https://packages.twingate.com/apt/
As well, what is the response from nslookup packages.twingate.com
I just double checked using a 20.04 VM hosted on AWS and had no issues.
Let me know!
-arthur
techize
September 26, 2023, 4:11pm
4
Hi Arthur
When run with curl I get a gemfury page when hitting just packages.twingate.com . If I try to connect to https://packages.twingate.com/app I get 404 “not found”
Arthur
September 26, 2023, 4:20pm
5
and immediately after you do that, if you try and do an sudo apt update
what do you get for output? Can you paste the whole block for me please and thanks!
techize
September 26, 2023, 4:33pm
6
Hi Arthur
Here is the full output from the curl and the apt update.
root@gateway:~# curl https://packages.twingate.com/apt/ -v
* Trying 34.232.222.170:443...
* TCP_NODELAY set
* Connected to packages.twingate.com (34.232.222.170) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=packages.twingate.com
* start date: Aug 28 16:14:18 2023 GMT
* expire date: Nov 26 16:14:17 2023 GMT
* subjectAltName: host "packages.twingate.com" matched cert's "packages.twingate.com"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55be6638c220)
> GET /apt/ HTTP/2
> Host: packages.twingate.com
> user-agent: curl/7.68.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 404
< content-type: text/plain; charset=utf-8
< strict-transport-security: max-age=2592000; includeSubDomains
< vary: Accept-Encoding
< x-content-type-options: nosniff
< x-frame-options: DENY
< x-xss-protection: 1; mode=block
< content-length: 10
< date: Tue, 26 Sep 2023 16:31:37 GMT
<
Not Found
* Connection #0 to host packages.twingate.com left intact
root@gateway:~# apt update
Hit:1 http://gb.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://gb.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:3 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Ign:4 https://packages.twingate.com/apt InRelease
Err:5 https://packages.twingate.com/apt Release
404 Not Found [IP: 34.232.222.170 443]
Get:6 http://gb.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Reading package lists... Done
E: The repository 'https://packages.twingate.com/apt Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@gateway:~#
Arthur
September 26, 2023, 4:55pm
7
Can you try running sudo apt update --allow-unauthenticated
That message suggests for some reason the [trusted=yes]
flag in the list file is being ignored.
Let me know if this results in different behaviour.
Thanks,
techize
September 28, 2023, 8:08am
8
Still not going as expected.
ubuntu@gateway:~$ sudo apt update --allow-unauthenticated
Hit:1 http://gb.archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://gb.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:3 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Ign:4 https://packages.twingate.com/apt InRelease
Err:5 https://packages.twingate.com/apt Release
404 Not Found [IP: 34.232.222.170 443]
Get:6 http://gb.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Get:7 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [2,852 kB]
Get:8 http://gb.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [2,328 kB]
Get:9 http://gb.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1,117 kB]
Get:10 http://gb.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [25.8 kB]
Reading package lists... Done
E: The repository 'https://packages.twingate.com/apt Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
ubuntu@gateway:~$
Ive just tried a different network/ISP just incase its a router issue or ISP issue my end. Same error.
techize
September 28, 2023, 1:57pm
9
Ive now managed to download the deb package via another system and I’m able to get it installed.
I guess this shows it is not a problem with your side, but a config somewhere with my network/router/isp filtering or controlling the route to the packages.twingate.com host.
Thanks for the help!
Arthur
September 28, 2023, 2:32pm
10
Glad you got things working. Very strange indeed.