Running Pluto on Login Node

First, make sure that you have set up your ssh-config such that you can ssh onto a specific node of Nocuta 2 (or Noctua 1) directly, i.e. for example via ssh n2login1 (see Access for Applications like Visual Studio Code for help) and connect to the chosen login node.

...

After this, you should be able to use the link given by Pluto above in your local browser (if you’ve changed <local port> you need to change the port in the link as well) and should see the Pluto starting webpage.

Running Pluto on Compute Node

In principle, you can do the same as under “Running Pluto on Login Node” above but using, say, n2cn0164 n2cn0216, instead of n2login. However, since you won’t always get the same compute node when requesting resources via Slurm this approach is tedious because you need to set up direct ssh access to the given compute node (n2cn0164 n2cn0216 in this example) each time.

...

ssh -L 1234:127.0.0.1:1234 noctua2 ssh -L 1234:127.0.0.1:1234 -N n2cn0164n2cn0216

Here, noctua2 is the Noctua 2 jump host (see as specified in Access with SSH for ssh configuration) and n2cn0164 n2cn0216 is the given compute node. Hence, for different Slurm jobs, you only need to change the name of the compute node at the very end of this command (instead of modifying your ssh config).