The client also provides optional flags to use a web proxy, and to display its own version or help text:
The access key that you provide when connecting a tunneling client identifies you (the user) and the project you are logged into. If a new client connects with the same key while an old one is connected, the old client will disconnect after emitting an informative message to the console.
When the client is running, it may write diagnostic messages to the log file, located in the same folder from which it was run. The log file is named per session, with the process ID as part of the file name (eg, network-tunnel_12718.log).
Using the Client with self-signed Certificate
If the Cloud server is configured for Secure mode and is using a self-signed certificate, you may need to add the following 2 arguments to the invocation of the client:
Where path-to-cert.pem is the file where your custom certificate can be found.
Using the Client with untrusted Cloud Certificate
In case you use a custom certificate for your cloud server, which is not trusted by the operating system on your Windows/macOS station, the tunneling client will not connect to the cloud, and you will see a warning similar to this:
The simplest way to resolve this, is to add the flag
--no-verify-server-ssl-cert to the tunneling client command line. This causes the client to trust any certificate.