@florent said in Snapshots are no longer being pruned? Commit 58f02:

@probain thanks for signaling this, we just merged a fix, that fix it on our labs
can you test it on your side ?
https://github.com/vatesfr/xen-orchestra/pull/9202

I can confirm that it solves the issue in my primary lab. Tomorrow I will be able to re-validate at my second lab as well.
Thank you for such a quick fix!

I've mentioned it on the forums once or twice. And after @wezke explicitly asked for it. I decided to take the time to finally go ahead and publish an Ansible-role for installing XO from source.

Benefits from using any of the many installation-scripts:

Scripts are often quite big. Making them hard to validate and scrutinize for security reasons.

Ansible (imho) is easier to read and see what it does.

If you are orchestrating your environment through Ansible already, this should drop in semi-nicely

This follows the official steps from the Xen-Orchestra docs, except for ONE main thing. This does not run the xo-server as root. In the hopes that it should raise security just a tiny bit more.

Note and Disclaimer!
Do your own validation of the source. Do NOT take my word for how this works. And use it at your own risk.
Now, with all disclaimers out of the way. Feel free to use as you'd like. I hope the community takes kindly to this.

https://github.com/cloudrootab/ansible_role_xoce

PS: This is ported from my private role. But should work. See the disclaimer above!
PPS: This is a re-post from a now deleted forum-post, where I mistakenly placed the topic in XCP-NG/Installation.

@olivierlambert said in ️ XO 6: dedicated thread for all your feedback!:

So I quickly experimented different "identities"/themes.

Here is "Nord" in dark mode:

Please add this. This was gorgeous!

@florent said in Backblaze as Remote error Unsupported header 'x-amz-checksum-mode' received for this API call.:

,
requestChecksumCalculation: "WHEN_REQUIRED",
responseChecksumValidation: "WHEN_REQUIRED"

I (previously as @jr-m4) just tried the patch you suggested. And I can confirm that this does indeed make the backup complete successfully!
Great work finding a solution that quicklly!

@JamfoFL

@Danp responded to similar/same issue here:
https://xcp-ng.org/forum/post/89858

@R2rho
Faulty gear always sucks. But who would've guessed that two separate systems would produce the same problems. That is highly unlikely, but never impossible.

Good luck with the RMA

For completeness sake. Confirming that the fix also works in my second lab as well.

I can now reliably recreate the behavior between the commits mentioned above.
As I expected, the problems with finding a "known good" was due to user error

@AlexD2006

Thanks for your input.

So I believe I've managed to find which commit breaks my snapshot-pruning.

If I use the commit: 8a390057b648205b7ae2c6ccc2a0bc78dc624e08 - Then the pruning works.

However, if I go to the next one: 05c6f87a1212e81c51e63f6a585b9e97a3c1bfb2- Pruning breaks and snapshots are no longer being deleted as retention says they should.

I can consistently and reliably re-create the different scenarios in my first lab. This doesn't explain why I'm seing inconsistent results in my other lab. But that might be user error, that I have to double check tomorrow!

Perhaps you could try to see if you see the same behaviour between the commits?

It might be that my known good, isn't that good at all.

I can replicate the problem in my second lab as well. But it is being affected even with commits older than a101e.
I'm still trying to find and provide better/useful information.

Windows guests Console - Reloads every 5-10s.

When trying to use the console for both my Windows 11 and Server 2025. The console reloads every 5-10s. This makes it borderline unusable. Since it resets the viewport/window scroll placement as well. Also the console seems to loose focus when this happens as well. Leading to have to click the console-section to get it in focus, to receive I am not seeing this behaviour in XO5 at all.

I do not see the same behaviour on Linux (Ubuntu 24.04) guests. But they are cli-only. No X/Wayland

Commit: b89c26459cfd301bb92adf0a98a0b2dbab57e487
node: 24.12.0
Management agent 9.1.100-59 on both VMs

Windows 11 has GPU passthrough & bios
Windows Server 2025 - no GPU passthrough , uses uefi

@Mathieu said in ️ XO 6: dedicated thread for all your feedback!:

Has anyone tried to access XO 6 via a reverse proxy?
I'm using nginx proxy manager in a docker container to access my XO instance.
Everything is working fine with XO5 (both XOCE and XOA).
But when trying to access XO6 through the reverse proxy, it shows only a few info, with a circle loading on the top and nothing on the left bar:

If I access XOCE and XOA v6 by their IP address, it's working as expected.

Websocket support and cache is activated on the reverse proxy, nothing else fancy on that side.

Thanks.

I haven't tried ngnix. But I access my though haproxy:443 - > xo:8443. And that works just fine. But there needed to be a couple of fixes upstream in master to iron out the quirks with non-443 ports and such.

Replying back, that with commit 5fcb6db32e884e7d7d4cc2bb7430532201a45699 the graphics for 2FA look as they should

@olivierlambert said in 2FA doesn't load graphics properly after XO6 went default (XO from source):

Does it work OK without the proxy?

Testing on my secondary lab, and the results are the same. Secondary lab runs privileged service, 443 without proxy.

Since XO6 went default. The 2FA has been a bit wonky. See screenshot from chrome console.

Logins work as they should though. So there is no problem there.

My setup runs on port 8443, behind a haproxy.

@MajorP93

Thanks for your feedback. I'll look into it over the christmas hollidays

@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):

@probain branch mra-fix-secure-port

Success!! Amazing. Thank you so much

@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):

@probain I will prepare a branch for a potential fix, so you can still use the 8443 port

Absolutely fantastic. I will test it as soon as possible to help out however I can.

Cheers!

@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):

@probain If you can, it will help a lot. Thanks

I remember why I chose to use 8443. It is because the xo-user running the service isn't running with root privileges. So doing it with an ordinary user was way more difficult to setup than just use 8443.

But...
Switching over so that service-user runs as root. 443 becomes possible. And things work again as expected. However, I really did like not running xo-server as root.

@MathieuRA said in XO5 breaks after defaulting to XO6 (from source):

@probain

Web server listening on https://[::]:8443

Well, I may have an idea about your issue.
The code is looking for the port 443 to know if he should use secure protocol ('wss:' / 'https:')
Is your second lab also in https on the 8443 port?

Hmm, no the second lab is more "standard" and uses 443.
I can try and set 443 on the primary lab as well to test.