Common MU Online server errors and how to fix them
Connect Fail, a GameServer that closes on its own, SQL connection error: diagnose and fix the most common errors.
Every server owner will run into these errors. The good news: most have a known cause. Here's the quick diagnosis guide.
"Connect Fail" on the client
The client can't reach the ConnectServer. Check, in this order:
- Is the server on (ConnectServer running)?
- Is the IP/port in the Main correct?
- Are the ports open in the firewall and router?
- If you use No-IP, is the domain pointing to the right IP?
127.0.0.1 (local). If it works locally but not externally, the problem is network (ports/firewall/No-IP).GameServer closes on its own
The GameServer opens and closes instantly. Common causes:
- SQL/DataServer unreachable (stopped service, wrong password, wrong ODBC);
- Port already in use by another program;
- Config file with a syntax error.
Database connection error
- Is the SQL Server service running?
- Is the authentication mode mixed?
- Does the DSN/ODBC point to the correct database?
- Is the database user's password correct?
Client won't open / file error
- Corrupted or incomplete client files (run the launcher);
- Antivirus blocking the Main (add an exception);
- Missing runtimes (DirectX, Visual C++).
Perguntas frequentes
Why does 'Connect Fail' appear when entering the server?
Usually the client can't reach the ConnectServer: wrong IP/port in the Main, server offline, or ports not opened in the firewall/router.
Why does the GameServer close on its own?
Almost always it's a SQL/DataServer connection failure, a port already in use, or a config file with an error. The GameServer log points to the cause.