Workflow Issue SSH Ubuntu to Windows Server worng Systanx or worng Path

Questions
1

Describe the problem/error/question

Hello Guys, maybe you can help me out here.
Execute a command
SSH connection successful
This command must create a Folder on a share drive on MS Windows Server.
But whit click on execute, i get an error Message "Syntax Filename or Foldername or DriveLetter is Wrong.
Test from Ubuntu Server to MS Windows are establish.

N8NError
N8NError1485×635 53.1 KB

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
1 Like
3

@rudolph welcome

from your screenshot, i think the ssh connection itself is fine and the problem is now the windows command syntax. I’d try writing to the target file with the full Windows path in quotes, and I’d also test the exact same command manually on the Windows server with the same SSH user. At this point, this looks more like Windows path parsing or permissions on D:\N8N\test.txt than an n8n issue.

2 Likes
4

Hi Tamy,

thank you very much. The Folder is complet open and the User has full access to this machine. So Can you tell me, what is the right command for exsampel: cmd. exe / “echo ..

Thanks

5

Try this command on Windows: If it still doesn’t work, test the same command directly on the server with the same SSH user. That should show whether it’s a Windows command syntax or file permission issue, because it doesn’t look like an n8n problem anymore.

6

The issue is the Command has > inside the quotes

7

The site is returning a 403 error

8

Same. Have been trying to post my answer to this for nearly half an hour, but i keep getting 403s

10

just remove the quotes from the command and you should be good

11

Hi Guys thank you very much , still the same error. On MS PS this Command working. ON N8N not.

N8NError1
N8NError1634×600 25.2 KB

12

I think this might be a known issue with n8n in docker. Have a look here: SSH node fails to execute commands on Windows 11 OpenSSH server when n8n runs in Docker (path/shell handling issue) · Issue #23299 · n8n-io/n8n · GitHub

13

some users have reported this workaround works.

Leave the working directory field empty and instead include it with the command itself.

14

What worked for me here was calling PowerShell explicitly. Even though the connection is fine, the SSH session on Windows doesn’t always interpret paths like the same way PowerShell does;
I also made sure not to use / as the working directory, since that’s a Linux path and doesn’t make sense on Windows.