Skip to content

Cloud Access Connector Installer Issues

Teradici moved to a new distribution system and on December 31, 2020 the legacy system was shut down. As a result of this change some errors may occur for users with Cloud Access Connectors that were installed from older installer versions.

In almost all cases downloading the latest installer version and running the cloud-access-connector install, cloud-access-connector update or cloud-access-connector diagnose commands with the new install should work.

Error Messages

The following are a list of potential error messages that a user may encounter as a result of the change of distribution system:

Attempting to download the installer

Error 1

user@vm:~$ mkdir ~/v2connector && cd ~/v2connector
user@vm:~/v2connector$ curl -LO https://teradici.bintray.com/cloud-access-connector/cloud-access-connector-0.1.1.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 41 0 41 0 0 141 0 --:--:-- --:--:-- --:--:-- 141
user@vm:~/v2connector$ tar xzvf cloud-access-connector-0.1.1.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Error 2
user@vm:~$ mkdir ~/v2connector && cd ~/v2connector
user@vm:~/v2connector$ curl -LO https://teradici.bintray.com/cloud-access-connector/cloud-access-connector-0.1.1.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: teradici.bintray.com

Running older installer versions

If the Cloud Access Connector installer was installed before December 11, it may generate some of the following errors:

Error 3

[2020-12-22T20:36:57Z]  INFO Verifying installer version
[2020-12-22T20:36:57Z] ERROR yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `The req...` into docker.ComposeConfig

Error 4

[2020-12-22T20:07:09Z]  INFO Downloading compose file
[2020-12-22T20:07:09Z]  INFO curl: (60) SSL certificate problem: self signed certificate
[2020-12-22T20:07:09Z]  INFO More details here: https://curl.haxx.se/docs/sslcerts.html
[2020-12-22T20:07:09Z]  INFO
[2020-12-22T20:07:09Z]  INFO curl failed to verify the legitimacy of the server and therefore could not
[2020-12-22T20:07:09Z]  INFO establish a secure connection to it. To learn more about this situation and
[2020-12-22T20:07:09Z]  INFO how to fix it, please visit the web page mentioned above.
[2020-12-22T20:07:09Z] ERROR exit status 60
Error 5
[2020-12-22T20:24:06Z]  INFO Configuring Docker Daemon
[2020-12-22T20:24:06Z]  INFO populateTrustAndKeyStore: Pulling setup container and populating Java trust and key store
[2020-12-22T20:24:07Z]  INFO Error response from daemon: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<!doctype html><html lang=\"en\"><head><title>HTTP Status 404 – Not Found</title><style type=\"text/css\">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 – Not Found</h1><hr class=\"line\" /><p><b>Type</b> Status Report</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class=\"line\" /><h3>Apache Tomcat/8.5.59</h3></body></html>"
[2020-12-22T20:24:07Z] ERROR exit status 1
Error 6
[2021-02-11T01:02:42Z] INFO Error response from daemon: Head https://teradici-docker-registry.bintray.io/v2/diagnostics/manifests/stable: unauthorized: Unauthorized
[2021-02-11T01:02:42Z] ERROR exit status 1