🛰️ XO 6: dedicated thread for all your feedback!

[acebmxer]

@coolsport00

Same here on XO from sources - commit f93bb

[coolsport00]

@acebmxer Thank you for confirming as well "Ace". And, I am also running XO from Sources, same build (4 commits behind is all)

[john.c]

@coolsport00 said:

@julienxovates - playing around some more in XO6. I have quite a list I want to submit for feature enhancements (needs, really). One you all already have is being able to open a VM Console in another Tab. I attempted to but it keeps spinning & Console never displays:

I'm using Brave browser. Sometimes this particular browser can cause issues loading pages because of its security. But, I also tried Chrome and same behavior. Thoughts?

@acebmxer @coolsport00 Just like Microsoft Edge, Brave and Google Chrome both share the same upstream Chromium codebase. If there is an underlying bug in Chromium itself, it can potentially affect both browsers simultaneously.

However, because this involves the XO6 VM Console spinning indefinitely, it is usually caused by environment configurations or active development bugs. Here are the best steps to troubleshoot:

• Update XO From Sources: If you are running XO from sources, try updating by building from the head of the master branch. XO6 is moving fast, and this console bug may already have a fix waiting for you in the latest commit.

• Self-Signed Certificates: Open a new tab and navigate directly to your XO instance's IP/domain to explicitly "Accept the risk and continue". Chromium browsers often silently block background Console WebSocket connections if the root SSL certificate isn't trusted.

• WebSockets & Proxies: Ensure your reverse proxy, firewall, or ad-blocker isn't dropping or blocking wss:// (Secure WebSocket) connections, which the console relies on to stream the visual data.

[acebmxer]

@john.c

Updated to latest commit did not help as expected... Also tried firefox an with out reverse proxy...