> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/storage/local-storage/proxy-configuration.md).

# Proxy Configuration

Learn about working with proxy configuration for file servers

## Overview

If the Couchdrop Windows / macOS Agent is running in a network where internet access is only available through a proxy server, additional configuration is required.

You can add the proxy details directly to the Couchdrop Agent configuration file.

{% hint style="info" %}
For the full agent installation and configuration process, see **Windows / Mac File Server**.
{% endhint %}

## How to configure a proxy

{% stepper %}
{% step %}

### Install and configure the agent

Install and run the Couchdrop Agent, then set the connection token as normal.
{% endstep %}

{% step %}

### Stop the agent

Stop the Couchdrop Agent before editing its configuration file.
{% endstep %}

{% step %}

### Locate the configuration file

Locate the Couchdrop Agent configuration file.

On Windows, it is normally stored in:

`C:\Users\%username%\AppData\Local\CouchdropCloudConnector`

Open the configuration file using Notepad or another text editor. The file contains the agent configuration in JSON format.
{% endstep %}

{% step %}

### Add the proxy configuration

Locate the `"proxies"` section and add the HTTP and HTTPS proxy addresses.

```json
{
  "...": "...",
  "proxies": {
    "http": "",
    "https": ""
  },
  "...": "..."
}
```

Enter the proxy URL required by your network for the `"http"` and `"https"` values.
{% endstep %}

{% step %}

### Save and restart the agent

Save the configuration file, then start the Couchdrop Agent again.

The agent will use the configured proxy when communicating with Couchdrop.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Proxy settings, along with shortcut links to the agent logs and configuration files, are also available from the **Settings** gear within the Couchdrop Agent.
{% endhint %}

## Proxy URL syntax

Use the appropriate syntax for your proxy configuration.

| Type                    | Format                                 | Example                                    |
| ----------------------- | -------------------------------------- | ------------------------------------------ |
| No username or password | `http://<ip>:<port>`                   | `http://127.0.0.1:8080`                    |
| Username and password   | `http://username:password@<ip>:<port>` | `http://proxyuser:password@127.0.0.1:8080` |
| SOCKS proxy             | `socks://<ip>:<port>`                  | `socks://127.0.0.1:8080`                   |

## Debugging

If the agent cannot connect after configuring the proxy, check the log files stored in the same directory as the configuration files.

You can also use the shortcuts available from the agent **Settings** menu to open the logs and configuration files.

For additional help, contact [**support@couchdrop.io**](mailto:support@couchdrop.io).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/storage/local-storage/proxy-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.