Conrad Sallian's community posts

Thank you for the report. Currently checking one of our servers that could have the said issue. Sorry for the inconvenience.

Hi Mihhail ,

Feel free to try again now.

Thanks.

Hi Mihhail,

Thanks for letting us know. We'll check out the script and see what might be wrong with it.

Hi Nijel ,

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.

Hope that helps.

Hello Myavin,

Thank you for your message.

Yes, they may send various verification methods including the one you mentioned (they may also give you a call to verify the order). You shouldn't be worrying.

You can also call them directly (i.e. initiate a call from your side) and ask about that message to be 100% sure that it's from them. Here is their contact information - the phone numbers are down below on the page:

https://payproglobal.com/contact/

Hope that helps.

Currently fixing the server issues. Please, let us know if/when the connections are restored.

Manuel Lopez wrote:

Here is my viewer log (I replaced the pc name with PCX and my IP with x.x.x.x):

31-01-2023__15:28:43__774 Connection #455877. Connection to "PCX". Mode: <Authorization>. Connecting...
31-01-2023__15:28:43__775 InetConnection #455877. Internet connection to PCX (x.x.x.x:5655).
31-01-2023__15:28:43__795 InetConnection #455877. Method "Connect" - OK. PCX connected to ID server: x.x.x.x.
31-01-2023__15:28:44__769 InetConnection #455877 - PCX need. Server version: 0
31-01-2023__15:28:59__783 InetConnection #455877. Socket error. Name: "PCX", host: "x.x.x.x:5655". Exception class: "EIdReadTimeout". Message: "Read timed out.".
31-01-2023__15:28:59__784 Connection #455877. Connection to "PCX" failed. Mode: <Authorization>.
31-01-2023__15:28:59__785 Context #455877 removed. Mode: <Authorization>.

Hi Manuel,

What's the server IP address in "PCX connected to ID server: x.x.x.x." ? This will help us pinpoint the issue.

Thanks.

Hello ,

Thank you for the reports. Currently checking the issue.

Hello Alan,

Sorry that it took the Mac/Linux host longer than it expected. We will do our best to release the first public beta as soon as possible.  

Thank you.

Hello Ales,

Thank you for your message.

Unfortunately, no. This notification is not supposed to be customizable. This is a warning message that tells the user that their computer might be accessed by someone not being authorized to.

The fact that this message only shows for the free license means that it was the free license/version that was often abused in the past. We had to implement this message to restrict the ability to use the free license for malicious purposes out-of-the-box.