Skip to content
Back to Homepage

Return to Moria Server Troubleshooting

This guide covers common issues when running a Return to Moria server on AleForge. AleForge handles port forwarding and DDoS protection for you, so most connection problems come down to server state, credentials, or save files.

  1. Confirm the server is running and fully started on the Console page
  2. Wait for the join code or IP and port to appear on the Dashboard
  3. Double-check you are using the correct join method, see Connect to your server
  4. If a server password is set, enter it exactly (passwords are case-sensitive)
  5. Verify you are not exceeding the 8-player simultaneous connection limit
  6. Confirm all players own required DLC if Durin’s Folk is enabled on the world
  • Copy the join code fresh from the Dashboard after each server restart
  • If the code was regenerated, use regenerateinvitecode in the Console and restart, see Console Commands
  • Try direct connect with IP and port instead, see Connect to your server

The official known issue notes that dedicated servers can hang during world load. On AleForge:

  1. Open the Console page
  2. Click into the console output area
  3. Press any key

The world should continue loading immediately.

  1. Confirm the .sav file is in Moria/Saved/SaveGamesDedicated
  2. Verify World Name on Startup matches the save filename without the .sav extension
  3. If you have multiple saves with the same world name, set OptionalWorldFilename in Game Config to the exact .sav filename, see Upload a save
  4. Stop the server before uploading or editing save files
  • Lower Loaded Area Limit on Startup (try 8 for small groups)
  • Set Server FPS to 60 or 30, see Optimize your server
  • Reduce the number of simultaneously connected players
  • Run unblock [playername] in the Console, or remove Blocked from their entry in MoriaServerPermissions.txt while the server is stopped
  • See Kick or block players
  1. Restart the server from the Console page
  2. Restore from a backup if a save was corrupted
  3. Contact AleForge support with your server ID and any Console output