This article relates to the now deprecated Time Tagger Web Application. Please consider using Time Tagger Lab (GUI) for local control of the Time Tagger hardware or Time Tagger Network for remote time tag streaming.
For security reasons, the Time Tagger Web Application server does not allow connections from the network computers; only localhost connections are allowed. The Time Tagger Web Application neither manages access rights nor encrypts the communication. Nevertheless, networking tools like SSH can provide secure access to a remote Time Tagger Web Application server. This requires an SSH server to be set up and run on the machine where you run your Web Application server. The remote clients then establish an SSH tunnel from their PC to the Time Tagger server (listening on the “localhost” of the server PC) and use the Web Application the same way as locally connected.
You can find here more information about port forwarding.
The SSH client establishes a connection with the server and binds the local port on your client computer with the port on the server computer corresponding to the Web Application “localhost:50120”. This way, you connect to the “localhost:port” on your computer, and SSH will forward that connection to the remote computer.
Example:
ssh -L 12345:localhost:50120 username@server
Here:
The server computer where Time Tagger is connected must have an SSH server installed and be accessible from the client.
Client must have an SSH client installed and be able to connect to the SSH server.
Please consult your network administrator if you need assistance setting up an SSH connection and port forwarding. For more information, please have a look at the Time Tagger Network functionality that allows you to send the time tag stream to a remote computer and process it there.