Skip to content

Frameworks

Errors from the framework your site or backend is built with. 9 answers.

Next.js error Find where it happens: at build time (read the build log), on the server (your host's function logs), or in the browser (the console). Each has its own fix. Node crash By default, an uncaught exception makes Node.js print the stack trace and exit. Read that trace, fix the error, and run Node under a process manager. Express error Express handles errors through middleware with four arguments (err, req, res, next). Make sure async errors reach it, and log the error before responding. Laravel error Read storage/logs/laravel.log for the full error. Keep APP_DEBUG false in production. Common causes: .env settings, cache, permissions, or a missed migration. Django error Keep DEBUG off in production and read your server logs for the traceback. A 400 Bad Request on every page usually means ALLOWED_HOSTS is missing your domain. Rails error Read the production log in your app's log folder for the exception. Common causes: pending migrations, missing credentials or environment variables, assets. Nuxt error Nuxt errors come from several places: Vue rendering, server and client startup, and the Nitro server. Find which one from the error page and logs. Remix error In Remix, a route's ErrorBoundary shows when its component, loader or action throws. Read the server log for loader and action errors. Gatsby build failed Read the first error in the build output; it names the file and step. Usual causes: data sourcing, gatsby-node.js code, a plugin, or the Node version.

Not sure what's wrong with yours?

One click checks your site, and your Cloudflare if you connect it, and gives you a report of what's wrong and what to do. Your first report is free.

Run your free report