Yes, it would be interesting to know which browser was originally problematic?
Because in addition to the issue with ad blockers, described here, as a Binder power user I’ve occasionally (extremely rare) had a build started via Chrome mess up in a such way that although you try to start a new launch process (or reload), you cannot connect to what should otherwise be a successful session launch in Chrome for hours. However, going to another browser it will launch a session on the same computer during those hours. Eventually like a day or so later it will again launch the sessions successfully in Chrome on that computer. This is very rare so no one has been able really track it down. (Or really confirm it even happens.)
1 Like