Connection Procedures
Details and examples of tunnelling specific protocols and applications

http - Web

If you discover a web service on, you would use the following details:
  • IP:
  • remote port: 80
  • local port: 8080
And then use your Web Browser to browse to http://localhost:8080 to connect to the remote web service.


When you use a browser to connect to a device that is on port 443 (https) you must connect using the prefix https, as follows:
Warning: If you connect as http://localhost:2222, without prefixing the URL with https, then the device might return as "Page Not Found".
If this is successful you will then likely be presented with a certificate warning. Click on [Advanced...] and then [Accept] and continue to connect to the device.
Could not load image


To SSH to the remote Ardexa machine, you would use the following details:
  • IP:
  • remote port: 22
  • local port: 2222
Then run SSH on your local machine to connect to the tunnelled port
ssh -p 2222 [email protected]
And you will be logged into the remote machine!

Using a TIA Project

When a Totally Integrated Automation project is being utilised the following procedure should be followed to connect your Ardexa tunnel:
  1. 1.
    Open the TIA Project
  2. 2.
    Open Services and stop the service S7 S7DOS Help Service (this service occupies port 102)
  3. 3.
    In the Ardexa App, configure the TUNNEL to use Local and Remote port 102
  4. 4.
    Start the tunnel with powershell (as Administrator)
  5. 5.
    Restart the S7 S7DOS Help Service
  6. 6.
    In TIA navigate to Online -> Extended online
    • NB. Extended online does not work with HMI panels. This is a limitation of the panel.
  7. 7.
    Choose PN/IE_
  8. 8.
    Double-click in the IP Address field and enter the value:
  9. 9.
    Connect to the SPS
  10. 10.
    (do work)
  11. 11.
    Go Offline must be clicked before closing the TUNNEL
  12. 12.
    Close TIA
  13. 13.
    Close TUNNEL

Running multiple tunnels on the same local port

If you need to use multiple concurrent tunnels and are unable to alter the local port (e.g TIA Portal), you can tell the Ardexa Tunnel client to bind to a specific IP address. For example:
ardexa-tunnel $workgroupId $deviceId 102 102 -b
ardexa-tunnel $workgroupId $deviceId 102 102 -b
By binding each tunnel to a specific loopback address, you can connect as many tunnels as you need.
Last modified 2yr ago