XFile Ultra
Log inSign up

xfileultra systemd service

The Node app runs as the xfileultra unit. Use systemctl and journalctl for status, restart, and logs.

xfileultra systemd service

After a normal install, the Node app is managed by systemd as xfileultra. Nginx proxies to that process. If the service is down, the site is down even when Nginx is fine.

buyer-setup.sh creates and starts this unit (see also SYSTEMD.md in the package).

Useful commands

sudo systemctl status xfileultra
sudo systemctl restart xfileultra
sudo journalctl -u xfileultra -n 50 --no-pager

Follow live logs:

sudo journalctl -u xfileultra -f

When to restart

  • Right after the install wizard Done step (required)
  • After you change .env
  • After buyer-update.sh (it usually restarts for you)
  • When status shows failed / inactive or the site returns 502

Common problems

failed / activating forever

Read the last 50–100 journal lines. Typical causes: bad .env, database unreachable, port already in use, or a failed build.

Nginx 502 Bad Gateway

Nginx is up; Node is not. Restart xfileultra and watch the journal.

Edited .env but nothing changed

Restart the service after env file edits. Most admin UI settings apply without a restart; disk/env changes do not.

Related