Troubleshooting

Fix the errors everyone hits: crashes, missing modules, port problems, memory limits and failed installs.

When your server won't start

How to read the console from the first error down, tell an install failure from a code error, and fix the handful of problems that stop most app servers.

I can't reach my app

A step-by-step checklist for a website or API that won't load — the SERVER_PORT and 0.0.0.0 rules, the right address to visit, and how to tell if your app is even listening.

My bot shows offline in Discord

The five reasons a hosted bot sits grey in Discord — a bad token, missing privileged intents, a crash after login, an expired free timer, or a server that never started — and how to fix each.

How to recognize an out-of-memory kill (exit code 137, "Killed"), why heavy apps hit the free 2.5 GB limit, and practical ways to use less memory in each runtime.

When dependencies won't install

Read the three install failures you'll actually hit — two from npm, one from pip — spot the package that broke, and fix it at the source.

When a Git deploy fails

Read the deployment log first, then fix the handful of usual causes — wrong branch, revoked access, a private repo linked by URL, or a "successful" deploy that changed nothing.

EADDRINUSE — the port is already in use

Decode the "address already in use" crash — Node's EADDRINUSE and Python's OSError errno 98 — understand why it happens when you get one public port, and bind it exactly once.

EACCES and ENOENT — permission and missing-file errors

Decode the two file errors every runtime throws — ENOENT (no such file) and EACCES (permission denied) — by reading the exact path in the message, then fix it in the File Manager.

Node version errors — unsupported syntax and engine mismatches

Tell the two apart — a hard SyntaxError when your code is newer than the running Node, and the softer EBADENGINE warning — then set the right version in Settings.

Python version errors — SyntaxError from version gaps

When "invalid syntax" really means "this feature is from a newer Python" — spot the version-gap crash from match/case and friends, then set the right Python in Settings.

Config file errors — reading JSON and YAML position pointers

When your app crashes parsing its own config or data file, the error tells you exactly where — learn to read the line/column pointer, and fix the handful of JSON and YAML mistakes that cause it.

Discord rate limits — 429s and how bots should behave

What a 429 and retry_after mean, why discord.js and discord.py already handle them for you, the loops that get you in trouble, and the invalid-request limit that can temporarily ban your bot's connection.

Git conflicts and stale files

Two different "Git" headaches — deploy-time stale files and overwrites on Falix (copy, never delete), and the merge conflicts you resolve locally before you push — untangled and fixed.

Why is my website slow?

"Slow" is three different problems wearing one coat — your app, the proxy, or the network. Measure the split with one curl command from another machine, then fix the part that's actually slow.

Reading a Minecraft crash report

A crash report looks like a wall of Java, but it's organized. Read four things top-to-bottom — the description, the stack, the "Caused by", and the mod/plugin fingerprints — and the culprit names itself.

Players can't join my Minecraft server

When someone can't get in, the client usually says why in one short line. Decode the whitelist, version-mismatch, server-full, wrong-address, and online-mode messages — and match each to the exact fix.

Database connection errors, decoded

A database that won't connect throws one of a handful of errors, and each names its own cause. Here's the whole zoo across mysql2, pg, MongoDB, and redis — the exact codes, what they mean, and the fix.

When a one-click template won't deploy

Deploying a starter template runs a short pipeline on your server. It can be turned away at the door, or finish partway with warnings — this decodes both, so you know exactly what happened and what to do.

Backup and restore problems

Backups are simple until one won't create, won't delete, or restores the wrong thing. Here's each snag — the cooldown, locks, the free-plan Google Drive step, and the one restore toggle everyone gets wrong.

When (and how) to contact support

Support helps fast when you hand over the right three things — shared logs, your server ID, and what you already tried. Here's how to gather them, and an honest picture of what support can and can't do.