Unable to Copy Workflow Nodes – “Copied to clipboard successfully” but nothing is copied (Self-Hosted v2.7.4)

Questions
1

Hello,

I am currently using self-hosted n8n version 2.7.4 on my VPS (installed via Docker). I am facing an issue while trying to copy workflow nodes.

Whenever I select one or multiple nodes and try to copy them using any of the following methods:

  • Right click → Copy

  • Ctrl + C

  • Ctrl + Shift + C

I receive the message “Copied to clipboard successfully”, but the nodes are not actually copied. When I try to paste, nothing happens.

Because of this, it is becoming very difficult to:

  • Duplicate nodes

  • Move nodes between workflows

  • Export partial workflow sections

So currently the copy functionality is not usable.

Details:

  • n8n Version: 2.7.4

  • Deployment: Self-hosted via Docker

  • Browser: Google Chrome

  • OS: Windows

Has anyone else faced this issue or knows how to resolve it?
Is this a known bug in this version?

Any help would be greatly appreciated.

Thank you.

1 Like
2

Hi @pankaj_ikraft

this is most likely because you’re accessing n8n over HTTP, the browser’s Clipboard API requires HTTPS to work. If that’s true, try to set up SSL on the instance and tell me if this works ! :crossed_fingers:

1 Like
3

Yeah this is the HTTP vs HTTPS thing, Chrome’s clipboard API just doesnt work over plain HTTP. Quickest fix without setting up SSL is go to chrome://flags/#unsafely-treat-insecure-origin-as-secure, add your n8n URL there and relaunch Chrome. Or just use Firefox which doesnt have this restriction.

1 Like
4

Hi @pankaj_ikraft, this does not usually occur but you can always switch to incognito mode to make sure that the JSON you are tryna copy gets copied as it is, also if this problem persists i would recommend adding a small proxy between you and your instance so that you are always a new client for it with clean cache memory. (this will increase some overheads)

5

Perfect, thank you! The Chrome flags trick worked — added the n8n URL and relaunched, clipboard API is working fine now. Appreciate the quick fix!

1 Like
6

Hey @houda_ben, yes that was exactly the issue — accessing n8n over HTTP. I’ve set up SSL and it’s working now, thanks for pointing me in the right direction!

7

@pankaj_ikraft glad it helped ^^

please close the answer as the solution !

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.