Hi Daniel,

Try adding the same options (chiefly the "-A naiss2025-22-549" option) to the "in-line" options of your HPC configuration Slurm profile. In general, I would debug this by first making sure that the HPC functionality works without a problem before testing the remote connection functionality. To do this, simply connect to your institution using ThinLinc, open CONN there, go to "HPC configuration" and test your Slurm profile using the "test profile" button (and checking the logs and debugging if necessary) until that works fine. Once that test works correctly, the conn remotely functionality to connect to the server will have one less potential problem to run into (and I think it should work fine without any additional issues)

Hope this helps

Alfonso

Originally posted by Daniel Simon:

Hi Alfonso!

I've got the system running fine over ThinLinc with a remote desktop on the server. The in-line "ml add PDC; ml matlab/r2024b" helped a lot there! Thanks!

But I still can't get "conn remotely" to work. I tried adding the in-line command to my local AND remote HPC "Slurm computer cluster" settings. But I'm still stuck at this line:

Requesting a new Matlab session in rasimon@dardel.pdc.kth.se. This may take a few minutes, please be patient as your job currently sits in a queue. CONN will resume automatically when the new Matlab session becomes available

Do you have any suggestions on how to debug at this point? When I run the Matlab GUI on the HPC (e.g., through ThinLinc), I need to run (something like) this command first:

salloc --ntasks=2 -t 1:00:00 -A naiss2025-22-549 -p shared --qos=normal

...where -A naiss2025-22-549 is required for my account, and then SSH -X into the node where I have allocated space to run Matlab.