Help Center

Start with the dashboard

Most configuration problems are easier to diagnose from the dashboard because you can see the selected server, channels, roles and module settings together. Confirm that you are logged into the Discord account that actually has Manage Server or Administrator permission.

Bot permissions

If a feature cannot send messages, create ticket channels, manage roles or delete messages, check Eclipse's server role and its channel overwrites. Discord role hierarchy matters: Eclipse cannot manage a role positioned above its own role.

Commands not appearing

Slash commands are registered through Discord and can take time to refresh after a deployment. If only one command is missing, check that it is present in the current bot build. If every command fails, verify that the bot is online and that the current Discord application is the one connected to the deployed token.

Dashboard login

The dashboard uses Discord OAuth2. If login returns a redirect error, confirm that the exact production callback URL is configured in the Discord Developer Portal. For this deployment the intended callback is https://www.eclipsedashboard.com/callback.

Getting human help

If you still need help, use the Discord icon in the footer to open the Eclipse support server. When reporting a problem, include what feature you were using, what you expected, what actually happened and any relevant Railway log error. Never post your bot token, OAuth secret or session secret.