@simonp said:
@acebmxer Hi,
Thanks to your help we were able to identify an issue with Redis that we think is the source of the v6 dashboard loading issue.
Could you try and checkout the fix_redis_encryption_issue branch, rebuild xo and restart ?
This should solve the 401 issues.
Switched back to Master branch and made some changes to my install script.
add diagnostics for missing XO 6 web UI build artifacts
Plain bash [[ -f ]] fails silently on unreadable paths owned by
SERVICE_USER, causing false-positive missing-artifact warnings. Switch
all file/dir tests and grep calls to use sudo.
SUCCESS] Xen Orchestra built successfully
[INFO] Build verification passed: dist — all JS chunks present.
[INFO] Build verification passed: dist — all JS chunks present.
[INFO] Creating systemd service...
[SUCCESS] Systemd service created and enabled
[INFO] Configuring sudo for xo-service (mount/umount/findmnt)...
[SUCCESS] Sudo configured for xo-service (mount, umount, findmnt)
[INFO] Applying security hardening...
[INFO] Starting xo-server service...
[INFO] Waiting for Xen Orchestra to become ready (up to 60s)...
[INFO] Not ready yet (attempt 1/10), retrying in 6s...
[SUCCESS] Xen Orchestra is ready (HTTPS on port 443)
[SUCCESS] Update completed successfully!
[INFO] New commit: 0f29421627c7
v6 Dashboard still loading correctly. Thank you for the fix.