L2 Server Errors Fix: Seven Install Failures and Their Real Causes

The fastest l2 server errors fix is reading the exception class before you open a config file. A server that dies during boot and a server that boots into an empty world fail in different layers, and the message almost always names the layer: the JVM, the JDBC connection, the login handshake, or the client. The failures below are the ones that come up most often on L2J, L2JMobius and aCis installs. Each entry is the error you see, the thing that actually causes it, and the specific file, port or command that resolves it.
Java Is Not Recognized as a Command
On Windows the shell says java is not recognized as an internal or external command, operable program or batch file. On Linux it says java: command not found. Both mean the same thing: no JDK is installed, or one is installed and neither JAVA_HOME nor PATH points at it. The install guide starts here for a reason. Nothing past this step can work.
Install an OpenJDK build, then point the environment at the JDK root, not at the bin folder inside it.
- Set
JAVA_HOMEto the JDK directory, for exampleC:\Program Files\Eclipse Adoptium\jdk-25. - Add
%JAVA_HOME%\bintoPATHon Windows, or$JAVA_HOME/binon Linux. - Open a new terminal. Environment changes do not reach a shell that was already running.
- Check both commands,
java -versionandjavac -version. If only one works, you installed a JRE and the build will fail later.
Windows has a one-line install if you use winget: winget install EclipseAdoptium.Temurin.25.JDK. Match the major version to your pack before running it, which is the subject of the third section.

The Game Server Dies With a Database Error
The console prints Couldn't init DB connection, or the driver reports Unknown database 'l2jdb', and the process exits a few lines later. The world never starts. There are five ordinary causes and no exotic ones.
- The database name appears twice in the JDBC URL. A URL like
jdbc:mariadb://localhost:3306/l2jdb/l2jdbis parsed as a database namedl2jdb/l2jdb. Keep one segment after the port. - The database name is wrong. L2J ships expecting
l2jdb, but a restored dump or a renamed schema leaves the config pointing at a name that no longer exists. - The user or password is wrong. The account the game server uses is not the MySQL root account. Test with the exact credentials in the config from a client such as HeidiSQL before blaming the server.
- The database was never created. An empty server with no schema fails at the first query. Creating it is a separate step, covered further down.
- The database service is not running. After a reboot, MariaDB or MySQL may be stopped. Start the service and retry before editing anything.
The keys live in different files depending on the pack: config/loginserver.properties and config/server.properties for L2J, dist/game/config/Database.ini for L2JMobius, database.properties for the Docker image. The key names are URL, Login and Password, with User in place of Login on some packs. Fix both the login server and the game server configs; they connect independently and one will happily boot while the other fails.
UnsupportedClassVersionError Means the JDK Does Not Match the Pack
UnsupportedClassVersionError is not a broken download. It means the class files were compiled for a newer Java release than the one running them, or the source expects a newer language level than your JDK provides.
- Official L2JServer currently targets Java 21 or 25. The official installation guide is written against the current LTS line.
- Old L2J and Interlude-era packs target JDK 8. They were written before modules and records, and newer JDKs reject parts of the code.
- aCis depends on the revision: JDK 8 below revision 381, JDK 11 from 381 to 406, JDK 21 from 406 onward. The public repository states the target for the current revision.
Reading the number in the error helps. Major version 52 is Java 8, 55 is Java 11, 61 is Java 17, 65 is Java 21. If the class file is newer than your runtime, install the matching JDK. If it is older and the pack still refuses to run, the pack is asking for a newer one and the build needs recompiling with the correct compiler level. Keeping several JDKs installed and switching JAVA_HOME per pack is normal practice, and the JDK and Eclipse setup guide covers the switching mechanics.

