Private modem rentals

Test a private modem over HTTP and SOCKS5

TL;DR

Open the rental in My modems and test its HTTP and SOCKS5 entries separately against the same IP check. Compare each result with the modem’s current exit IP. Then test the site you actually need. Those three results tell you where to investigate.

In this guide

Start with the rental you paid for

In My modems, match the modem to your order. If you bought several, also check the country, carrier and individual modem ID. An order marked pending is still being set up. Reconciling means the balance was charged and the order outcome is being checked. Keep that order open and wait for its result before placing another.

Once the modem is active, open its connection details. Note the current exit IP privately and check whether an automatic rotation is scheduled. During the test, leave the rotation controls alone. Use the host and port printed on this rental for each protocol. The shared Pool Gateway has separate addresses and credentials.

Run the same request through each connection

  1. HTTP. In a client that accepts authenticated HTTP proxies, enter the host, port, username and password from the HTTP entry. Open the IPv4 address check through that client. A successful response is a single IP address. Record the time in UTC and whether the address matches the rental card.
  2. SOCKS5. Open a fresh connection in a client that explicitly supports SOCKS5 username and password. Select SOCKS5 and copy the four fields from its own entry. Request the same IPv4 check. If you use curl, socks5h tells the proxy to resolve the destination hostname. A browser with only system HTTP proxy settings cannot run this half of the test.
  3. Your workload. With the working proxy profile still selected, load one page you control or have permission to test. Record the expected result, such as the correct currency on a regional storefront. The address check confirms routing. The storefront check answers a different question about the application.

Using curl on macOS or Linux? For each entry, set the shell variable ending in _ENDPOINT to the host and port together, and the variable ending in _USER to its username. Run each command in a terminal. curl prompts for that entry’s password. The empty proxy bypass list makes this test use the proxy even if your shell normally skips it for this address.

curl --disable --noproxy "" --max-time 15 --fail --silent --show-error \
  --proxy "http://$HTTP_MODEM_ENDPOINT" --proxy-user "$HTTP_MODEM_USER" \
  https://api.ipify.org

curl --disable --noproxy "" --max-time 15 --fail --silent --show-error \
  --proxy "socks5h://$SOCKS_MODEM_ENDPOINT" --proxy-user "$SOCKS_MODEM_USER" \
  https://api.ipify.org

Each successful check should return a single IPv4 address. If the check service returns an HTTP error or an error page, record that result before comparing addresses.

Decide what the two results mean

Use the same IPv4 check for both protocol results.
What you observeNext check
Both return the modem’s current IPBoth protocols reached the check through the expected exit. If your own page fails, inspect its status or application logs.
HTTP works, SOCKS5 failsCheck the SOCKS5 port, credentials and client authentication support. A working HTTP path gives you a control for the same rental.
SOCKS5 works, HTTP asks for credentialsRe-enter the HTTP proxy login in the proxy settings. An HTTP 407 is a proxy authentication response.
Neither connectsCheck that the order is active and the IP-check service answers outside the proxy. Check the card for a line warning, then use the connection troubleshooting guide for the specific error.

If the two addresses differ, refresh the card and check whether the carrier changed the exit between requests. Repeat close together on fresh connections. An IP match on one request cannot establish how long the address will stay the same.

An example that support can act on

Suppose a storefront tester records “14:02 UTC, HTTP returned the card’s current IP. 14:03 UTC, SOCKS5 asked for authentication and then disconnected. Same laptop, same destination.” That gives support a working control and a specific failure. If re-entering the SOCKS5 details fixes it, the customer can keep the same rental.

If the problem persists, send the order or modem ID, UTC timestamps, client name, protocol and exact error in a private support ticket. Remove credentials, full proxy URLs, rotation links and VPN profiles from attachments. If the line itself is failing, see when to renew or replace a private modem before changing it.

Common questions

What if the SOCKS5 entry is missing?
Wait if the card is still loading connection details. If an active rental shows only HTTP after a refresh, send support the modem ID and ask which credentials are available. Guessing the SOCKS5 port makes the result hard to interpret.
Do I have to rotate the IP to accept the modem?
No. First check both protocols against the current exit. A rotation changes one of the things you are trying to measure and can interrupt work already using the modem.

Sources