As with most Linux systems you can securely access to the jPC form another device using Secure Shell (SSH).

The SSH daemon (i.e. server) is masked by default. To enable it run the following commands:

sudo systemctl unmask ssh.socket ssh.service
sudo systemctl enable ssh.socket ssh.service
sudo systemctl start ssh.socket ssh.service

Setup passwordless SSH login to avoid having to type in a password every time you open an SSH session. This is also typically required for remote deployment and debugging from a development PC.

1. On your remote device, generate a key pair

   ssh-keygen -t rsa

   The key pair will likely be stored in your user profile's home directory (i.e. $HOME/.ssh or on Windows C:\Users\{Username}\.ssh).

2. Copy the public key to the jPC panel PC. Don't miss the trailing colon.

   scp $HOME/.ssh/id_rsa.pub admin@{jpc_ip_address}:

3. Register the public key as an authorized key on the jPC. On the jPC, run

   mkdir .ssh && cat id_rsa.pub >> .ssh/authorized_keys

4. The next time you start an SSH session from your remote device, you should not be asked to authenticate with a password.

Files can be transferred to and from the jPC using any device with the scp (i.e. Secure Copy) command installed. It should be in stalled by default on most Windows 10 and Windows 11 PCs.

To transfer a file from your remote device to the jPC, run

scp {path_to_source_on_remote_device} admin@{jpc_ip_address}:{path_to_destination_on_jPC}

To transfer a file from the jPC to your remote device, run

scp admin@{jpc_ip_address}:{path_to_source_on_jPC} {path_to_destination_on_remote_device}

Use the -r switch for recursive copies. scp also supports wildcards (.e.g. *.xml) for selecting files matching a pattern.

If you prefer to use a GUI, consider using the FileZilla client.