Copy and paste into the console, and why your keyboard types the wrong characters

You copy a long command on your own machine, click into the guest's console, press paste, and nothing happens. Or worse, something happens and it is not what you copied.

Two different things are going on here, and they get confused with each other constantly. One is about the clipboard. The other is about the keyboard, and it is the one that wastes whole afternoons.

Why the clipboard does not simply cross

The graphical console is a picture of a screen. What travels from you to the guest is not text, it is key events: you pressed this key, then that one. The guest has no idea a clipboard exists on your side.

Your browser also refuses to let a web page read your clipboard whenever it likes, which is a good rule that exists for obvious reasons and is not going to be relaxed for convenience.

So the console gives you an explicit way across: a clipboard panel. You paste your text into that box, which sets the remote clipboard, and then you paste normally inside the guest. It is one extra step and it is the whole mechanism.

The direction back out works the same way in reverse: copy inside the guest, then read it from the panel.

The setting that mistypes everything

Here is the one that looks like a broken paste and is not.

The graphical console has a keyboard layout, and it is set at the datacenter level, not per user and not by your browser. It controls how key events are interpreted for the virtual machine's virtual keyboard.

If that layout does not match the one you are physically typing on, letters come through fine and everything else does not. Symbols land in the wrong place, and the characters that suffer worst are exactly the ones in passwords and configuration files.

On the host used to check this, the layout was set to a non-English one, which is correct for that machine and wrong for anyone typing on a different physical keyboard against it.

The symptom is very specific and worth memorising: letters and digits are fine, punctuation is wrong. That is a layout mismatch, not a paste failure and not a broken console.

Why long pastes still go wrong

Even with the clipboard panel working and the layout correct, very long text pasted into a graphical console is fragile. Every character is a synthetic key event, and a guest under load can drop some. You will not get an error; you get a command with three characters missing somewhere in the middle.

If what you are pasting matters, do not paste it as keystrokes at all.

What to do instead when it matters

A key, a password, a certificate, a long configuration block. Do not type it through a screen at all. Write it as a file: the guest agent can put a small file into a running guest without any network, which is exactly what that channel is for. Anything past about 60 KB needs the network instead.

A shell command you will run again. Put it in a file and run the file. This survives a dropped keystroke and you get to keep it.

A whole working session. Use the text console if the guest has one, or SSH if the network is up. Both are text, so your terminal's own copy and paste behaves normally and no layout translation happens.

SPICE, briefly

SPICE does support real clipboard sharing between your machine and the guest, with an agent installed inside the guest. If you spend serious time in a graphical desktop guest, that is the reason to set it up.

For a server you visit twice a month, it is more setup than the problem deserves.

What Atlas does

Atlas opens Proxmox VE's own console, so the clipboard behaviour you get is Proxmox's, unchanged. There is no separate Atlas clipboard to learn and no second implementation to trust.

What Atlas changes is the frequency of the problem. Most pasting into a console is not debugging; it is a command someone found because the task had no screen. Storage operations, network changes, updates, user and permission work: those have screens, so the clipboard never enters into it.

The console remains for the cases that genuinely need one, and for those, the advice above is the same advice everyone gives, because it is the mechanism and not a preference.