> 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/ensuring-the-best-endpoint-uptime.md). # Ensuring the Best Endpoint Uptime Learn how to keep your Proxidize Proxy Builder endpoints stable by following the recommended server, modem, network, and environment practices. ## What Endpoint Uptime Means In Proxy Builder, an endpoint is a proxy connection created from your hardware. For Linux Agent setups, this usually means: * A Linux server running the Proxidize platform. * USB modems connected to the server through a powered USB hub. * SIM cards inside the modems. * A stable wired internet connection from the server to your router. * The Proxidize dashboard used to monitor and manage the setup. Endpoint uptime depends on the full setup. A modem can be healthy, but the endpoint can still go down if the server runs out of storage, the SIM runs out of data, the internet connection drops, or the hardware is placed in a poor environment. *** ## Start With the Recommended Setup The best way to improve uptime is to follow the recommendations in the Proxidize Help Center before troubleshooting advanced issues. ### At minimum, make sure: * The Linux Agent is installed on a supported operating system. * The server meets or exceeds the minimum hardware requirements. * The server has enough free storage. * The server is connected through wired Ethernet. * The USB modems are supported. * The USB hub is externally powered. * The host is onboarded correctly. * The server has a stable local IP if local access or port forwarding is needed. For setup requirements, see [Linux Agent: System Requirements & Supported Modems](/legacy-products/proxy-builder/hardware/linux-agent-system-requirements-and-supported-modems.md). For host setup steps, see [Linux Agent: Onboarding and Offboarding Hosts](/legacy-products/proxy-builder/setup-and-onboarding/linux-agent-onboarding-and-offboarding-hosts.md). *** ## Before You Start Before troubleshooting uptime, collect: * Server model or kit type. * Operating system version. * Available storage. * RAM amount. * Number of connected modems. * USB hub model and power source. * SIM carrier for each modem. * Whether each SIM still has active data. * Internet speed and stability. * Whether the issue affects one modem, one hub, or the whole server. *** ## Keep Enough Free Storage on the Server Your Proxidize server needs available storage to run normally. Low or full storage can cause: * Service instability. * Failed updates. * Logging issues. * Slow dashboard response. * Unexpected process failures. Check available storage from the server's terminal: ```bash df -h ``` If storage is low, free space before continuing. Larger setups with more modems may need more storage, especially if logs are retained for longer periods. *** ## Use a Stable Wired Internet Connection The Proxidize Linux Agent should run on a server connected through **wired Ethernet**. Wi-Fi is not supported for Linux Agent setups because it can introduce instability, packet loss, and unpredictable connectivity issues. **To improve uptime:** * Connect the server directly to the router or switch using Ethernet. * Avoid weak Wi-Fi bridges or repeaters. * Use a stable router and internet connection. * Confirm the internet connection is fast enough for your proxy usage. * Monitor whether disconnects happen during ISP outages or router restarts. *** ## Make Sure SIM Cards Stay Topped Up With Data Each USB modem depends on its SIM card and mobile carrier connection. If a SIM runs out of data or becomes suspended by the carrier, the modem may still appear physically connected but the endpoint will not work correctly. Best practices: * Track data usage for each SIM. * Keep SIM plans renewed and topped up. * Confirm the carrier has not throttled or suspended the SIM. * Test the SIM in another device if you suspect the plan is inactive. * Document which SIM belongs to which modem or endpoint. *** ## Use Supported and Recommended Modems Use modems recommended or supported by Proxidize for your region and setup. Unsupported or region-mismatched modems may cause: * Weak signal. * No connectivity. * Frequent disconnects. * Poor speed. * Inconsistent behavior across carriers. Review the supported modem list before expanding or replacing hardware: [Linux Agent: System Requirements & Supported Modems](/legacy-products/proxy-builder/hardware/linux-agent-system-requirements-and-supported-modems.md) *** ## Use a Powered USB Hub USB modems require stable power. An unpowered or low-quality USB hub may not provide enough power for multiple modems, which can cause random disconnects or modem instability. Best practices: * Use an externally powered USB hub. * Avoid overloading one hub with too many modems. * Use the hub's original power adapter. * Avoid loose USB connections. * Replace hubs that randomly disconnect devices. *** ## Place the Server and Modems in a Suitable Environment Physical placement can affect uptime. Avoid placing the server or kit: * In a poorly ventilated area. * Near heat sources. * Inside closed cabinets with little airflow. * Near devices that may cause network or cellular interference. * In areas with weak cellular reception. Better placement can improve both heat management and signal reception. *** ## Maintain Good Cellular Signal Reception Weak signal can cause endpoints to disconnect, slow down, or fail to reconnect. To improve signal: * Place modems in an area with better carrier reception. * Avoid placing modems behind metal surfaces or dense walls. * Test different modem positions. * Compare carriers if one SIM performs worse than others. * Check whether nearby towers support your modem's bands. For band and tower guidance, see [Proxidize Modems Bands and Frequencies](/legacy-products/proxy-builder/advanced-configuration/proxidize-modems-bands-and-frequencies.md). If a modem keeps choosing a weak or congested band, band locking may help. See [USB Modem Band Locking on Proxidize MX2 Modems](/legacy-products/proxy-builder/advanced-configuration/usb-modem-band-locking.md). ### Keep the Linux Agent Updated Software updates may include stability improvements, security fixes, and compatibility improvements. Keep the Proxidize Linux Agent updated so the server has the latest available fixes. For update steps, see [Keeping Your Proxidize Linux Agent Up to Date](/legacy-products/proxy-builder/advanced-configuration/keeping-your-proxidize-linux-agent-up-to-date.md). *** ## Monitor for Patterns When uptime issues happen, look for patterns before changing settings. Ask: * Does the issue affect one modem or all modems? * Does it affect one USB hub? * Does it affect one carrier? * Does it happen when data runs out? * Does it happen during heavy usage? * Does it happen after router or ISP outages? * Does it happen when the server storage is low? * Does it happen when the room or cabinet becomes hot? Patterns help identify whether the issue is caused by the server, modem, SIM, carrier, USB hub, router, internet connection, or environment. *** ## Troubleshooting | Issue | What to Check | | ------------------------------------------ | ----------------------------------------------------------------------------------------- | | One endpoint is unstable | Check that modem's SIM data, signal, carrier, band, USB port, and modem model. | | Multiple endpoints disconnect at once | Check the USB hub, hub power supply, server power, router, or internet connection. | | All endpoints are offline | Check server internet, Linux Agent status, storage, power, and dashboard connectivity. | | Endpoint is online but proxy traffic fails | Check SIM data balance, carrier throttling, generated proxy port, and routing. | | Endpoint fails after server reboot | Confirm the server has enough storage and services start correctly after reboot. | | Remote access fails but local access works | Check public/WAN IP changes, DDNS, port forwarding, and CGNAT/double NAT. | | Modems become unstable over time | Check heat, ventilation, USB hub power, and whether the modems are in a weak-signal area. | *** ## Related Articles * [Proxidize Proxy Builder (Legacy) Overview & How It Works](/legacy-products/proxy-builder/getting-started/proxidize-proxy-builder-legacy-overview-and-how-it-works.md) * [Linux Agent: System Requirements & Supported Modems](/legacy-products/proxy-builder/hardware/linux-agent-system-requirements-and-supported-modems.md) * [Linux Agent: Onboarding and Offboarding Hosts](/legacy-products/proxy-builder/setup-and-onboarding/linux-agent-onboarding-and-offboarding-hosts.md) * [Proxidize Modems Bands and Frequencies](/legacy-products/proxy-builder/advanced-configuration/proxidize-modems-bands-and-frequencies.md) * [USB Modem Band Locking on Proxidize MX2 Modems](/legacy-products/proxy-builder/advanced-configuration/usb-modem-band-locking.md) * [Local IP Reservation (DHCP)](/legacy-products/proxy-builder/advanced-configuration/local-ip-reservation-dhcp.md) * [Dynamic Public/WAN Addresses](/legacy-products/proxy-builder/advanced-configuration/dynamic-public-wan-addresses.md) * [Keeping Your Proxidize Linux Agent Up to Date](/legacy-products/proxy-builder/advanced-configuration/keeping-your-proxidize-linux-agent-up-to-date.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 . --- # 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://help.proxidize.com/legacy-products/proxy-builder/advanced-configuration/ensuring-the-best-endpoint-uptime.md?ask=&goal= ``` `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.