In this article, we will discuss some common problems that our users have when installing a Royal Server and how to troubleshoot them. In many cases, users will get the following error message:

(Error while loading Royal Server Permissions:

The was an error loading the Royal Server Permissions: ReceiveFailure: The underlying connection was closed: An unexpected error occurred on a receive)

This error message suggests either a problem with the self-signed certificates or with the TLS version being used. If you get this message the first thing to check is whether or not you have already created self-signed certificates. If you haven't, this can be done in the Royal Server Configuration Tool under "Royal Server - Service Configuration", by clicking on "Create Self-Signed":

If you have, please remove any existing ones and create new ones. If that also doesn't help, then you may have a problem with the allowed security protocols. Microsoft has changed the way the OS handles cipher protocols (e.g. for SSL connections) over time and disabled insecure ones.

In the installation directory of the Royal Server, you will find RoyalServer.exe.config and RoyalServerConfig.exe.config.
These two XML-configuration files have a key called "SecurityProtocolType" which is set to TLS12. The next step would be to change these settings to "SystemDefault". Please note: the value must be the same in both files!

Additionally, you can check in the registry which protocols are configured by the OS. You can find this information here:

There you can see the protocols and their respective keys that are either "Enabled" or "DisabledByDefault".

Last but not least, it is also possible that the "SchUseStrongCrypto" registry key has been removed or changed. Please check the following registry key and make sure it is set to "1": 

HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node\]Microsoft\.NETFramework\<VERSION>: SchUseStrongCrypto

You can find some more information on this topic here: