Your server host and port information are set up during installation. If they ever change, you’ll need to update the configuration.
For more info on server configuration options, see Installing the Game.
To configure the server:
Table of Contents
These advanced server options will not be needed by every game.
If you want to have your web portal use HTTPS instead of HTTP, you will need to first install a security certificate. CertBot is a really easy way to do this.
server.ymlin the game configuration:
Go to the CertBot website. Select ‘nginx’ for your web server and your server’s version of Ubuntu (usually either 16.04 or 18.04; you will see the version printed in your server shell when you log in.) This will give you the necessary steps to install CertBot.
sudo certbot --nginx.
From the aresmush directory, run
bin/certs YOURHOSTNAME. Again, make sure that the domain name exactly matches the certificate name/MUSH hostname.
Reboot the server. See Rebooting the Server.
Security certificates expire after 90 days. If all went well with your install, CertBot should automatically renew your certificates when they expire. If you get a security warning saying that your certificate is invalid when viewing the web portal, you may need to reboot the server so that the game and web portal recognize the renewed certificate.
bin/devstart command to run the game in dev mode will not work if HTTPS is enabled. Instead you must run the start command manually:
bundle exec rake startares
This feature only applies to the web portal. Ares does not currently support a SSL connection through standard MU clients.
When hosting a game on a host with separate public/private IP addresses (commonly found with AWS) you’ll need to tell the server to start up on the private IP. Do this by setting the
bind_address config option to the private IP.