This guide walks you through launching Rustmail and verifying your setup.
From your installation directory:
./rustmailOn Windows:
rustmail.exeOn successful startup, you will see:
[INFO] Database connection pool established
[INFO] Database connected!
[INFO] Starting rustmail...
[INFO] listening on 0.0.0.0:3002
[INFO] Configuration successfully validated!!
[INFO] Mode: Mono server (ID: 711880297272311856)
[INFO] Rustmail is online !
[INFO] All pending reminders have been scheduled.
[INFO] Updated 0 ticket statuses
If there are configuration errors, the bot will display specific messages indicating what needs to be fixed.
In Discord, verify the bot appears online in your server's member list. Its status should display the text you
configured in bot.status.
In any channel where the bot has access:
- Type
/helpand press Enter - The bot should respond with a list of available commands
If slash commands don't appear:
- Wait a few minutes (Discord caches command registrations)
- Verify the bot has the
applications.commandsscope - Check that the bot has permissions in the channel
- Send a direct message to the bot
- The bot should:
- Reply with your configured
welcome_message - Create a new channel in your inbox category
- Reply with your configured
- Staff can now respond using
/replyor!replyin the ticket channel
Open your browser and navigate to:
- Local:
http://localhost:3002 - With reverse proxy:
https://your-panel-domain.com
Click Login to authenticate with Discord.
Failed to parse config.toml: ...
Check your config.toml for:
- Missing required fields
- Incorrect TOML syntax (missing quotes, brackets)
- Invalid color hex codes (should be 6 characters without
#)
Main server not found: ...
Verify:
- The guild IDs in your configuration are correct
- The bot has been invited to all configured servers
- You're using the server ID, not a channel or user ID
'logs_channel_id' field is required if 'enable_logs' is true
Either:
- Set
enable_logs = falseto disable logging - Or provide a valid
logs_channel_id
The same applies to enable_features and features_channel_id.
If the panel login fails:
- Verify
client_idandclient_secretmatch your Discord application - Ensure
redirect_urlexactly matches what's configured in Discord Developer Portal - Check that your application has the OAuth2 redirect URI added
For production, run Rustmail as a background service.
Create /etc/systemd/system/rustmail.service:
[Unit]
Description=Rustmail Discord Bot
After=network.target
[Service]
Type=simple
User=rustmail
WorkingDirectory=/opt/rustmail
ExecStart=/opt/rustmail/rustmail
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.targetEnable and start:
sudo systemctl daemon-reload
sudo systemctl enable rustmail
sudo systemctl start rustmailView logs:
sudo journalctl -u rustmail -fSee Docker Deployment for containerized operation.
Your bot is now running. Learn more about: