HTTP proxy support

  • Updated

The LucidLink Classic Client supports the following HTTP proxy options:

Currently, Proxy by hostname is supported when auto-detected from the OS proxy configuration or PAC/WPAD. When using the --proxy argument via CLI or the "proxy" override in the app.json, only IP addresses are supported.

We recommended configuring the proxy via the OS proxy settings or PAC/WPAD for full feature support.

Automatically detected

  1. OS proxy configuration
  2. PAC (Proxy Auto-Configuration) file and WPAD

Manually specified

It can be passed either on the command line as a --proxy option on the link and update commands, or in the LucidApp configuration file in .lucid/app.json with the "proxy" config parameter.

If you would like to set the proxy settings manually, please follow these steps:

1) Make sure the Lucid client is stopped.

2) Find and edit the configuration file .lucid/app.json in your user's directory. Replace "127.0.0.1:8080" with the IP and port of the proxy server you wish to connect through:

3) To find your .lucid folder location open a Terminal Window or Windows Command Prompt and type lucid2 info and look for the config-path config directory.

Append "proxy": "127.0.0.1:8080" to the end of the app.json by adding , behind the last ] between the final }.

 ],
"proxy": "127.0.0.1:8080"
}

4) Start the Lucid client. It should now try to connect via the proxy server specified in the configuration file.

Note that the proxy server needs to be an HTTP proxy server that supports HTTP tunneling (https://en.wikipedia.org/wiki/HTTP_tunnel#HTTP_CONNECT_method). The proxy server needs to allow tunneling of TCP traffic with destination port 443 (used for metadata synchronization) as well as HTTP(s) traffic to the object store. SOCKS proxies are not supported.

 
 

Was this article helpful?

0 out of 0 found this helpful