Use Proxies.sx with GenRouter
Import a proxy, assign it to one phone or computer, and check the route before connecting the rest of your devices.
GenRouter lets you assign proxy connections from its router dashboard. Your devices connect to the router; Proxies.sx supplies the proxy credentials. Start with one device and a connection you can test.
1. Choose the connection you need
| Product | Where to copy the connection | What you control |
|---|---|---|
| Private modem rental | Open your active rental in My modems. Copy its own host, protocol port, username and password. | One rented modem, its supported rotation controls and rental term. The carrier can still change its public IP. |
| Shared pool, billed per GB | Open Pool Gateway. Choose an explicit pool, an available country, protocol and saved session ID. | A routing preference within available supply. It does not reserve a device or guarantee a distinct IP for each imported row. |
Keep rental endpoints exactly as shown on their cards. The gateway host and ports below apply to shared-pool connections.
Shared-pool fields
| Field | Value |
|---|---|
| Host | gw.proxies.sx |
| Protocol and port | HTTP: 7000. SOCKS5: 7001. |
| Username example | psx_ACCOUNT_ID-peer-us-sid-genrouter01-rot-sticky |
| Password | Your gateway proxy password from the portal. |
Replace the placeholders with your own credentials. Choose a country with current stock in the portal; us is a format example. The proxy password is separate from your account login password and API key.
Choose the pool explicitly: peer uses mixed peer supply, mbl uses shared carrier modems, and any or best may use both. For residential classification, add -iptype-residential and check matching stock. A pool name alone does not guarantee residential-only exits.
Use a different saved SID for each device or workflow, such as genrouter01 and genrouter02. SIDs accept 1–64 lowercase letters, digits or underscores. Reuse the same SID and routing settings when reconnecting that workflow. Different SIDs can still receive the same public IP.
2. Add one proxy to GenRouter
- Open your GenRouter management page on your local network. The vendor documents
192.168.5.1:9000as its default address; use your router's actual management address if you changed it. - Open Proxy Manager and choose Add proxy.
- Select the import format shown by GenRouter. Export your Proxies.sx connection in that same format, then paste one connection per line into the Proxy field.
- Click Add proxy to save the list. The field table above is a reference, not an import file.
If the exported format does not match the router's options, use the separate host, port, username and password fields in the next step. Keep credentials private; do not put an import list in a shared document or support screenshot.
3. Assign it to a device
- On the router dashboard, open Devices and select Update proxy for your test device.
- Choose HTTP or SOCKS5 to match the connection and port.
- Use Select from List to choose the imported entry, or Input Manually to enter each field. Confirm the selected connection with the router's Add or Update proxy control.
- Connect that device to the intended GenRouter Wi-Fi network and perform the checks below.
For a larger group, GenRouter also supports selecting several devices and using Update Proxy with an imported list. Expand only after the one-device test works. More imported rows do not create more account quota, concurrency capacity or unique IPs.
4. Check the route before expanding
- From the assigned device, open an IP-check page and record the observed country and exit privately. Repeat after reconnecting the same workflow.
- Open a page your actual workflow needs. Check that it loads and that any login or session remains usable. An IP-check success alone does not establish that the destination accepts the connection.
- If you plan to offer both protocols, test HTTP and SOCKS5 separately. A working HTTP connection does not establish that the SOCKS5 port works.
- Check DNS and WebRTC behavior in the device's actual application. This guide does not establish UDP routing or leak protection for every application.
- Review traffic and the selected country's rate in Proxies.sx before importing the remaining devices. Pool traffic consumes a shared account allowance; country tiers affect the balance consumed.
Sticky routing requests the same eligible assignment, but its public IP can change. Timed rotation requires a stable SID and is evaluated on a subsequent connection; it does not close existing sockets or guarantee a different IP. Use a new SID when changing the routing settings.
If the first device does not work
| What you see | What to check |
|---|---|
| The proxy was imported but the device keeps its previous route | Confirm the entry is assigned under Devices and the device joined the intended Wi-Fi network. |
| Authentication or quota error | Check the complete generated username, proxy password, account allowance and any key cap or expiry. Save the sanitized error code and UTC time. |
| No matching stock | Check the exact pool, country and filters in Pool Gateway. Keep the requested location unchanged until you deliberately select an available alternative. |
| HTTP works, SOCKS5 fails | Check the protocol and port independently. For a rental, use the card's advertised SOCKS5 endpoint. Report which protocol fails; repeatedly replacing a working modem is not a diagnostic step. |
| Same IP on several devices, or IP changes later | Check that workflows have different saved SIDs. Separate SIDs do not guarantee distinct IPs, and a carrier can change the IP of the same modem. |
For help, send the product, selected country/pool, protocol, UTC time and a screenshot with credentials removed to maya@proxies.sx. Include the affected rental ID if you use a Private modem.
References
- GenRouter: Add proxy
- GenRouter: assign a proxy to a phone or BoxPhone
- Proxies.sx shared-pool reference and Private modem rentals
- GenRouter partner overview
Instructions checked against the linked GenRouter documentation on November 10, 2026.