Sometimes things go wrong, and you’ll get the “Sorry! The code lost its mind while executing a command…” message or the Sad Picard screen on the web portal. This article will help you diagnose the problem.
If the information below doesn’t help you, you can always ask for help on the Ares Forums.
Table of Contents
The first place to check is the game log. This will help you pinpoint the exact file and line number where the code failed. See Using Log Files for help.
For tricky issues - especially during development - it can be helpful to run the game in Debug Mode.
The configuration files use YAML, and there are several common issues that can result from trouble with your game configuration. Often you’ll see an error message like “Error reading YAML from fs3combat.yml…”, but any error that happens right after you changed your game configuration should make you suspect a YAML problem. See Troubleshooting YAML for more details.
Sometimes you’ll get a ‘connection refused’ error in your MU client or a ‘This site can’t be reached’ error in your web browser. When this happens, there are a few things to check:
bin/devstartinstead of startares. This will run until you hit CTRL-C, and you will see log messages live on your screen.
If your game can’t connect to the database you’ll see an error like: “Error connecting to database. Check your database configuration.” Here are a few things to try:
service redis-server status.
If you get a ‘page not found’ error for your web portal, here are some things to check:
service nginx status.
/var/www/html. You should see index.html and other files there.
server.yml. In nginx, this site configuration should be in
Sometimes you’ll get a Sad Picard message saying the web portal can’t connect to the game.
Make sure there’s a symbolic link from your web portal directory to your game directory. If you do
ls -l in your
/var/www/html directory, you should see an entry like this:
ares ares 24 Apr 2 01:01 game -> /home/ares/aresmush/game