HTTP proxy support

  • Updated

The LucidLink client supports running behind an HTTP proxy that supports connect tunneling of TCP traffic. Basic authentication is supported. The proxy configuration is specified using an IP Address.

Note that only IP address is supported and not hostnames.

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

The current recommended way to connect via a proxy is to:

1) Make sure the Lucid client is stopped.

2) Find and edit the configuration file .lucid/app.json in your user's directory. Replace "" 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 lucid info and look for the config-path config directory.

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

"proxy": ""

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 ( 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