Remote Access

Kargatum edited this page Apr 24, 2018 · 4 revisions


Azerothcore has 4 ways of interfacing with the world server.

  • In Game
  • The Console
  • Telnet (RA)

The in game menus and the console are pretty self explanatory, however you are not always able to administer the server locally nor do the first two options provide many opportunities for automation. If you want to provide a way to access your server remotely, or let software manage it then you have two options.

Choosing the Correct Protocol

Remote Access

Remote access is basically a telnet connection and has all of the downsides a telnet connection brings. These would be:

  • Data is sent over cleartext which can be intercepted easily.
  • You use distinct sessions, meaning you open and close a connection each time.
  • It can be difficult to parse the return since it just returns what you would see in the CLI

However, it has upsides as well, namely:

  • It is simple with little overhead.
  • It is well established and documented.
  • Platform independent.

Remote access is good for running on a local server, and accessing it securely over SSH to send it commands. Its simplicity is its strength. On top of that it is built in to most machines without any configuration needed.


It stands for simple object access protocol and is a format for sharing structured data between machines. It is a common xml analogue to ReST and json, and lets two pieces of software interact with each other despite running on different code bases, languages, and operating systems. Lets get on to the weaknesses.

  • No default encoding meaning that you can get away with almost anything. Some people may see it as a bonus but it can be confusing.
  • Little security

And its strengths.

  • XML is a well established format supported in most programming languages.
  • Uses standard HTTP

In a more simplified format: SOAP for websites, telnet for command line.

Using the Protocol of Choice


  1. Both protocols must be enabled via the worldserver config files.
  2. When they are enabled, in order to authorize access to the database, you need to find the account_access table in the auth database and make sure the realmID of your user is -1 (meaning all realms).
  3. When that is done you are set up to use telnet and SOAP



Due to it's ubiquity telnet is easy to use from almost anywhere.

  1. open up a terminal session (or PuTTY) and type in telnet {{ ip }} {{port}}
  2. Enter your username and password.


Soap works using POST requests on the HTTP protocol. If you are using php for your server, these is a module that will create and send SOAPs for you, namely:

$conn = new SoapClient(NULL, array(
    'location' => "http://{{ ip }}:{{ port }}/",
    'uri'      => 'urn:TC',
    'style'    => SOAP_RPC,
    'login'    => '{{ username }}',
    'password' => '{{ password }}'
echo $conn->executeCommand(new SoapParam('server info', 'command'));

However if you are not using php, it's a little more complicated. Or, it was before this documentation showed up! To create a valid soap request you need to include the appropriate xml namespaces. These were taken directly from the ones the server itself uses. You can see the SOAP itself is taken from the SOAP-ENV schema. Under the ns1 namespace are the commands we need to interact with the server. All commands go in the body of the SOAP. To send a command, you call the function executeCommand in the ns1 namespace and send the parameter command to the server. In this case our command gets the server status.

 			<command>server status</command>

The response to this command is what you would expect from the terminal.

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.