same result - still spins - but appears to stop quicker (though have now just disabled that other VS and was just about to re-enable it (cannot leave it disabled too long or someone will get upset)
it didn’t fix that other problem anyway - still defaults to wrong VS
@Stegan Do you always use the same browser? I’ve had some obnoxious behavior disappear with a different browser. I forget exactly what it was but there was a button on some page that basically did the same thing. I tried another browser and it worked. But, it was 100% in Opera. 0% in Chrome. Both are the same base too. Both are pretty much ‘as is’. No extensions or any security lock downs in either. I keep those two that way to use when I have access problems in my other browsers.
Chrome most of the time, but both Mozilla quite a bit and have tested this on both. I tend to avoid IE and others - my PC just doesn’t have much space to waste (thanks to Microsoft + Windows bloat)
Oh and @Ilia, I did not answer the question regarding “rogue browser extensions”
Only “Bitwarden Password Manager”, “DuckDuckGo Privacy Essentials” and “Ghostery Tracker & Ad Blocker - Privacy AdBlock” but I turned them off when you prompted (but it didn’t change anything) been using them for years without a problem.
It is important to note this is only happening on 1 VM sadly a machine that is quite a lot of developer activity ATM
today (I’m too remote and off-line very soon, but can PM a team access pass tomorrow about this time - thanks - don’t waste too much of your valuable time though)
Can you PM me at least the domain name of the system, without login credentials? Perhaps I can identify something even without logging in. Also, do you have the same issue if you connect to the system using the IP address, i.e., 1.2.3.4:10000?
@Stegan thanks! I logged in and checked the File Manager tree—there were no “spinning dooms” that I could find—the file tree opened as expected!?
@Jamie, however, I did discover something that could technically be classified as a bug. If the stats.pl server is started by one sudo-capable user, another sudo-capable user won’t be able to connect to the socket to collect real-time stats. Stats will still be collected in the background and displayed, but only after a page reload.
For the user who initially started the stats.pl server, the socket connection works fine.
I have not applied this (should I? and how?) or is this not directly connected to the original issue as the problem has bounced up again today! - I was logged in as “Server Owner”