Remote access troubleshooting

Configuration issues

To isolate a configuration problem, you may want to temporarily test connecting to the Web Server from a browser on the computer where AVEVA Real-Time System (RTS) is running instead of a remote computer. Use the same URL that you use to access RTS Console remotely. If you can locally access the same URL on the computer that is running the RTS web service, the configuration problem is likely related to Firewall issues.

Certificate issues

If you are not sure if an issue is related to HTTPS certificates, you may want to temporarily configure RTS for remote access through port 80 (regular HTTP) to isolate certificate related issues.

If you have a .cer, .crt, or .der file, you can obtain the thumbprint by entering the following commands in a Command Prompt window with administrator privileges:

$cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 'certificate.cer'

$thumbprint = $cert.Thumbprint

If you have a .pem file, you can obtain the thumbprint by entering the following command instead:

certutil -dump .\certificate.pem

Once you have the thumbprint, you can check for the value of the Cert Hash(sha1) field.

In general, you can view imported certificates by using the following commands in Windows PowerShell:

dir Cert:\LocalMachine\My

dir Cert:\LocalMachine\Root

Depending on your system configuration, such as on Windows Server operating systems, you may need to reserve the URL by entering the following commands in a Command Prompt window with administrator privileges:

netsh http delete urlacl url=https://<ip-address>:443/

netsh http add urlacl url=https://<ip-address>:443/ user=Everyone