Skip to main content

Troubleshooting Common Panel & Server Errors

1. EADDRINUSE: address already in use​

  • Cause: Your application or bot is trying to bind to a network port that is already in use by another process.
  • Solution:
  1. Check your assigned network port in the Network tab.
  2. Update your configuration or .env file to match your primary assigned port.

2. Server Marked as Offline or Crash Loop​

  • Cause: Insufficient RAM allocated to the container or syntax error in your application entry file.
  • Solution: Check the Console logs immediately after starting. If Node.js throws a SyntaxError, fix the file in File Manager.