Common Issues

A list of issues people might commonly have!

Problem not solved after checking here? Let us know in our Support Server!

Bot Related

My Bot Crashes Immediately

Your Configuration is not complete

You may have forgotten to fill some information in the common.json file. It's mandatory to fill in every space in that file!

Guild Not Whitelisted

You may have forgotten to add your Guild to the whitelist required with your license!

Make sure to run /guild whitelist in our Support Server!

IP Not Whitelisted

You may have forgotten to add your IP to the whitelist required with your license!

Make sure to run /ip whitelist in our Support Server!

---

Antivirus Related

My Antivirus Quarantined Files

Microsoft Defender and potentially some other Anti-Malware services are flagging the obfuscated code with emojis in them! These are not malicious files but they're being quarantined/removed by accident. You can restore the files through whatever software solution you're using to get the files back in place, they do not contain malicious code!

---

Command Related

My Commands aren't working

Forgot to configure Permissions

You need to make sure all permissions are assigned in the permissions.json file, both the roles and IDs, as well as the permission levels each of them get!

Developer Mode is Enabled

This can cause commands to not show up! Make sure that developer-mode is disabled in the common.json file.

A Plugin might have crashed

Check to see if you don't have errors coming up in your console for plugins! If plugins disable, they'll disable any associated commands too.

Server or Bot ID may be incorrect

Check to see if your Server/Bot ID are wrong by accident. Your bot needs the right value. If either of them are wrong, your bot will not know what it's trying to connect to.

---

MongoDB Related

My Bot Crashes During Startup

MongoDB Firewall

MongooseError: Operation users.findOne() buffering timed out after 10000ms
    at Timeout. (C:\Users\khyek\crossfit-wod-api\node_modules\mongoose\lib\drivers\node-mongodb-native\collection.js:187:23)
    at listOnTimeout (node:internal/timers:594:17)
    at process.processTimers (node:internal/timers:529:7)

If you encounter this error, make sure to add your host's IP address to your database's IP allowlist (whitelist). Alternatively, you can allow connections from any IP by adding 0.0.0.0/0 to the allowlist. A guide to that is here!

If and only if that did not resolve the issue, make sure your MongoDB connection string contains a database name. Some MongoDB setups require a database name to be specified. If it is missing, Mongoose may fail to connect and you'll receive the same error. ✅ Correct

mongodb+srv://<credentials>@cluster.mongodb.net/athenabot?retryWrites=true&w=majority&appName=YourCluster

❌ Incorrect

mongodb+srv://username:<PASSWORD>@cluster.mongodb.net?retryWrites=true&w=majority&appName=YourCluster

Notice the /athenabot after .mongodb.net/. If you don't have a database yet, you can use any name. MongoDB Atlas will automatically create it the first time AthenaBot stores data.

MongoDB Connection

[ERR] | ERROR REPORT
[ERR] | * Error: querySrv ECONNREFUSED _mongodb._tcp.cluster0.gpitjxx.mongodb.net
[ERR] | * Type: Javascript
[ERR] | * ID: as7mf0
[ERR] | * Impact: critical
[ERR] |
[ERR] | Error Information
[ERR] | * Registered error: ✅
[ERR] | * Description: These are very specific errors that require further investigation. Please create a ticket
[ERR] | * Documentation: none
[ERR] |
[ERR] | (!) Please checkout our documentation page to address your issue.

There is currently an issue in Node.js on Windows that can cause this error. If you're interested, you can read more about it here: https://github.com/nodejs/node/pull/61453.

The issue has already been fixed in Node.js v26, and the Node.js team is working on backporting the fix to earlier versions.

For the time being, the recommended workaround is to downgrade to Node.js v24.11.1 or run Athena on a non Windows host (such as Linux), where this issue does not occur.

---

Dashboard Related

My Dashboard Fails To Build During Startup

Dependency Issues

[ERR] | ERROR REPORT
[ERR] | * Error: npm run build exited with code 135
[ERR] | * Type: Javascript
[ERR] | * ID: 15e5sl
[ERR] | * Impact: critical
[ERR] | 
[ERR] | Error Information
[ERR] | * Registered error: ✅
[ERR] | * Description: These are very specific errors that require further investigation. Please create a ticket
[ERR] | * Documentation: none
[ERR] | 
[ERR] | (!) Please checkout our documentation page to address your issue.

This issue can have two different causes:

• Insufficient memory: The bot does not have enough RAM available to build the dashboard.

• Node.js version change: Updating or changing your Node.js version can leave behind incompatible build artifacts.

To resolve the issue, navigate to your /dashboard folder, delete the .next and node_modules directories, and then restart the bot. This will force the dashboard to rebuild using your current Node.js version.