🛰️ XO 6: dedicated thread for all your feedback!
-
The odd part is that I'm happy with XO Lite, so not sure why 6 is causing me problems other than needing g to jump back to 5. I only have one XO new enough to be updated, I guess I need to update my lab since I'm in it a lot lately and come up with more productive comments for the team. The switch just immediately shocked me in a way that it shouldn't have done being that I've been using Lite to try and get ready.
-
That's also because XO Lite is replacing basically "nothing before", while XO 5 is 10y full of features that we can't all re-implement at once in XO 6
-
Tasks still show completed actions, a month ago events.
No way to install updates. New ui less informative than the old one - no packages changelog.
It also take a time to get into new navigation. Instead of static categories at sidebar, now i can't open Backup while inside pool settings. Need to do extra clicks.
-
See https://feedback.vates.tech/?tags=xo-6 (updates are planned already)
For the rest, if it's a feedback that's not there and not a bug, feel free to add it
-
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.
-
@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.
-
@Mathieu I do use NGINX Proxy Manager and i have no issues accessing XO-CE via the new v6 default or the old v5 with working links.
As @probain has stated there have been quite a few updates pushed to fix most issues. My issues were related to the script i used to install XO-CE. The script creator had to update the script to the recent changes made.
Make sure you are on the latest commit and/or update your script and try again.
-
@acebmxer
I found the culprit:HTTP/2 support needs to be enabled on the SSL tab of npm for v6 to work fine behind the reverse proxy.
It's now working fine.
-
@Mathieu ok. Yeah I already had that enabled. Glad you got it working.
-
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 VMsWindows 11 has GPU passthrough & bios
Windows Server 2025 - no GPU passthrough , uses uefi
