In the next version (RV20), which be released in a few weeks, by default LongRange will only accept trusted certificates.
This means self-signed certificate will no longer be accepted by default.
To get LongRange to accept your self-signed certificate, you have 2 options:
- Install the CA certificate on your device (best practice)
- Change a setting in your server profile to allow the use of any (non-trusted) SSL certificate (not recommended as this is susceptible to man-in-the-middle attack).
Note that existing Server Profiles created prior to RV20 will still by default accept any (including self-signed) certificates. However new Server Profiles created using RV20 will NO longer accept self-signed certificate unless you change the setting to allow it.
There is also a new parameter to control this setting when configuring server profiles using longrange:// URL. The parameter is called anysslcert.
If you are currently using self-signed certificate, and you don't have the CA installed on every device, it is recommended that you add that parameter to your profile configuration URL to make sure that newly created profiles in RV20 are behaving in the same way as in RV19:
longrange://updateprofiles/?prf,1.anysslcert=Y&...