Game Server Missing From the Login Server List
Both processes start, both logs look calm, and the client shows a server list with nothing in it. The game server never registered itself with the login server, so the login server has nothing to announce.
Registration is a tool, not a config value. Run the pack's register-game-server tool, which writes a hexid.txt file. Copy that file into the login server's config folder, next to loginserver.properties, using the same id the tool reported. Restart the login server, then the game server, in that order.
If the file is in place and the server still does not appear, the two processes cannot talk. They use port 9014, and a local firewall rule, a Docker network boundary or a hosting panel can block it between containers or virtual machines even when both are on the same machine. Allow that port between the two, not to the internet.
Ping 9999 and the Server Select Wall
You log in, the server list shows an entry with a ping of 9999 milliseconds, and clicking it returns you to the list. The login worked, so credentials and the database are fine. What failed is the client reaching the game server.
Two things cause it: a hostname the client cannot resolve, or a port the client cannot reach. Check the external and internal hostnames in the config, keyed ExternalHostname and InternalHostname on L2J and under Network.ini on Mobius packs. External is what players connect to, internal is what the login server uses to reach the game server. Setting both to 127.0.0.1 works for a local test and fails for everyone else.
Then open or forward ports 2106 and 7777. The L2J README states the same solution in one line:
Set up your IP's properly, forward/open good ports if accessing from outside.
A server behind NAT needs the public address in the external hostname and a forward for both ports. A server on a VPS usually needs the hosting firewall opened, not just the OS one. The game and login server configuration guide goes through the hostname keys one by one.
The World Loads Empty
The server boots, the client connects, and the world has no NPCs, no item templates and no spawns. Nothing is broken: the schema was never installed, or only part of it was. Tables that the loaders expect are missing and the loaders skip them quietly.
Run the pack's database installer before the first start.
- L2J:
l2jcli.bat db install -sql <path> -u <user> -p <pass> -m FULL -t LOGINand then the same command with-t GAME. The login and game schemas are separate. - Older packs:
database_installer.shordatabase_installer.batinside thetoolsfolder.
Partial installs are common when the SQL path is wrong or the installer stops on the first error. Watch its output to the end rather than assuming it finished, then check that the game database actually has tables in it.
Ports and the Client Hosts File
Four ports decide whether an install works. Only two of them belong on a public interface, and the database port on none.
| Port | Purpose | Exposure |
|---|---|---|
| 2106 | Login server, client connections | Public |
| 7777 | Game server, client connections | Public |
| 9014 | Login server to game server | Private, between the two processes only |
| 3306 | MySQL or MariaDB | Never public |
Exposing 3306 is the single most common security mistake on a Lineage 2 host. Nothing outside the machine needs it, and an internet-facing database port gets scanned within hours. Bind the database to localhost and let only the server processes use it. MariaDB installers live at mariadb.org; the database setup guide covers users and binding.
On the client side, the game resolves l2authd.lineage2.com. Point that name at your server with a hosts entry, or launch l2.bin IP=<address> directly. Two mistakes break this repeatedly on Windows: the file is saved as hosts.txt, which Windows ignores because there is no extension, and the entry points at an address the client cannot route to. Confirm the file has no extension and edit it as administrator.
Config Files That Fail to Parse on Windows
Some packs refuse to start with no readable error at all, or print a parse failure on a line that looks correct. The usual cause is the file encoding. Save an L2J .properties file as UTF-8 with a byte order mark after a Notepad save and the loader can choke on the first non-ASCII byte, because the BOM is read as part of the first key.
To confirm, check the first three bytes of the file. A BOM starts with EF BB BF. Save without it, keep values plain ASCII, and re-run the server. Config files are also case-sensitive on Linux, so a path that works on Windows can fail on the host.
Quick Reference
The core failures, compressed for the moment you are staring at a console:
| Error | Real cause | Fix |
|---|---|---|
| java is not recognized | No JDK, or PATH and JAVA_HOME not set | Install the JDK, set JAVA_HOME to the JDK root, add its bin to PATH |
| Couldn't init DB connection | Wrong URL, wrong credentials, missing database, service stopped | Fix the URL, Login and Password keys in the game and login configs |
| UnsupportedClassVersionError | JDK newer or older than the pack expects | Install the JDK the pack targets and rebuild |
| Empty server list, or ping 9999 | No hexid.txt, or hostnames and ports not reachable | Register the game server, then open 2106 and 7777 |
| Empty world | Schema never installed or partially installed | Run the pack database installer for both LOGIN and GAME |
Work top to bottom. Each failure hides the next one: a server cannot report a database error until the JVM runs, and it cannot register with the login server until the database connects. Fixing them out of order produces new errors that look unrelated.
When the install is finally stable and the server is ready for players, add it through the free listing form, or take VIP placement to sit ahead of the queue in the server directory.
