Pauline's community posts

Hello Cody,

Could you please clarify if you mean what ports are needed to be opened in case if you want to use IPv6 protocol? Please note, that for the RU Server, you can use any port of your choice that is bound to an IPv6 address. In this case, please make sure to specify the same port value in the Internet-ID settings in the Host Settings and in the Connection Properties.

In addition, please note that you can check if your server is visible from the outside and the selected port is opened by opening canyouseeme.org on the Server machine. In case if you receive a Success as the check result in this form when checking the port, then it means that everything is configured correctly.

Hope that helps.

Hello Vasilis,

Thank you for your message.

Unfortunately, my reply was meant for user ML as he reported an issue with specific keys like Ctrl, Shift and etc. so this is why I asked them to update their Host to the latest Beta version - there was a similar issue in the earlier versions.

As for the updates on the issue with Greek accents - I'll check with our developers if there are any updates on this. However, please note, that reproducing this issue and implementing a fix for it might take some time. We hope that the fix will be available in the next update of the Beta version of Viewer for Mac/Linux, but unfortunately, we cannot provide any ETA on when this update is going to be released yet. Sorry for the inconvenience.

I'll get back to you if there are any updates on the issue.

Hello,

Thank you for your message.

Unfortunately, we couldn't reproduce the issue. Could you please clarify what version of Linux do you use?

In addition, please let us know what version of Host is used? If it's version 6.10.10.0 or an earlier version - please try updating your Host to the latest 6.12.2.0 (Beta 2) version as it contains a fix for a similar issue that was occurring in the 6.10.10.0 version when some keys (Enter, Ctrl, Shift, etc.) were sometimes not working on a remote machine, so this might help to resolve the issue. A full list of Release Notes is available here.
Version 6.12.2.0 (Beta 2) is available for the download on this page.

Please let us know if the issue persists.

Hello Cody,

Thank you for the provided screenshots.

To begin with, please make sure that your RU Server is directly accessible for your Hosts and Viewers from the outside. Here's our step-by-step guide on making the Server accessible.

Then you need to configure your Hosts and Viewers, so they would use your custom self-hosted server as a relay server instead of our public server. This tutorial describes how to configure Host and Viewer for using a self-hosted relay server. Please note that in order to use IPv6, you simply need to enable the Use IPv6 checkbox when specifying the Server's address and enter the IPv6 address of your server:

Here you can also specify a custom port number for Hosts and Viewers, in case if your Server uses another port as its communication port. For more information on Ports used by RU Server please see this page.

Please note that the only IP address you should be using in this case - is your Server's IPv6 address - it should be specified in the Host and Viewer's settings as described above. However, when it comes to connecting to the remote Hosts - when using self-hosted RU Server as a relay server, you should be adding the Hosts to the address books via their Internet-ID codes (i.e. using the Internet-ID connection).

In addition, please note that in case if the Use IPv6 checkbox is enabled, then for the remote Host machines that do not support IPv6 protocol, the connection will simply fall back to using IPv4, as this checkbox means use IPv6 whenever available, otherwise use IPv4, i.e. these are just additional options, they are not exclusive.

Hope that helps.

Hello Cody,

Thank you for your message.

Yes, IPv6 is supported for the RU Server. You can specify the server's address and then enable the Use IPv6 feature in the Host Settings -> Internet-ID settings and in the Connection Properties window -> General tab the Viewer's side.

However, please note that we highly recommend that you use a DNS name as the server address instead of using an IP address so that you can easily migrate your Server to a new computer or hosting location without updating settings on all your Viewers and Hosts - in this case, you'll only have to update your DNS record and point it at the new IP address of the server. For more information please see this page.

Hope that helps.

Hello John,

Thank you for your message.

Yes, of course! We already have a few video-tutorials published on our website (like the program registration tutorial here, for example) and we definitely plan to publish a series of videos that explain how to set up different program features, including the tutorials on setting up the RU Server. Unfortunately, we cannot provide any specific ETA on the videos yet, but we will try to make them available as soon as possible.

Please let us know if you have other questions.

Hello Iris,

Thank you for your message.

We've updated the current Beta version of Viewer for Mac/Linux and extended the free license period until December 31, 2020. Please re-download the updated Beta version with an extended license period from this page. Sorry for the inconvenience.

Please let us know if you have more questions.

Hello Michal,

Thank you for your message.

We've updated the Beta version of Viewer for Mac/Linux and extended the free license period until December 31, 2020. Sorry for the inconvenience.

In order to continue using Viewer for Mac, please re-download the updated Beta version with an extended license period from this page.

Please let us know if you have more questions.

Hello Trent and Brandon,

I just got an update from our development department - we will additionally test this on a newer version of the mobile Viewer to see if the issue persists there and if yes, will try to implement a fix for this. This might take some time, but we'll try to fix the issue as soon as possible.

I'll keep you updated on the issue and let you know once there are any updates on this.

Hello Brandon,

Thank you for reporting on this.

I've forwarded the information on the issue to our development department and asked them to look further into the issue. I'll get back to you soon with their reply.

Sorry for the inconvenience.