"Couldn't connect to the server"

Couldn’t connect to the server means Lords Bot could not reach the Lords Bot server at all. It is not a wrong password. Something between your PC and the server is blocking the connection, most often antivirus “web protection”, a firewall or a proxy setting.

How Lords Bot connects #

Lords Bot first connects to gateway.lords-bot.com on port 443 (HTTPS). If that fails, it tries the server’s address on port 80. Your PC, network and firewall must allow outgoing connections on port 443, or at least port 80.

Try these in order #

1. Update Lords Bot. Older versions only used port 80, which some antivirus programs and VPS providers block. Run LordsBotSetup or use Settings > Check for updates if you can reach the main window. See Updates.
2. Check your internet connection. Make sure other websites load on this PC.
3. Add Lords Bot to your antivirus exclusions. Add LordsMobileBot.exe and the whole install folder (by default %LocalAppData%\Lords Bot) to your antivirus exclusions. Many antivirus programs have a separate list for web protection or web shield; add it there too. Avira, Kaspersky, ESET and Avast all have this kind of filter.
4. Try with web protection turned off for a minute. If Lords Bot connects, the antivirus is the cause; keep the exclusions from step 3 and turn protection back on.
5. Try another network, such as a phone hotspot. If it works there, your router, workplace network or provider is blocking the connection.

Check the connection yourself #

Open PowerShell (search for it in the Start menu) and run:

Test-NetConnection gateway.lords-bot.com -Port 443

It should end with TcpTestSucceeded : True. If it says False, a firewall or antivirus on this PC or network is blocking port 443.

netsh winhttp show proxy

This should say Direct access (no proxy server). If a proxy is listed, that proxy may be blocking Lords Bot.

Collect a network log for staff #

If nothing above helps, staff can look at a network log:

1. Close Lords Bot.
2. Open appSettings.json in the install folder with Notepad. Straight after the first {, add a new line with "networkLog": true, (including the comma) and save.
3. Start Lords Bot and try to sign in again.
4. Send the file Logs\network.log from the install folder to staff on Discord.

When you are done, close Lords Bot and remove that line again.

Related messages #

Message	Where	Meaning
You are sending requests too fast, please try again later	Register or Reset Password	You clicked again within 20 seconds. Wait a moment and try again.
Couldn’t start: the login server could not be reached	An account’s log, when starting it	The bot couldn’t reach the Lords Bot server to start the account. Check your connection as above.
Token expired	Sign-in screen	Your PC’s clock is wrong. See Token Expired.

For messages that come back from the server, such as a wrong password, see Sign-In Messages and What They Mean.