Troubleshooting

Device doesn’t connect to the portal

If your device doesn’t connect to the portal, please check if the TCP port is not blocked do terminate which port you’re using to connect open .zip config file and open client.conf file there should be a row saying remote X.server99.myscada.cloud 80 (or whatever port you’re using)

Open PowerShell and use this command

 Test-NetConnection X.server99.myscada.cloud -Port YOUR PORT

And it should return TcpTestSucceeded : True

If it doesn’t return true, check your firewall rules and allow the outgoing port

Make sure you try as well to disable the firewall.

If myACCESS doesn’t connect and you’re using more network cards, make sure that you set up the metric correctly – make the network card that is being used for the internet connection to be preferred one

Set-NetIPInterface -InterfaceAlias "Ethernet" -InterfaceMetric 10

Set-NetIPInterface -InterfaceAlias "Wi-Fi" -InterfaceMetric 50

The lower the metric number the more preferred the interface will be

This has to be done due to WSL binding with the preferred interface if it’s binded with an interface that has no DNS or no internet connection, it can’t connect/resolve DNS, which are required to connect with myACCESS server

After this step is finished restart whole computer


Updated on February 26, 2026