Error Message Decoder

Connection refused. The target server is not running or not accepting connections on that port.

Fix: Check if the server is running. Verify the port number. Check firewall rules.

DNS lookup failed. The hostname could not be resolved.

Fix: Check the URL/hostname for typos. Verify DNS settings. Check internet connection.

Connection timed out. The server didn't respond within the time limit.

Fix: The server may be overloaded. Check network connectivity. Increase timeout settings.

Port is already in use by another process.

Fix: Kill the process using the port: `lsof -i :PORT` then `kill PID`. Or use a different port.

Cross-Origin Resource Sharing blocked. Browser security prevents requests to a different domain.

Fix: Add CORS headers on the server. Use a proxy in development. Check Access-Control-Allow-Origin header.

Cannot find the module/package you're trying to import.

Fix: Run `npm install`. Check import path for typos. Verify package exists in node_modules.

Out of memory. The process exceeded available RAM.

Fix: Increase Node.js memory: `--max-old-space-size=4096`. Check for memory leaks. Add swap space.

Permission denied. The operation requires elevated privileges.

Fix: Run with sudo/admin. Check file permissions with `ls -la`. Change ownership with `chown`.

No such file or directory. The path doesn't exist.

Fix: Check the file path for typos. Ensure the file exists. Check relative vs absolute paths.

Process was forcefully terminated (OOM killer or manual kill).

Fix: Check system memory. The process may have been killed by the OS OOM killer.

Process received a termination signal (graceful shutdown).

Fix: This is usually intentional. Handle SIGTERM in your code for cleanup.

Connection was reset by the remote server.

Fix: Server may have crashed. Check server logs. Could be a firewall or proxy issue.

Payload Too Large. The request body exceeds the server's size limit.

Fix: Reduce payload size. Increase server's body-parser limit. Use chunked uploads.

Too Many Requests. You've been rate-limited.

Fix: Implement exponential backoff. Reduce request frequency. Check API rate limit headers.

Bad Gateway. The reverse proxy received an invalid response from the backend.

Fix: Check if the backend service is running. Check proxy configuration (nginx/apache).

Service Unavailable. The server is overloaded or under maintenance.

Fix: Wait and retry. Scale the service. Check server health and logs.

Self-signed certificate not trusted.

Fix: In dev: set `NODE_TLS_REJECT_UNAUTHORIZED=0`. In prod: use a valid certificate (Let's Encrypt).

The SSL certificate has expired.

Fix: Renew the certificate. Check auto-renewal setup (certbot). Restart the web server.