A 503 from your hosting panel means its proxy can't reach Webfaze: the app either stopped, or it's listening somewhere the proxy isn't looking.

Step 1: read the log. It's the only place the real reason appears.

  • Hostinger: hPanel → your Node.js app → Logs.
  • cPanel: the log file shown in Setup Node.js App.

A healthy start ends with Webfaze 1.0.0.3 listening on http://0.0.0.0:….

Step 2: match the cause

  • listening on http://127.0.0.1:… You set WEBFAZE_HOST. Delete it and restart.
  • You set PORT. The panel assigns the port; delete PORT and restart.
  • Admin password must be at least 12 characters. Lengthen WEBFAZE_ADMIN_PASSWORD.
  • Wrong database username or password or Access denied. See "I get an Access denied database error".
  • Database "x" does not exist. DB_NAME must match your panel exactly, prefix included.
  • Cannot find module 'node:sqlite'. Node.js is too old for SQLite. Raise it to 22.15 or newer, or set the DB_* settings.
  • The log is completely empty. The startup file is wrong. It must be app.js.

Step 3: if the log doesn't say enough, run the doctor. Change the startup file to doctor.js, restart, read the log, fix anything marked with a cross, then set the startup file back to app.js and restart.

Two other pages that look similar

  • "Webfaze could not start" with a list of checks: Webfaze is showing you the problem itself. Fix the item marked with a cross and restart.
  • "Your site is temporarily unavailable. Please check back soon." That's the licence page, not a deploy problem. See "My site is locked because the licence ended".