Troubleshooting

From ArcEmu-Wiki
Jump to: navigation, search

<stub>

This page tries to help with some common problems.


Contents

Problems observed on the client side

You are getting "Unable to connect" or "Login server down" error message when trying to log in

Possible causes

  • Your network is malfunctioning
  • The logon server is not running
  • You've changed the login server's listening port, but the client is still trying to connect to the old one
  • A firewall is blocking your connection, either client side or server side
  • The login server is behind NAT ( Network Address Translation ) ( most of the times a router ), and the ports are not forwarded.


Solution

  • Fix your network
  • Start the logon server if it's not running
  • Modify the realm list setting of the client to match the current settings


NOTE:
Example:

If you changed the logon port to 1337, then instead of

set realmlist 127.0.0.1

write

set realmlist 127.0.0.1:1337



  • Make sure your firewall allows traffic on the logon port for both the client and the server


NOTE:
The default port of the logon server is 3724.


  • Make sure that this port is forwarded if the server is behind a router, or another NAT solution

You are getting "Unable to validate game version" error message when trying to log in

Cause

  • The client's version doesn't match the version supported by your copy of Arcemu.


Solution

  • Upgrade / downgrade your wow client to match the Arcemu version.



You are getting stuck on "Handshaking" when trying to log in

Possible causes

  • The client's version doesn't match the version supported by your copy of Arcemu


Solution

  • Upgrade / downgrade your wow client to match the Arcemu version.




You are getting an empty realm list after logging in

Possible causes

  • The world server is not running
  • The world server couldn't connect to the logon server
    • The world server is misconfigured and tries to connect to the wrong address and/or port
    • The world server is not allowed to connect to the logon server


  • The world server couldn't authenticate with the logon server
    • The world server and logon server have different remote password settings


Solution

  • Start the world server if it's not running
  • Make sure the world server tries to connect to the logon server on the right address and port.


NOTE:
You can set the logon server's inter-server connection listen settings in the logon.conf file, in the 'ISHost' and 'ServerPort' variables.


NOTE:
You can set the world server's link to the logon server in the realms.conf file, in the 'LogonServer Address' and 'Port' variables.


  • Make sure the world server is allowed to connect to the logon server


NOTE:
You can set the allowed server connection IPs in the logon.conf file, in the 'AllowedIPs' and 'AllowedModIPs' variables.


  • Make sure the world server can authenticate with the logon server.


NOTE:
You need matching remote password in the world.conf and logon.conf files for this.



You keep getting back to the realm list after selecting a realm ( also called realm loop )

Possible causes

  • The connection is blocked by a firewall on either the server or client side
  • The world server is behind NAT ( Network Address Translation ) ( most of the times a router ), and the ports are not forwarded.
  • The world server is behind NAT ( Network Address Translation ) ( most of the times a router ), and you are trying to connect from the inside.


Solution

  • Make sure the firewall allows traffic on the world server port on both the client and server.


NOTE:
The default port of the world server is 8129


  • Make sure to forward this port if necessary.
  • If the server is behind a NAT device, make sure to connect using a DNS address, and that the DNS address is resolved to the LAN address of the server.


NOTE:
You can do this by adding an entry to the client's hosts file, that locally resolves the DNS address to the LAN address of the server

You keep getting disconnected when creating a new character

Cause

  • The playercreateinfo tables in the world database are either corrupted or empty


Solution

  • If the tables are not empty, re-import your world database
  • If the tables are empty, get a new database which has those tables


You try to enter the world, but get stuck on the loading screen

Cause

  • The `worldmap_info` table in the world database is either empty or it is missing some data


Solution

  • If the table is not empty, re-import your world database
  • If the table is empty, get a new database which has that table



Problems observed on the server side

You are getting 'Could not open xyz.conf' error message when trying to start up the server

Cause

  • The server cannot find or access the config files
  • Sometimes the comments in the .conf files will cause this


Solution

  • Make sure to have the config files in the right folder.


NOTE:
Config files on Windows go to the directory 'configs', on other platforms they go to the directory 'etc' within the Arcemu installation directory.


  • Make sure the files have access rights set in a way that the server can access them.
  • If even after these you get the error, try to remove the so called comment lines from the files


NOTE:
Lines starting with a # character or text blocks starting with a /* and ending with a */ pairs are comment lines



You are getting 'Connection failed due to: `ERROR`' message when trying to start up

Cause

  • The database settings are misconfigured in either logon.conf or world.conf
  • If the database server is on a remote host, a firewall might be blocking the connection
  • The database server software is not running
  • The database server software is configured not to allow remote connections


Solution

  • Make sure your database settings are correct according to your database server.


NOTE:
You can find the Arcemu database settings in the "<LogonDatabase" directive of logon.conf and in the "<WorldDatabase", "<CharacterDatabase" directives of world.conf.


  • Make sure to allow the database server's host and the database server to accept connections from the logon server and world server.
  • Make sure the database server software is running.
Personal tools