Troubleshooting
Fixes for myACCESS connectivity issues — blocked TCP ports, firewall rules, and network interface metric configuration on Windows.
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. To determine which port you’re using to connect, open the .zip config file and open client.conf — 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_PORTIt should return TcpTestSucceeded : True.
If it doesn’t return true, check your firewall rules and allow the outgoing port. Make sure you also try disabling 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 the preferred one:
Set-NetIPInterface -InterfaceAlias "Ethernet" -InterfaceMetric 10
Set-NetIPInterface -InterfaceAlias "Wi-Fi" -InterfaceMetric 50The lower the metric number, the more preferred the interface will be. This is required because WSL binds to the preferred interface — if that interface has no DNS or internet connection, myACCESS cannot connect or resolve DNS.
After this step is finished, restart the computer.