Access over SSH

Clone, pull, and push git repositories over SSH with an Ed25519 or RSA-2048+ key registered on your git.eu account.

Access over SSH

git.eu authenticates the git command-line client over SSH with public-key authentication - no password, no token in the URL. You generate a key pair on your machine once, register the public half in your account settings, and every clone, pull, and push over SSH authenticates automatically from then on.

Key requirements:

Ed25519 (recommended) or RSA with a modulus of at least 2048 bits.
ECDSA, DSA, and weaker RSA keys are rejected.

Every snippet uses two placeholders that resolve automatically when you are signed in on this site:

<INSTANCE> - your instance slug (for example beta2). In call-to-action links it expands

to the full instance URL.

<USERNAME> - your account name on that instance.

Not signed in? The placeholders stay visible as styled literals - swap them for your own values by hand.

Step 1 - Generate a Key Pair

Open a terminal on the machine that will talk to git.eu and generate an Ed25519 key pair:

ssh-keygen -t ed25519

Accept the default location (~/.ssh/id_ed25519) and set a passphrase when prompted. A passphrase-protected key stays safe even on a laptop that gets lost or stolen - the private key alone is not enough to impersonate you.

Prefer RSA? Use a modulus of at least 2048 bits:

ssh-keygen -t rsa -b 4096

ECDSA, DSA, and RSA keys smaller than 2048 bits are rejected when you register them.

Step 2 - Add the Public Key to Your Account

The public half of your key pair - the file ending in .pub (for example ~/.ssh/id_ed25519.pub) - is safe to share. Copy its full contents and register it in your account settings. The private half never leaves your machine and is never sent to git.eu.

Open SSH Keys settings

Give the key a name you will recognize later (for example my-laptop) so you can tell devices apart and revoke a single lost machine without touching the others.

Step 3 - Clone, Pull, and Push

Create the repository on your instance first if it does not exist yet (web UI: New repository). Then clone it over SSH - the SSH URL follows the scp-style form git@<INSTANCE>.git.eu:<USERNAME>/REPO_NAME.git:

git clone git@<INSTANCE>.git.eu:<USERNAME>/REPO_NAME.git
cd REPO_NAME

Already have a working copy over HTTPS? Switch the remote:

git remote set-url origin git@<INSTANCE>.git.eu:<USERNAME>/REPO_NAME.git

Then work as usual - git add, git commit, git pull, git push. Every operation authenticates with the registered key; nothing is typed per call.

Troubleshooting

Permission denied (publickey). The key is not registered on your account, or the ssh client cannot find it. Check that you registered the public key (.pub) in Settings → SSH Keys, that it matches the private key on this machine, and that the ssh agent holds it (ssh-add -l). The fingerprint shown in your settings must match

ssh-keygen -lf
~/.ssh/id_ed25519.pub

on your machine.

Key not accepted when adding it. Only Ed25519 and RSA keys of 2048 bits or more are accepted. Generate a supported key pair (Step 1) and paste the full ssh-ed25519 AAAA... or ssh-rsa AAAA... line from the .pub file. The comment at the end of the line (your name or hostname) is optional.

Cannot access a private repository. A private repository is visible only to the owner and invited collaborators. Ask the owner to add you as a collaborator on the repository settings page, or use your own repository.

Push refused while the repository is busy. A repository accepts one push at a time; when another operation (web UI, HTTPS, or another SSH session) is writing to it, git reports that the repository is busy. Wait a moment and retry - your changes are not lost.

Next Steps

Ready to get started?

Manage your SSH keys