Would these problems have affected a self hosted RU server? I had some problems connecting to hosts the past few days but I think I figured it out that I was inadvertently exceeding the license limit by using my single PRO license on Linux Viewer to connect to my Windows PC which has the same PRO license to then connect to hosts using my self hosted server and shared address book. I just re-read the EUA licensing and realize I was probably not supposed to be doing that, and checking the logs on my server saw talk about licensing error exceeding limits or something like that and after logging out all but one computer from the shared address book that allowed me to connect to hosts again, so long as only one Viewer is in use at a time, although, I did notice by signing out of Linux Viewer I can still control the Windows Viewer PC with a direct LAN connection, so I can still use it the way I like to. My bad! I wasn't trying to break the rules on purpose, I just find the Windows Viewer is much more reliable at maintaining multiple host connections than the Linux Viewer is, and I prefer to use Linux so that's the only reason I was using the program that way.
No, self-hosted server isn't affected in any way because it doesn't require our hosted service to work. It is a completely isolated/autonomous solution.
My bad! I wasn't trying to break the rules on purpose, I just find the Windows Viewer is much more reliable at maintaining multiple host connections than the Linux Viewer is, and I prefer to use Linux so that's the only reason I was using the program that way.
No worries ) You should just apply your RU license key in RU Server as described here. While any paid customer can still use RU Server in the "free mode" , registering it with their RU key will extend their allowed connections via that server (it will bring this number to that allowed by their RU license). So if you have a paid RU license and you use RU Server it's always a good thing to register RU Server as well.