Understand the error. Find the fix.
Troubleshoot common bot and hosting problems with practical explanations. Search by error code, message or technology to find the steps that matter.
Discord
Common Discord API and bot connection failures.
4014 Privileged Intents Not Enabled The bot requests gateway intents that have not been approved or enabled.
Why it happens
Discord closes the gateway connection when your bot requests privileged intents that are unavailable to the application.
How to fix it
- Open the Discord Developer Portal and select your application.
- Under Bot, enable only the privileged intents your project actually needs.
- Make sure the intents configured in your bot's code match the enabled settings.
- If your verified bot needs approval for an intent, follow Discord's approval process.
50013 Missing Permissions Discord rejected an operation because the bot lacks sufficient privileges.
Why it happens
The bot may be missing the required permission, or its highest role may be below the target role or member.
How to fix it
- Identify the action that failed and review its required permission.
- Check channel-specific permission overwrites.
- Review the bot's role position when managing roles or members.
- Grant only the necessary permissions and retry the action.
50001 Missing Access The bot cannot access the requested guild, channel or resource.
Why it happens
The resource may be inaccessible, removed, or outside the guilds and channels available to the bot.
How to fix it
- Confirm that the bot has joined the correct Discord server.
- Verify the channel or resource ID used by the command.
- Check View Channel permissions and relevant channel overrides.
- Handle deleted or unavailable resources gracefully.
Invalid Token Bot Authentication Failed Your bot cannot authenticate using the token supplied in its configuration.
Why it happens
The token may be missing, revoked, pasted incorrectly or loaded from the wrong environment variable.
How to fix it
- Check the environment variable name and confirm it is being loaded.
- Verify that the token belongs to the correct Discord application.
- Rotate the token through the Developer Portal if it may have been exposed.
- Update the secret in Volyx and restart your server.
- Never paste a token into public logs or support screenshots.
429 Rate Limit Reached Too many API requests were sent within Discord's permitted interval.
Why it happens
Discord applies rate limits to prevent excessive API activity; repeated or parallel requests can reach those thresholds.
How to fix it
- Respect Retry-After or the rate-limit information returned by Discord.
- Use a queue instead of sending large batches simultaneously.
- Avoid tight loops that repeat failed API calls.
- Use a maintained Discord library that handles rate limits appropriately.
10062 Interaction Expired Discord no longer recognizes the interaction your command is answering.
Why it happens
An interaction may have expired before its initial response, or the application may be referencing an invalid interaction.
How to fix it
- Acknowledge interactions promptly, within Discord's response deadline.
- Defer the reply if processing requires more time.
- Use editReply or followUp as appropriate after deferring.
- Check that duplicate bot processes are not mishandling the same event.
50035 Invalid Request Data Discord rejected fields or values included in an API request.
Why it happens
The request body may contain an unsupported value, an invalid field type or content exceeding API limits.
How to fix it
- Read the specific field path reported by Discord.
- Validate message, embed and component lengths.
- Confirm that IDs, arrays and required properties use the expected types.
- Log a sanitized request structure to locate malformed data.
Telegram
Bot API responses related to delivery, access and duplicate sessions.
409 Conflicting Bot Sessions Multiple consumers are attempting incompatible update retrieval methods.
Why it happens
Two processes may be polling updates with the same token, or webhook and polling settings may conflict.
How to fix it
- Ensure that only one intended polling process is active.
- Check whether a webhook is already configured.
- Choose webhook delivery or polling according to your application design.
- Stop abandoned bot instances before restarting the intended instance.
403 Bot Access Denied Telegram does not permit the bot to deliver the requested message.
Why it happens
A recipient may have blocked the bot, or the bot may no longer have access to the destination.
How to fix it
- Handle the error without repeatedly retrying the same destination.
- Check whether the bot is still permitted in the target chat.
- Allow users to re-enable the bot voluntarily.
- Remove inaccessible destinations from automated notifications where appropriate.
429 Telegram Request Limit The bot is sending requests more quickly than Telegram currently permits.
Why it happens
High-frequency messages or bursts of API traffic may trigger request throttling.
How to fix it
- Follow the retry_after value when Telegram supplies one.
- Queue notifications and spread out large broadcasts.
- Avoid immediately retrying failed requests in an infinite loop.
- Monitor the sending rate when running scheduled announcements.
Node.js
Runtime, dependency and JavaScript module issues.
Heap out of memory JavaScript Memory Exhausted The Node.js process used more heap memory than its configured limit.
Why it happens
Large datasets, unbounded caches, memory leaks or excessive allocations can exhaust the JavaScript heap.
How to fix it
- Inspect server memory metrics and recent log output.
- Limit in-memory caches, arrays and queued work.
- Investigate listeners and objects that remain referenced indefinitely.
- Adjust memory allocation only when sufficient hosting resources are available.
Cannot find module Dependency or File Not Found Node.js could not resolve an imported package or local module.
Why it happens
A dependency may be missing, the import path may be incorrect, or the server filesystem may differ from your development machine.
How to fix it
- Check the module name shown in the error.
- Install the required dependency using your package manager.
- Verify relative import paths, extensions and filename capitalization.
- Confirm that deployment includes required files and dependencies.
ERR_REQUIRE_ESM Module Format Mismatch CommonJS code attempted to load an ES module using an incompatible require call.
Why it happens
Some packages support ESM imports rather than CommonJS require.
How to fix it
- Check the package documentation for its supported module format.
- Use import syntax or dynamic import where appropriate.
- Review package.json module settings and file extensions.
- Use a compatible package version only when that fits your project.
Python
Python package resolution and process termination problems.
Exit code 137 Process Terminated The application received a forced termination and could not shut down normally.
Why it happens
Exit status 137 often indicates SIGKILL. Resource exhaustion is a common cause, but other external termination is possible.
How to fix it
- Review memory consumption in your Volyx server metrics.
- Check whether the host or container recorded an out-of-memory event.
- Reduce unnecessary memory usage and expensive concurrent tasks.
- Check for administrative or automated process termination if memory is normal.
ModuleNotFoundError Python Package Missing The Python interpreter cannot import a requested module.
Why it happens
The package might not be installed in the active environment, or the import path may not match the installed package.
How to fix it
- Find the missing module name in the traceback.
- Install its package into the Python environment used by the server.
- Check requirements.txt and your deployment setup.
- Confirm the active Python version and virtual environment match your installation.
How to read server errors
Start with the exact error code or exception name. For Discord, codes such as 50013 identify API failures, while gateway close codes such as 4014 describe connection-level issues. Telegram may return HTTP status codes together with additional response details.
For Node.js and Python, examine the exception message and traceback. Check the earliest meaningful failure and the file or line it points to. Look at the Volyx Console logs, environment configuration and resource metrics before restarting the server repeatedly.
When requesting support, include the relevant error message, runtime, steps to reproduce the problem and sanitized logs. Never share API keys, bot tokens, passwords or other secrets.