VPN and SSH access

Connecting to Mjolnir takes two steps: connect to the UCPH VPN, then SSH to the cluster entrance.

Step 1 — Connect to the UCPH VPN#

Connect to the UCPH VPN before connecting to Mjolnir. Current guidance is to use the Cisco AnyConnect client obtained from UCPH:

Note Use the client obtained from UCPH. A version downloaded elsewhere, or carried over from another institution, may not be configured for UCPH remote access.

VPN and remote-access problems are handled by UCPH IT rather than by Mjolnir support — see KU-IT contact details. If the VPN itself will not connect, that is the right place to start.

Step 2 — Log in over SSH#

Once the VPN is connected, open a terminal and run:

bash
ssh <KU-ID>@mjolnirgate.unicph.domain

Replace <KU-ID> with your own KU user ID. Your password is the password associated with your KU-ID — there is no separate Mjolnir password.

The first time you connect, your SSH client will ask you to accept the server's host key. This is normal on a first connection.

Where you land#

mjolnirgate is the entrance to Mjolnir. It is a DNS name covering the login node and several standby servers, so the machine you land on may vary between sessions.

Important The login node is not for computation. It is for logging in, managing files, preparing work, and submitting and monitoring jobs. Analyses belong in Slurm jobs — see Login nodes vs compute nodes.

If login fails#

SymptomWhat it usually means
SSH hangs or times outThe VPN is not connected, or not connected with Cisco AnyConnect
VPN itself will not connectA KU-IT issue — use the KU links above, not Mjolnir support
VPN works but SSH is refused or rejects your passwordAsk Mjolnir support — see Getting help

If the VPN connects successfully and you still cannot log in, that is a Mjolnir issue and worth raising. Include the exact command you ran and the error text.

Next steps#