Hello @Anouar_Hichri,
This issue has been discussed recently, and it appears to be a known problem with n8n installed via npm on Windows 11,
You can find more details here:
For now, the safest approach is to install and run n8n using Docker.
Hello @Anouar_Hichri,
This issue has been discussed recently, and it appears to be a known problem with n8n installed via npm on Windows 11,
You can find more details here:
For now, the safest approach is to install and run n8n using Docker.