Allow Proxy for Remote Communication

JFrog Connect allows edge devices to use a proxy to communicate with the servers to use Remote Control and Remote Commands features.

Edge devices that communicate through web proxy servers require changes in the JFrog Connect service configurations to enable packet transmission. This page describes how to configure communication through a proxy specifically to enable Remote Control and Remote Commands.

To enable remote connections through a proxy, do the following:

1. Define the proxy protocol where applicable, as shown in the examples below. Available proxies are:

socks4 -> 4 
socks5 -> 5 
http -> connect

For example, http:

ProxyCommand nc -X connect -x 192.168.20.165:8000 %h %p

1. To enable Remote Control through a proxy, add the following line to the end of the file /etc/connect/service/remoteA (note the indentation):

    ProxyCommand nc -X <4|5|connect> -x 
<proxy-host>:<proxy-port> %h %p

1. To enable Remote Access through a proxy, add the following line to the end of the file /root/.ssh/config:

Host forwarding.connect.jfrog.io
    ProxyCommand nc -X <4|5|connect> -x 
<proxy-host>:<proxy-port> %h %p

What's Next?

Learn how to allow a proxy for standard communication between the edge device and the Connect server.