Online Setup

Evennia development can be made also without any internet connection (except to download updates). At some point however, you are likely to want to make your game visible online, either as part of making it public or to allow other developers or beta testers access to it.

Settings for allowing external connections

By default Evennia will only allow connections from your own computer (localhost, the IP address To make it available to the outside world you need to make some changes to your settings file. To have Evennia recognize changed port settings you have to do a full stop of the server (not just a reload), via evennia stop before starting again.

Below is an example of a new section added to the settings. For a common setup, Evennia will require access to five computer ports, of which three (only) should be open to the outside world.

# in mygame/server/conf/


# open to the internet: 4000, 4001, 4005
# closed to the internet (internal use): 4002, 4006
WEBSERVER_PORTS = [(4001, 4002)]
AMP_PORT = 4006

# security measures (optional)

# uncomment to take server offline

# Register with game index (see for first setup)
    'game_status': 'pre-alpha',
    'game_website': '',
    'listing_contact': '',
    'telnet_hostname': '',
    'telnet_port': 4000,
    'short_description': "The official Mygame.",
    'long_description':'Mygame is ...'

When running, an external user should be able to connect with a telnet client to host and port 4000 and use a web browser to connect to (in this example also appears to be set up to point to that IP). If connecting does not work, try turning off the _INTERFACES optional security settings first. If that still doesn’t work, examine your firewall.

Read on for a description of the settings.


# Required. Change to whichever outgoing Telnet port(s)
# you are allowed to use on your host.
# Optional for security. Restrict which telnet
# interfaces we should accept. Should be set to your
# outward-facing IP address(es). Default is ´´
# which accepts all interfaces.

The TELNET_* settings are the most important ones for getting a traditional base game going. Which IP addresses you have available depends on your server hosting solution (see the next sections). Some hosts will restrict which ports you are allowed you use so make sure to check.

Web server

# Required. This is a list of tuples
# (outgoing_port, internal_port). Only the outgoing
# port should be open to the world!
# set outgoing port to 80 if you want to run Evennia
# as the only web server on your machine (if available).
WEBSERVER_PORTS = [(4001, 4002)]
# Optional for security. Change this to the IP your
# server can be reached at (normally the same
# Optional for security. Protects against
# man-in-the-middle attacks. Change  it to your server's
# IP address or URL when you run a production server.
The web server is always configured with two ports at a time. The outgoing port (4001 by default) is the port external connections can use. If you don’t want users to have to specify the port when they connect, you should set this to 80 - this however only works if you are not running any other web server on the machine.
The internal port (4002 by default) is used internally by Evennia to communicate between the Server and the Portal. It should not be available to the outside world. You usually only need to change the outgoing port unless the default internal port is clashing with some other program.

Web client

# Required. Change this to the main IP address of your server.
# Optional and needed only if using a proxy or similar. Change
# to the IP or address where the client can reach
# your server. The ws:// part is then required. If not given, the client
# will use its host location.
# Required. Change to a free port for the websocket client to reach
# the server on. This will be automatically appended
# to WEBSOCKET_CLIENT_URL by the web client.

The websocket-based web client needs to be able to call back to the server, and these settings must be changed for it to find where to look. If it cannot find the server you will get an warning and the client will revert to the AJAX-based (much simpler) version of the client instead.

With these changes in place, the server should be ready to accept external connections.

Other ports

# Required. But you should only change this if there is a clash
# with other services on your host. Should NOT be open to the
# outside world.
AMP_PORT = 4006
# Optional, only if you allow SSH connections (off by default).
SSH_PORTS = [4004]
# Optional, only allow SSL connections (off by default).
SSL_PORTS = [4003]

The AMP_PORT is required to work, since this is the internal port linking Evennia’s Server and Portal components together. The other ports are encrypted ports that may be useful for custom protocols but are otherwise not used.

Lockdown mode

When you test things out and check configurations you may not want players to drop in on you. Similarly, if you are doing maintenance on a live game you may want to take it offline for a while to fix eventual problems without risking people connecting. To do this, stop the server with evennia stop and add LOCKDOWN_MODE = True to your settings file. When you start the server again, your game will only be accessible from localhost.

Registering with the Evennia game directory

Once your game is online you should make sure to register it with the Evennia Game Index. Registering with the index will help drum up interest for your game and also shows people that Evennia is being used. It’s a convenient place to reference your game from (if you don’t have a fancy URL set up yet). You don’t need to have a fully-fledged production game to go on the game index. If it’s very rough just set the development status to “pre-alpha”.

In the example settings snippet above is an example registry entry you can modify for your game. To activate the directory client you also need to add three lines to mygame/server/conf/

# in mygame/server/conf/`

from evennia.contrib.egi_client import EvenniaGameIndexService  # ADD

def start_plugin_services(server):
    This hook is called by Evennia, last in the Server startup process.

    server - a reference to the main server application.
    egi_service = EvenniaGameIndexService()  # ADD  # ADD

Once that’s in place, just restart your game. See the EGI client documentation for more info.

Using your own computer as a server

By far the simplest and probably cheapest option. Evennia will run on your own home computer. Moreover, since Evennia is its own web server, you don’t need to install anything extra to have a website.


  • Free (except for internet costs and the electrical bill).
  • Full control over the server and hardware (it sits right there!).
  • Easy to set up.
  • Also suitable for quick setups - e.g. to briefly show off results to your collaborators.


  • You need a good internet connection, ideally without any upload/download limits/costs.
  • If you want to run a full game this way, your computer needs to always be on. It could be noisy, and as mentioned, the electrical bill must be considered.
  • No support or safety - if your house burns down, so will your game. Also, you are yourself responsible for doing regular backups.
  • Potentially not as easy if you don’t know how open ports in your firewall or router.
  • Home IP numbers are often dynamically allocated, so for permanent online time you need to set up a DNS to always re-point to the right place (see below).

Setting up your own machine as a server

Making Evennia available from your own machine is mainly a matter of configuring eventual firewalls to let Evennia’s communication through. With Evennia running, note which outgoing ports it is using. Default ports are 4000 for telnet, 4001 for the website and port 4005 for the websocket-based client. Note that if the websocket port is not open, Evennia will fall back to the website port and use a less able version of the client. We assume the defaults below.

  1. Go to (or similar site). They should tell you which IP address you are connecting from, let’s say it is 230.450.0.222.
  2. In your web browser, go to http://230.450.0.222:4001, where the last :4001 is the webclient port Evennia uses. If you see Evennia’s website and can connect to the webclient - -congrats, you are almost there! Click on the webclient link. Next try to connect with a traditional MUD-client to the telnet port.
  3. Most likely your ports won’t work straight off though. This is probably because you have a firewall blocking the ports we need. How to open the right ports in your software firewall is something you need to look up in the manual for your firewall. There could also be a hardware-router between your computer and the Internet - in that case the IP address we see “from the outside” is actually the router’s IP, not that of your computer on your local network. The router has ports of its own that need to be opened.
  • If your computer’s software firewall is blocking Evennia’s outgoing ports, you need to open those ports in your firewall software. Please refer to the manual/helpfile for your firewall on how to do this.
  • If you are (maybe in addition to a software firewall) using a hardware router/firewall, this has its own internet-facing IP and ports. Exactly how to configure it is again depending on brand and version. In principle you should look for something called “Port forwarding” or maybe “Virtual server”. You want to route Evennia’s outgoing ports 4000/4001/4005 from your computer to equivalent “router outgoing ports” that the world can see. The router’s outgoing ports do not have to have to have the same port numbers as evennia’s outgoing ports! For example, you might want to connect evennia’s outgoing port 4001 to an outgoing router port 80 - this is the port HTTP requests use and web browsers automatically look for. If you use port 80 you won’t have to specify the port number in the url of your browser. This would collide with any other web services you are running through this router though.
  • For some hardware routers you have to reboot the router for the firewall changes to to take effect. It’s worth a try if your changes doesn’t seem to come into effect.
  1. At this point you should be able to invite people to play your game on http://230.450.0.222:4001 or via telnet to 230.450.0.222 on port 4000.

A complication with using a specific IP address like this is that your home IP might not remain the same. Many ISPs (Internet Service Providers) allocates a dynamic IP to you which could change at any time. When that happens, that IP you told people to go to will be worthless. Also, that long string of numbers is not very pretty, is it? It’s hard to remember and not easy to use in marketing your game. What you need is to alias it to a more sensible domain name - an alias that follows you around also when the IP changes.

  1. To set up a domain name alias, we recommend starting with a free domain name from FreeDNS. Once you register there (it’s free) you have access to tens of thousands domain names that people have “donated” to allow you to use for your own sub domain. For example, is one of those available domains. So tying our IP address to using the subdomain evennia would mean that one could henceforth direct people to for their gaming needs - far easier to remember!

  2. So how do we make this new, nice domain name follow us also if our IP changes? For this we need to set up a little program on our computer. It will check whenever our ISP decides to change our IP and tell FreeDNS that. There are many alternatives to be found from FreeDNS:s homepage, one that works on multiple platforms is inadyn. Get it from their page or, in Linux, through something like apt-get install inadyn.

  3. Next, you login to your account on FreeDNS and go to the Dynamic page. You should have a list of your subdomains. Click the Direct URL link and you’ll get a page with a text message. Ignore that and look at the URL of the page. It should be ending in a lot of random letters. Everything after the question mark is your unique “hash”. Copy this string.

  4. You now start inadyn with the following command (Linux):

    inadyn --dyndns_system -a <my.domain>,<hash> &

where <my.domain> would be and <hash> the string of numbers we copied from FreeDNS. The & means we run in the background (might not be valid in other operating systems). inadyn will henceforth check for changes every 60 seconds. You should put the inadyn command string in a startup script somewhere so it kicks into gear whenever your computer starts.

Remote hosting

Your normal “web hotel” will probably not be enough to run Evennia. A web hotel is normally aimed at a very specific usage - delivering web pages, at the most with some dynamic content. The “Python scripts” they refer to on their home pages are usually only intended to be CGI-like scripts launched by their webserver. Even if they allow you shell access (so you can install the Evennia dependencies in the first place), resource usage will likely be very restricted. Running a full-fledged game server like Evennia will probably be shunned upon or be outright impossible. If you are unsure, contact your web hotel and ask about their policy on you running third-party servers that will want to open custom ports.

The options you probably need to look for are shell account services, VPS:es or Cloud services. A “Shell account” service means that you get a shell account on a server and can log in like any normal user. By contrast, a VPS (Virtual Private Server) service usually means that you get root access, but in a virtual machine. There are also Cloud-type services which allows for starting up multiple virtual machines and pay for what resources you use.


  • Shell accounts/VPS/clouds offer more flexibility than your average web hotel - it’s the ability to log onto a shared computer away from home.
  • Usually runs a Linux flavor, making it easy to install Evennia.
  • Support. You don’t need to maintain the server hardware. If your house burns down, at least your game stays online. Many services guarantee a certain level of up-time and also do regular backups for you. Make sure to check, some offer lower rates in exchange for you yourself being fully responsible for your data/backups.
  • Usually offers a fixed domain name, so no need to mess with IP addresses.


  • Might be pretty expensive (more so than a web hotel). Note that Evennia will normally need at least 50MB RAM and likely much more for a large production game.
  • Linux flavors might feel unfamiliar to users not used to ssh/PuTTy and the Linux command line.
  • You are probably sharing the server with many others, so you are not completely in charge. CPU usage might be limited. Also, if the server people decides to take the server down for maintenance, you have no choice but to sit it out (but you’ll hopefully be warned ahead of time).

Installing Evennia on a remote server

Assuming you know how to connect to your account over ssh/PuTTy you should be able to follow the Getting Started instructions normally. You only need Python and GIT pre-installed; these should both be available on any servers (if not you should be able to easily ask for them to be installed). On a VPS or Cloud service you can install them yourself as needed.

If virtualenv is not available and you can’t get it, you can download it (it’s just a single file) from the virtualenv pypi. Using virtualenv you can install everything without actually needing to have further root access. Ports might be an issue, so make sure you know which ports are available to use.

Hosting options

To find commercial solutions, browse the web for “shell access”, “VPS” or “Cloud services” in your region. You may find useful offers for “low cost” VPS hosting on Low End Box. The associated Low End Talk forum can be useful for health checking the many small businesses that offer “value” hosting, and occasionally for technical suggestions.

There are all sorts of services available. Below are some international suggestions offered by Evennia users:

Hosting name | Type | Lowest price | Comments
——————-|:————–:|:——-:|—————- | Shell account | Free for MU* | Private hobby provider so don’t assume backups or expect immediate support. To ask for an account, connect with a MUD client to, port 4201 and ask for “Jarin”.
Digital Ocean | VPS | $5/month | Please consider using the referral link You will get a $10 credit - and once you have paid $25 we will get that as a referral bonus to help Evennia development.
Amazon Web services | Cloud | ~$5/month / on-demand | Free Tier first 12 months. Regions available around the globe.
Amazon Lightsail | Cloud | $5/month | Free first month. AWS’s new “fixed cost” offering.
Genesis MUD hosting | Shell account | $8/month | Dedicated MUD host with very limited memory offerings. Note that Evennia needs at least the “Deluxe” package (50MB RAM) and probably a lot higher for a production game, so be very careful about choosing this host for Evennia.
Host1Plus | VPS & Cloud | $4/month | $4-$8/month depending on length of sign-up period.
Scaleway | Cloud | €3/month / on-demand | EU based (Paris, Amsterdam). Smallest option provides 2GB RAM.
Prgmr | VPS | $5/month | 1 month free with a year prepay. You likely want some experience with servers with this option as they don’t have a lot of support.
Linode | Cloud | $5/month / on-demand | Multiple regions. Smallest option provides 1GB RAM
Please help us expand this list.


If you are interested in running Evennia in the online dev environment Cloud9, you can spin it up through their normal online setup using the Evennia Linux install instructions. The one extra thing you will have to do is update mygame/server/conf/ and add WEBSERVER_PORTS = [(8080, 4001)]. This will then let you access the web server and do everything else as normal.


SSL can be very useful for web clients. It will protect the credentials and gameplay of your users over a web client if they are in a public place, and your websocket can also be switched to WSS for the same benefit. SSL certificates used to cost money on a yearly basis, but there is now a program that issues them for free with assisted setup to make the entire process less painful.

Let’s Encrypt

Let’s Encrypt is a certificate authority offering free certificates to secure a website with HTTPS. To get started issuing a certificate for your web server using Let’s Encrypt, see these links:

Also, on Freenode visit the #letsencrypt channel for assistance from the community. For an additional resource, Let’s Encrypt has a very active community forum.

A blog where someone sets up Let’s Encrypt

The only process missing from all of the above documentation is how to pass verification. This is how Let’s Encrypt verifies that you have control over your domain (not necessarily ownership, it’s Domain Validation (DV)). This can be done either with configuring a certain path on your web server or through a TXT record in your DNS. Which one you will want to do is a personal preference, but can also be based on your hosting choice. In a controlled/cPanel environment, you will most likely have to use DNS verification.