> For the complete documentation index, see [llms.txt](https://docs.iynxdev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iynxdev.com/getting-started/common-issues.md).

# Common Issues

{% hint style="info" %}
**Problem not solved after checking here? Let us know in** [**our Support Server**](https://discord.iynxdev.com/)**!**
{% endhint %}

## <mark style="color:blue;">Bot Related</mark>

### <mark style="color:yellow;">My Bot Crashes Immediately</mark>

#### <mark style="color:orange;">Your Configuration is not complete</mark>

You may have forgotten to fill some information in the `common.json` file. <mark style="color:red;">**It's mandatory to fill in every space in that file!**</mark>

#### <mark style="color:orange;">Guild Not Whitelisted</mark>

You may have forgotten to <mark style="color:purple;">add your Guild to the whitelist</mark> required with your license!

Make sure to run <mark style="color:green;">**`/guild whitelist`**</mark> in [our Support Server!](https://discord.iynxdev.com/)

#### <mark style="color:orange;">IP Not Whitelisted</mark>

You may have forgotten to <mark style="color:purple;">add your IP to the whitelist</mark> required with your license!

Make sure to run <mark style="color:green;">**`/ip whitelist`**</mark> in [our Support Server!](https://discord.iynxdev.com/)

***

## <mark style="color:blue;">Antivirus Related</mark>

### <mark style="color:yellow;">My Antivirus Quarantined Files</mark>

*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!

***

## <mark style="color:blue;">Command Related</mark>

### <mark style="color:yellow;">My Commands aren't working</mark>

#### <mark style="color:orange;">Forgot to configure Permissions</mark>

You need to <mark style="color:purple;">make sure all permissions are assigned</mark> in the <mark style="color:green;">**`permissions.json`**</mark> file, *both* the roles and IDs, as *well* as the permission levels each of them get!

#### <mark style="color:orange;">Developer Mode is Enabled</mark>

This can cause commands to not show up! Make sure that <mark style="color:green;">**`developer-mode`**</mark> is <mark style="color:purple;">disabled</mark> in the <mark style="color:green;">**`common.json`**</mark> file.

#### <mark style="color:orange;">A Plugin might have crashed</mark>

<mark style="color:purple;">Check to see if you don't have errors coming up in your console for plugins</mark>! If plugins disable, they'll disable any associated commands too.

#### <mark style="color:orange;">Server or Bot ID may be incorrect</mark>

<mark style="color:purple;">Check to see if your Server/Bot ID are wrong</mark> 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.

***

## <mark style="color:blue;">MongoDB Related</mark>

### <mark style="color:yellow;">My Bot Crashes During Startup</mark>

#### <mark style="color:orange;">MongoDB Firewall</mark>&#x20;

```javascript
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 <mark style="color:purple;">add</mark> your host's IP address to your database's IP allowlist (whitelist). Alternatively, you can allow <mark style="color:purple;">connections from any IP</mark> by adding <mark style="color:green;">**`0.0.0.0/0`**</mark> to the allowlist. [A guide to that is here](https://studio3t.com/knowledge-base/articles/mongodb-atlas-login-ip-whitelisting/)!

#### <mark style="color:orange;">MongoDB Connection</mark>&#x20;

<pre class="language-javascript"><code class="lang-javascript"><strong>[ERR] | ERROR REPORT
</strong>[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.
</code></pre>

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>.&#x20;

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.

***

## <mark style="color:blue;">Dashboard Related</mark>

### <mark style="color:yellow;">My Dashboard Fails To Build During Startup</mark>

#### <mark style="color:orange;">Dependency Issues</mark>

```javascript
[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.