> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/legacy-products/proxy-builder/advanced-configuration/keeping-your-proxidize-linux-agent-up-to-date.md).

# Keeping Your Proxidize Linux Agent Up to Date

Update the Proxidize Linux Agent and keep hosts on supported versions.

Learn how to manually update the Proxidize Linux Agent on your local server.

### What Is the Proxidize Linux Agent?

The Proxidize Linux Agent is the software installed on your local Linux server.

It is responsible for:

* Managing the USB modems connected to the server.
* Creating and managing local proxy endpoints.
* Communicating with the Proxidize Cloud Dashboard.
* Providing a local dashboard for troubleshooting and local management.

The Cloud Dashboard at [app.proxidize.com](https://app.proxidize.com/) is updated automatically by Proxidize. The Linux Agent runs on your own server, so it may need to be updated manually.

***

### Why Keep the Linux Agent Updated?

Proxy Builder is a legacy platform, so no new features are planned. See [Proxy Builder Platform Deprecation Notice](https://help.proxidize.com/legacy-products/proxy-builder-platform-deprecation-notice.md).

Running the latest available version of the Linux Agent gives your server:

* Stability improvements.
* Security improvements.
* Bug fixes.
* Compatibility improvements for supported hardware.

If your server runs an older version, updating helps your Proxy Builder setup stay stable.

***

### Before You Start

Make sure you have:

* Access to the Proxidize server terminal.
* The server's Linux user password.
* A stable internet connection on the server.
* Enough free storage on the server.

The update may temporarily restart services or interrupt local dashboard/proxy availability.

If you are not sure whether your server meets the requirements, see [Linux Agent: System Requirements & Supported Modems](https://help.proxidize.com/legacy-products/proxy-builder/getting-started/linux-agent-system-requirements-and-supported-modems.md).

{% stepper %}
{% step %}

## Open a Terminal on the Proxidize Server

You can update the Linux Agent from a local terminal or over SSH.

{% tabs %}
{% tab title="Open Terminal Locally" %}
Use this option if you have a monitor, keyboard, and mouse connected to the Proxidize server.

1. Connect a monitor to the server using HDMI.
2. Open the applications menu.

![](https://content.gitbook.com/content/iAQa47xivOtQQ7mQZOnQ/blobs/c1T87DS6snMfUNVOaYf6/20250326101452_8040.png)

3. Search for **Terminal**.
4. Open the Terminal app.

![](https://content.gitbook.com/content/iAQa47xivOtQQ7mQZOnQ/blobs/yt7DMr1C5p4oIangLz5q/20250326101513_6235.png)
{% endtab %}

{% tab title="Connect Over SSH" %}
Use this option if SSH access is enabled and you know the server's local IP address.

From another computer on the same network, open a terminal and connect to the server:

```bash
ssh username@server-ip-address
```

Example:

```bash
ssh proxidize@192.168.1.25
```

Replace `username` and `server-ip-address` with the correct Linux username and local IP address for your Proxidize server.

If you are not sure how to find the server IP address, see [Understanding Public IPs, Private IPs, and Your Router IP Address](https://help.proxidize.com/legacy-products/proxy-builder/advanced-configuration/understanding-public-ips-private-ips-and-your-router-ip-address.md).
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

## Check Available Storage

Before updating, check that the server has enough free storage:

```bash
df -h
```

If the disk is full or almost full, free storage before continuing. Low storage can cause updates to fail or services to behave unexpectedly.
{% endstep %}

{% step %}

## Switch to Root User

In the terminal, run:

```bash
sudo su
```

Enter the Linux user password when prompted.

After switching to root, your terminal prompt may change from `$` to `#`.
{% endstep %}

{% step %}

## Run the Linux Agent Update Command

Run the following command:

```bash
curl -fsSL https://pxfile.com/install_cloud | bash
```

The update process will start automatically. Wait for it to finish.

Do not close the terminal or power off the server while the update is running.
{% endstep %}

{% step %}

## After the Update Completes

When the update is complete, the installer should show the local IP address you can use to access the Linux Agent again.

Open the local dashboard in your browser using the server's local IP address.

Example:

```
http://192.168.1.25
```

If your setup uses a different dashboard port or custom access method, use the address configured for your environment.
{% endstep %}

{% step %}

## Confirm the Linux Agent Is Working

After updating:

1. Open the local dashboard.
2. Confirm the dashboard loads.
3. Confirm the host appears online in the Cloud Dashboard.
4. Confirm connected modems or endpoints start appearing normally.
5. Test a proxy if needed.
   {% endstep %}
   {% endstepper %}

***

### Troubleshooting

| Issue                                          | What to Check                                                                              |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------ |
| The update command does not run                | Confirm the server has internet access and DNS is working.                                 |
| sudo su asks for a password                    | Enter the Linux user password for the server account.                                      |
| Permission denied                              | Confirm your Linux user has sudo permissions.                                              |
| The update fails partway through               | Check available storage, internet connection, and rerun the command.                       |
| The local dashboard does not open after update | Confirm the server IP address, local network connection, and service status.               |
| Host does not appear online in Cloud Dashboard | Confirm the server has internet access and wait a few minutes for reconnect.               |
| Proxies do not work after update               | Confirm modems are online, SIMs have data, and the endpoints are visible in the dashboard. |

***

#### Related Articles

* [Proxidize Proxy Builder Overview & How It Works](https://help.proxidize.com/legacy-products/proxy-builder/getting-started/proxidize-proxy-builder-legacy-overview-and-how-it-works.md)
* [Linux Agent: System Requirements & Supported Modems](https://help.proxidize.com/legacy-products/proxy-builder/getting-started/linux-agent-system-requirements-and-supported-modems.md)
* [Linux Agent: Onboarding and Offboarding Hosts](https://help.proxidize.com/legacy-products/proxy-builder/setup-and-onboarding/linux-agent-onboarding-and-offboarding-hosts.md)
* [Ensuring the Best Endpoint Uptime](https://help.proxidize.com/legacy-products/proxy-builder/advanced-configuration/ensuring-the-best-endpoint-uptime.md)
* [Understanding Public IPs, Private IPs, and Your Router IP Address](https://help.proxidize.com/legacy-products/proxy-builder/advanced-configuration/understanding-public-ips-private-ips-and-your-router-ip-address.md)

***

### Need Help?

If you have any questions, concerns, or need further clarification, feel free to reach out to us via live chat or email us directly at <support@proxidize.com>.


---

# 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://help.proxidize.com/legacy-products/proxy-builder/advanced-configuration/keeping-your-proxidize-linux-agent-up-to-date.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.
