> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/administration-new-ui/general-settings/allow-proxy/allow-proxy-for-remote-communication.md).

# Allow Proxy for Remote Communication

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

2. 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

```

3. 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](/administration-new-ui/general-settings/allow-proxy.md) between the edge device and the Connect server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.connect.jfrog.io/administration-new-ui/general-settings/allow-proxy/allow-proxy-for-remote-communication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.