I agree, for those little guy and those of us testing the product, this is a real put off. Smaller, less intrusive and moveable would be acceptable, just. You have to understand as was mentioned earlier, many of us do maintenance work in the off hours so as not to intrude on our client time and we have to be able to do our job!
Yes I have, the hosts are visible to the RU Server so it has to be correct. The viewers see the server, the hosts see the server, I can connect to some of the hosts so that connection is working.
I should note, I am self hosted.
Version mismatch is 188.8.131.52 vs 184.108.40.206 and I have connected to other hosts with 220.127.116.11 Hosts are running, the server see them Server can see host with Inernet ID Firewall is fine, I can connect to some hosts No blocking on outbound ports Using Avast, inbound working because I can access some hosts Avast shouldn't be blocking outbound traffic, using free version No proxy required Cannot login never mind connect Hosts are shown online, at least some of the time Self hosted Can see everything No Pin Code
Edited:John Gatschuff - Jan 17, 2022 5:50:36 pm EST
This problem has been getting progressively worse. RU Server admin console show 9 hosts as idle, stop a host and the number of idle hosts is reduced. OK that seems to be working. Open Viewer connect to server address book shows all hosts, at any given time any number of those host show as offline. Some hosts, which show online and you attempt to connect, the host suddenly goes offline and cannot connect. I am currently using Viewer and Host 18.104.22.168 and Server 22.214.171.124. This problem has occurred over at least the last 5 versions. It has occurred on more than one viewer. I love the product and would consider expanding, but not until this problem is corrected.