> For the complete documentation index, see [llms.txt](https://docs.goproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goproxies.com/proxies/integrations/operating-systems/linux.md).

# Linux

Linux comes in many distributions, so this guide focuses on a system-wide proxy setup that applies broadly across them.

### Requirements

Before getting started, ensure that:

* No other VPN or proxies are active.
* You have your GoProxies endpoint ready, e.g. `proxy.goproxies.com:1080`
* Your GoProxies subuser (also called API User) username and password.

### Proxy Setup

1. Open **Terminal**.
2. Sign in as a root user.
3. Open the `/etc/environment` file with `nano`.
4. In the text editor, configure your proxy as follows:

```
http_proxy="http://proxy.goproxies.com:1080"
https_proxy="http://proxy.goproxies.com:1080"
no_proxy="localhost"
```

{% hint style="info" %}
If you need authentication, use the format `http://username:password@proxy.goproxies.com:1080`. You can also target a specific country by appending `-country-country_abbreviation` to your username, e.g. `customer-exampleuser-country-us`, as covered in our [proxy parameters article](https://docs.goproxies.com/proxies/rotating-residential-proxies/proxy-parameters).
{% endhint %}

5. Press `CTRL + X`, then `Y` to save, and `ENTER` to confirm the file location.
6. Lock the file with `chattr +i /etc/environment` and reboot your machine. Skipping this step may cause your proxy settings to reset.

{% hint style="info" %}
To unlock the file later, use `chattr -i /etc/environment`.
{% endhint %}

### Verify the Connection

Open a browser and go to [ip.goproxies.com](https://ip.goproxies.com). If the IP shown reflects your proxy location, you're all set.


---

# 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.goproxies.com/proxies/integrations/operating-systems/linux.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.