Fathom Scraper health
Back to desk

Is Node actually running?

A 503 means Passenger never got a live process. This page first hits /api/ping (instant). If ping works, the 503 is gone — any remaining problem is outbound HTTPS, not the web server.

Checking /api/ping…

Shop probes

Waiting for ping before probing shops.

Feed HTTP ms bytes parsed hint
Waiting for /api/health

If ping fails

  1. Setup Node.js App → the app must be Started.
  2. Startup file must be app.js in the application root, next to public/ and data/.
  3. Do not upload the Grok / GROK1.2 project. Only this pack.
  4. Read data/boot.log in File Manager.

If ping is OK but every shop is FAIL

The account cannot open outbound HTTPS. Ticket the host: “Please allow outbound TCP 443 and DNS from this cPanel account for a Node.js app.” Historic marks still print on the desk.

Cron

cd /home/USER/fathom && /home/USER/nodevenv/fathom/20/bin/node cron.js