Node is running on this host

If you can read this page, the server executed JavaScript to build it.

Reload this page a few times. If Requests served climbs and Process started stays the same, the application persists between requests, which is what the portal needs. If both reset each time, it is being started per request and cannot hold state.
RuntimeNode v22.18.0 on linux/x64
Process Started2026-09-24T19:19:36.221Z
Uptime28h 11m
Requests Served584
Pid1772261
Longest Gap Between Requests2h 17m
Memory Used By This App67.4 MB
Machine Memory250.9 GB total, 142.1 GB free
Cpus48
Working Directory/home/u180344934/domains/staging.webtreeit.co.uk/hbuilds/versions/01a0bf41-3516-72fb-9c2c-0ede1ab28fe5/nodejs
Port From Environmentnot set (defaulted to 3000)
Server TimeFri Sep 25 2026 23:30:38 GMT+0000 (Coordinated Universal Time)
Diskok: true
where: /tmp/wit-node-probe.txt
note: wrote and read back: written at 2026-09-25T23:30:38.163Z
Outbound Httpsstate: reached example.com
status: 200
ms: 23
Test outbound HTTPS →   Raw JSON →