Gateway or direct server IP: what to copy from the portal
A proxy card can contain a gateway, a direct server IP, a port, credentials, and a mobile exit IP. These fields are not interchangeable. The application first connects to the service endpoint, while the destination observes the outbound mobile address. MobiProxyDesk recommends the gateway for most customers; use a direct address only where an integration or a diagnostic procedure explicitly requires it.
Key points in one minute
- The Host field takes the connection endpoint, not the IP shown by an IP-check page.
- The gateway keeps the standard credentials stable after an equipment change and is normally the recommended option.
- A direct IP identifies the current server and is not the mobile exit IP.
- After an equipment change, direct connection details should be exported again.
- A direct IP alone does not guarantee lower latency or better stability.
Four different values
The connection endpoint answers where the application connects. The port selects a service at that endpoint. Credentials prove access rights. The exit IP answers a different question: which source did the destination observe after the mobile network leg? Copying the exit IP into the Host field will usually break the connection.
Why the gateway is easier
In MobiProxyDesk, the gateway is the recommended endpoint: its address, port, username, and password remain stable after an equipment change. The user does not need to replace Host with a new direct server address manually. Copy the value exactly as a fresh export shows it: stable gateway credentials are a service behavior, not proof of a particular DNS design.
What a direct IP means
A direct IP in MobiProxyDesk points to the current server node for that proxy. Use it only when a compatible integration or an approved diagnostic procedure explicitly selects direct mode. Do not confuse it with an Allowed IP: an Allowed IP authorizes the observed source address of the client, while a direct IP is the server address that the client connects to. It does not reveal the mobile exit address or promise automatic failover when the server assignment changes.
What can change after an action
A mobile IP change can alter only the address observed by the destination while leaving the gateway Host unchanged. An equipment or server-assignment change is deeper: the direct endpoint or related details may change. Wait for the final action status, create a fresh export, and replace the application configuration as one controlled change.
A simple selection rule
Start with the gateway and the complete details for the required protocol, HTTP or SOCKS5. Switch to a direct IP only for a documented reason and keep a quick path back to the gateway. Compare speed with repeatable measurements against the same authorized destination; one successful request does not prove an endpoint advantage.
Practical checklist
- 1Choose HTTP or SOCKS5 according to application support.
- 2Copy Host, port, username, and password from one current export.
- 3Do not use the mobile exit IP as the Host value.
- 4Do not confuse the direct server IP with the client's Allowed IP.
- 5Use the gateway unless you have a verified reason for a direct IP.
- 6Export fresh connection details after an equipment change.
- 7Remove obsolete details from configuration and logs.
Sources and documentation
This material is based on primary, official, and technical sources. The article is an original summary written for this knowledge base.