Install XO from sources.

[lem2405]

@acebmxer Even with the credentials present in the configuration file, the process still prompts for sudo permissions, which will not be visible or actionable when running as a cron job.

[acebmxer]

@lem2405

Sorry for any confusion. Hope this clears it up.

The credentials in xo-config.cfg are only for logging into Xen Orchestra (the pre-update task check and VM snapshot). There is no setting for a sudo password, and the script won't run as root, so sudo will still ask.

To run it from cron, the account running the script needs passwordless sudo. Run this as that user:

echo "$USER ALL=(ALL) NOPASSWD:ALL" | sudo tee /etc/sudoers.d/xo-cron
sudo chmod 440 /etc/sudoers.d/xo-cron
sudo visudo -c

Then add --non-interactive so it doesn't stop to ask anything:

0 3 * * * cd /path/to/install_xen_orchestra && ./install-xen-orchestra.sh --update --non-interactive

Keep in mind this gives that account full sudo with no password. Use at your own risk.

I've pushed this to the dev branch, including a new Scheduled Updates (cron) section in the README. To try it before it reaches main, switch your copy to dev:

cd /path/to/install_xen_orchestra
git fetch origin
git checkout dev

To go back later, run git checkout main.

Scheduled Updates (cron)

--update can run unattended from cron. Two things are needed:

1. Passwordless sudo for the account that runs the script. The script
   refuses to run as root and calls sudo throughout, and there is no config
   setting for a sudo password. Run this as that account:

   echo "$USER ALL=(ALL) NOPASSWD:ALL" | sudo tee /etc/sudoers.d/xo-cron
   sudo chmod 440 /etc/sudoers.d/xo-cron
   sudo visudo -c
   

   This gives the account full sudo with no password.

2. --non-interactive, so the update never stops to ask anything:

   0 3 * * * cd /path/to/install_xen_orchestra && ./install-xen-orchestra.sh --update --non-interactive >> "$HOME/xo-update.log" 2>&1
   

Set XO_API_TOKEN (or the user/password pair) in xo-config.cfg.
Without it, a non-interactive run skips the
running task check instead of
prompting for credentials.

[lem2405]

@acebmxer Thank you for your help and prompt response. I truly appreciate it!

[acebmxer]

@lem2405

No problem. Let me know if you still encounter any issues.

[acebmxer]

Update - changes are live in the dev branch now.

So figured out the update / switching branches for the proxy by connecting the proxy to my xoa free account. That triggered the available update to next version. From there I found the command that needs to be ran on the proxy to switch back and forth...

Latest branch

stable branch

Backup job ran sucessful.

2026-10-09T17_48_25.447Z - backup NG.txt

After the proxy has been deployed...

The proxy has been registered with your Xen Orchestra instance.
You can manage it from the Xen Orchestra web interface.

Next: register the proxy's updater and move it to the 'latest' channel.

1. On the pool master (IP), set a password for the proxy's 'xoa' user
   (choose your own) and reboot the proxy VM:
   xe vm-param-set uuid=UUID xenstore-data:vm-data/system-account-xoa-password='<your password>'
xe vm-reboot uuid=UUID
2. SSH to the proxy as 'xoa' (IP) and run:
   sudo xoa-updater register - This registers it with your vates account.
   sudo xoa-updater configure-channel xo-proxy-appliance-latest - set to latest or stable
sudo xoa-updater upgrade - This can be ran via the UI or this command. Both need to be done twice to do the upgrade and/or downgrade.
   register needs a free xen-orchestra.com account; see the README.

And host connected via proxy.