Lords Mobile Proxy: Where Is the Rule Written, and How Much Does It Cover?
In Lords Mobile, everything you see on screen is held on the publisher's infrastructure; the client only requests and displays. A proxy does not change that picture, it only changes the address the request comes from. This page explains whether to write the rule on the router or on the device, which traffic falls outside the scope, and why the exit silently closes on corporate networks.
Four separate loadsThe separate behaviour of identity, game state, notification channel and asset download traffic.
02
Scope decisionThe traffic that router, system-wide, network setting and per-application rules actually cover.
03
Kingdom serverWhere the world is hosted, and why "private server" claims are outside our scope.
04
Corporate networksPorts closed on campus and office exits, and policy-compliant routes to a solution.
In a mobile strategy game with a persistent world, the proxy decision differs from browser work on two points. First, there are few places where you can write the rule: you cannot interfere with the application's own network stack. Second, there is no screen that directly shows which requests the rule is applied to; you can only tell through indirect tests.
The sections below answer four questions: what loads the client actually produces on the network, which of those loads can pass through a tunnel, what writing the rule on the router gains and costs, and why the thing cutting your connection on a corporate network is usually not the game but an egress filter.
Let us draw a boundary up front. A proxy is a routing decision: your exit address changes, while your device identity, your session token and your account's history stay exactly as they are. There is no promise of speed either; adding a hop lengthens the total round-trip time in most setups.
The client produces four distinct loads on the network
When the app opens, the first job is establishing identity: the client performs a TLS handshake and identifies itself with the token stored on the device. The address visible on the other side is the proxy server's address if a proxy is in use. The token does not change, because it lives on the device, not on the network.
The second load is game state. Resource accumulation, troop training times and rally timing are held server-side; the client does not compute the result itself. Traffic therefore flows as small, frequent HTTPS requests: it does not strain bandwidth, but the round-trip time of each request determines how fluid the interface feels.
The third load is the long-lived notification channel: kingdom chat, guild calls and attack alerts — events that flow from the server towards you. This channel wants to stay open, and every point in between can drop an idle connection according to its own timeout policy. The fourth load is asset downloads: event images and interface updates usually come from a content delivery network and make up the bulk of the monthly volume.
Which of these loads enters the tunnel?
An HTTP proxy opens a tunnel with CONNECT opens a tunnel with and carries only TCP. No channel speaking over UDP can enter that tunnel. SOCKS5 on the side of UDP ASSOCIATE method can carry UDP, but for that both the proxy server and the game client must support the method; the great majority of mobile game clients do not speak SOCKS5. The practical outcome is this: a proxy mostly covers login, the game API, store pages and download traffic; if there is a channel it does not cover, the game sends it out over your normal line. The limits of the method SOCKS5 UDP support article.
Note
A proxy does not read HTTPS content; it carries encrypted bytes. What it can see is the identity of the target: the hostname you connect to may be recorded on the exit side. Provider choice is therefore as much a trust decision as a technical one.
DIAGRAMThe four traffic layers the client produces
You can scroll the diagram horizontally to inspect it
The layers go to different endpoints and behave differently; a proxy rule may cover only some of them.
Who hosts the world: kingdoms and "private server" claims
In some games you host the world yourself: you download server software, run it on a machine, and invite your friends to your own address. Lords Mobile is not in that class. The world runs on the publisher's infrastructure, the client is only an interface, and you do not choose the address it connects to. For proxies this has a single consequence: a proxy does not select a server address, it only changes your exit.
The in-game concept of a kingdom also lives at the account layer, not the network layer: which kingdom you are in is read from your account record, and changing your exit country does not change that record. Changing kingdom is an operation that can be performed within the game's own interface. Knowing this distinction eliminates most setups that start out with the wrong expectation of a proxy.
The "private server" or modified client packages circulating on the internet are a separate topic and outside the scope of this page: they are not official, they conflict with the terms of service, and entering account details into an application package of unknown origin means handing your credentials to a party you do not know. A proxy is not a tool related to such setups; a network routing setting says nothing about the integrity of the client.
What the community calls a "server" is often the messaging channels where guild chat takes place; those are ordinary web services and can be routed with a normal proxy rule.
Warning
This page was not written for the purposes of running multiple accounts, running automation or defeating the game's protection measures. Compliance with the game's terms of service is the user's responsibility.
A rule written on the router versus a rule written on the device
Most home routers have no "proxy client" field; what you find is usually NAT, a DNS setting and sometimes a VPN client. To apply a proxy to the whole home network you must either run a transparent proxy on the router or redirect traffic to a separate machine on the network. Both are heavy solutions for a home user.
The scope question is also not as broad as assumed. A transparent proxy typically catches TCP, and mostly only destination ports 80 and 443. The game's channels speaking over UDP, connections going to different ports and domain name resolution can fall outside that scope. What is more, in HTTPS traffic an intermediate point can only route by destination without opening the content; if it tries to open it, a certificate warning appears on the client, and that is a sign you should stop and think about.
Where the rule is written
What it covers
Not covered
The practical cost
Router / transparent proxy
TCP web traffic of all devices on the network
UDP channels, different ports, often DNS
Heavy to set up; everyone at home is affected
System-wide operating system setting
All applications that read the setting
Applications that use their own network stack
Update and backup services enter the tunnel too
Wi-Fi network setting (mobile)
Only HTTP proxy traffic on that wireless network
Cellular data, applications that ignore the setting
Silently stops applying when the network changes
Per-application routing
Only the process you select
Other processes and system services
Not available with the same ease on every platform
For a mobile game, router level is usually the wrong tool: the scope is either too broad or misses the channel you were targeting. Staying on the device makes diagnosis easier. For the options, proxy via the router and Android proxy settings is the starting point.
The connection life cycle and the side effect of rotation
A game session is not a single event but a cycle. The connection is established, the channel is carried for a while, at some point it breaks, and the client tries to come back. A proxy touches every step of that cycle; so instead of asking "did it connect", asking "how long does it stay connected" gives a better answer.
The most common mistake is using a rotating exit for gaming. A rotating proxy gives a different address on every request or at short intervals; it is the right tool for distributing load in jobs that read public data at scale. In a game session, however, every rotation breaks the open channel and the client tries to reconnect. In a flow that carries a session, what you need is stability: the same exit address must be held for a certain period. How this structure is set up is explained in the sticky session guide step by step.
The second source of disconnection is the idle timeout: the notification channel may carry no data for a long time, and an intermediate point may treat that as a dead connection and drop it. The symptom appears in the game, but the source is at the network layer. The third source is the device itself; when the phone switches from the wireless network to cellular data, a rule written into the network setting is no longer in effect.
Use a single fixed exit for the game session; do not enable rotation for this job.
Choose a sticky window longer than your typical game session.
Do not run a VPN and a proxy at the same time; two layers make diagnosis impossible.
When you experience a disconnection, first check whether the line has changed, then blame the proxy.
DIAGRAMThe life cycle of a game connection
You can scroll the diagram horizontally to inspect it
A rotating exit forces this cycle to the third step without your noticing; in a session-based flow a fixed exit is preferred.
Choose a fixed exit for your Lords Mobile session
In mobile games that carry a session, it is stability rather than rotation that works; mobile, residential and ISP exits are all managed in the same panel.
Choose whichever you need from our residential proxies, datacenter proxies, IPv6 and ISP solutions. Every plan comes with unlimited options, 99.9% uptime, rotating proxies, sticky sessions and 24/7 support. Ideal for web scraping, ad verification, SEO monitoring and digital data collection.
ISP ProxyStatic Turkish IPs registered to an ISP
ISP-registered static Türkiye IPs; they combine datacenter speed with the reputation of a real carrier. Ideal for long sessions and low-ping use.
Why does the exit silently close on campus and office networks?
Most corporate and campus networks keep egress narrow: 80 and 443 are open for the web, and sessions to the remaining destination ports are dropped at the firewall. If your provider gave you an exit listening on a port such as 1080 or 3128, the same credentials that work fine on your home line never open at all on the corporate network. The symptom is misleading: the error comes from a timeout rather than from authentication, so most users check their password first. What port numbers tell you proxy port numbers are collected in the article.
The second common situation is a login portal: on guest networks the device appears connected, but its traffic lands on a captive page and, because the proxy is unreachable too, the error picture is read incorrectly. The third is corporate-managed devices; the management profile may already have defined a proxy, and a second definition conflicts with it.
The correct order for a solution is this. First confirm that the exit really is up from outside with the proxy checker tool confirm it; if it is not up, the corporate network is not at fault to begin with. If it is up, try the same credentials on a different line: if it opens on your home line but not on the corporate network, the difference in between is an egress filter. At that point the right thing to do is not to try to circumvent the filter, but to ask your provider whether there is an exit option listening on 443 and, if necessary, to talk to your network administrator.
The institution decides what is permitted on its own network; putting your personal device on your own cellular data is in most cases both simpler and a route that consumes no corporate resources at all. The general framework access on school and workplace networks article.
Think of the setup in four steps. First, the protocol: look at which field your client offers, because writing a SOCKS5 exit into a place that only has an HTTP proxy field will not work. The port number alone does not determine the protocol; the same provider can offer both services through one port.
Field
Example value
Description
The server sends
proxy.example.com
The hostname in your panel
Port
8080
A format example only; it does not determine the protocol
Username
username
Required on exits with authentication
Password
password
Taken from the panel, not shared
The second step is the authentication method. IP authorisation is practical in an office with a fixed address; on a mobile device it is fragile, because your cellular address is outside your control and every renewal drops you off the authorised list. A username and password work everywhere, but they are a shareable secret and you need to know where they are stored on the device. The details of the two methods authentication methods article.
The third step is writing the rule at the right point; the scope table is in the previous section. The fourth step is verification, and it is the one step that must not be skipped. From the browser on the same device, your exit address check it; if the address you see is not the proxy's address, the rule is not being applied on that device. There is no way to tell this from inside the game, so always do the verification outside the game.
DIAGRAMThe four steps of setup and the decision at each step
You can scroll the diagram horizontally to inspect it
The steps run in order; setups that skip the verification step keep going out over the normal line while believing they are working.
Latency, transferred data and battery: the measurable cost
A proxy adds an extra hop to your connection: the request goes first to the proxy server, reaches the target from there, and the response returns by the same path. A proxy therefore does not lower ping; the total round-trip time lengthens in most setups. The only exception is the rare case where your default route is unusually circuitous and the proxy sits on a more direct backbone. That is not a rule but an exception that cannot be assumed without measurement.
Because this game's traffic consists of small, frequent requests, the cost accumulates not in bandwidth but in round-trip time. Keeping the exit close to both you and the target reduces that total; choosing an intercontinental exit lengthens every tap.
On the transferred data side, the picture reverses: most of your monthly consumption comes not from the hours you play but from update days. Downloading large patches outside the tunnel is the simplest saving. The third cost is on the battery side; the extra handshakes keep the radio unit awake for longer.
Tip
Before settling on an exit, the ping test run it three times: morning, evening and night. On shared pools, the difference in load during the day is exactly what a single measurement never shows.
Symptom, likely cause, what to check
Symptom
Possible cause
To be checked
The game does not open at all; the screen stays on loading
The proxy is unreachable or the destination port is filtered
Verify that the exit is alive and check the port number
Login works but images are missing
Asset domain names are outside the rule's scope
Check that the rule also covers subdomains
Chat and notifications go quiet after a while
An idle timeout is dropping the open channel
Ask about the timeout duration and the concurrent connection limit
407 Proxy Authentication Required
Credentials are not being sent, or the IP authorisation has lapsed
Verify the username, password and authorised address list
Works on Wi-Fi, does not work on cellular data
The rule was written only for that wireless network
Review the rule's scope and repeat the verification
The interface opens in an unexpected language
The exit country differs from the account's usual country
Match the exit location to your usual country of use
A certificate warning appears
An intermediate point is establishing the TLS session with its own certificate
Do not click past the warning; change the exit and the network
The connection drops after a certain period
The end of the quota or the expiry of the sticky window
Check the remaining quota and session duration in the panel
407 comes from two sources: either the client is not sending the credentials at all, or the provider identifies you by your address and your address has changed. The latter is the rule on mobile; when the cellular line is renewed, you no longer remain on the authorised list.
A certificate warning is a separate category: a correctly configured proxy does not interfere with the TLS session. If you see a warning, your traffic is being decrypted and re-encrypted at some point, and that is a sign you should not continue.
What a proxy does not solve, and when it is not needed
A proxy is not a performance tool. The places to look for in-game latency are different: the line itself, the quality of the wireless network, and the load on the device. Adding an extra hop does not appear on that list.
A proxy is not an account tool either. Your account's kingdom, purchase history and progress are held on the server; the device identity and session token also stay the same no matter which address you go out from.
The cases where it is meaningful are clear: using a fixed and known address when going out from a corporate network, keeping a consistent exit appearance while moving between multiple networks, separating an application's traffic from the local network, or verifying within a compliance framework how a service looks in another market. If you play normally with a single account from your own country, a proxy gives you nothing extra; it only adds latency, cost and one more possible point of failure. For the equivalent of the same logic in other games, game proxy guides .
Frequently asked questions about Lords Mobile and proxies
01Will a proxy improve my latency in Lords Mobile?
Generally no. Because an extra hop is added, the total round-trip time lengthens in most setups; a proxy does not lower ping. If your default route is unusually circuitous the difference can go the other way, but that is not a rule — it is an exception that must be confirmed by measurement.
02Should I write the rule on the router or on the phone?
For a single game, writing it on the phone is almost always better. Setting up a transparent proxy at router level spreads the scope to every device in the home, yet often does not cover UDP channels and different ports at all. Staying on the device also makes diagnosis easier.
03If I change my exit country, will my kingdom change?
No. The kingdom your account belongs to is read from your record on the server side, not from the address you connect from. Changes related to the kingdom are operations that can be performed within the game's own interface and rules; they cannot be forced from the network layer.
04If I use SOCKS5, will all of the game's traffic go through the tunnel?
Not necessarily. SOCKS5's UDP ASSOCIATE method can carry UDP, but both the proxy server and the client must support it. Most mobile game clients do not speak SOCKS5; in that case the scope remains limited to login, API and download traffic.
05Why does the connection time out on a corporate network?
The most common cause is an egress filter: if the network allows only destination ports 80 and 443, a proxy listening on another port never opens at all. Compare whether the same credentials work on a different line; if a difference appears, the party to talk to is your network administrator.
06Is a rotating proxy suitable for gaming?
It is not. Every rotation breaks the open channel and the client tries to reconnect. Rotation is designed for jobs that require no session and read public data; what you need in a game session is a fixed exit held for a certain period.
07Can I play with a free proxy?
Free lists are useful for learning and testing, but are not recommended in a game where you log in. Who operates the server is unknown, stability is low, and disconnections can mean losses in the game. In a flow that carries account information, this risk cannot be quantified.