Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. N8N
  3. How can FFmpeg work with N8N?

How can FFmpeg work with N8N?

Scheduled Pinned Locked Moved Solved N8N
6 Posts 2 Posters 51 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    creative567145
    wrote last edited by
    #1

    Hi

    According to this Forum post/comment:
    https://forum.cloudron.io/post/17531

    FFmpeg is installed on Ubuntu 24.04 LTS OS

    ...
    We researched and in order to make it work with N8N, some additional changes are required.

    It would be very helpful if anybody can share that info 🙂

    1 Reply Last reply
    0
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by james
      #4

      Hello @creative567145

      You have been misguided by this video.

      1. ExecuteCommand and LocalFileTrigger have been disabled by default for N8N 2.0 and above, documented here: https://docs.n8n.io/2-0-breaking-changes/#disable-executecommand-and-localfiletrigger-nodes-by-default
        You can edit your /app/data/env.sh file and add export NODES_EXCLUDE="[]" save the file and restart your N8N app, to re-enable all disabled nodes.
        But be advised, ExecuteCommand and LocalFileTrigger nodes have been disabled by default because they pose security risks
      2. since N8N on Cloudron is running inside docker and not on the system itself you will not find ffmpeg on the system but inside the docker container of N8N.

      After you have followed step 1. above, following up referring to the video, you can skip to the last part and test it with ExecuteCommand and ffmpeg -version since ffpmeg is installed in docker.

      I have confirmed this is working with the Cloudron N8N package version 4.1.1 (screenshot below number (1)) packaging N8N version 2.1.4 (screenshot below number (2)).

      86fc2996-59e6-47d1-9039-3ae78fceef49-image.png

      Running ffpemg -version in the Cloudron app after adding export NODES_EXCLUDE="[]" to /app/data/env.sh and restarting the app.

      4f871639-81ff-492f-9d35-1cccbc260e78-image.png

      1 Reply Last reply
      3
      • jamesJ Offline
        jamesJ Offline
        james
        Staff
        wrote last edited by
        #2

        Hello @creative567145

        Could you please go into a little more details what you are trying to do?
        A step-by-step process on what you are trying to do and where it fails would be a great help to reproduce the issue and give you a solid answer.

        1 Reply Last reply
        1
        • C Offline
          C Offline
          creative567145
          wrote last edited by
          #3

          Thank you @james for the fast response.

          1. For starters, we checked if FFmpeg is installed on the OS and we get the result that it isn't.
            Screenshot attached

          2. Then, according to this:


            We should perform modifications to the docker compose file of N8N,
            but since we are doing that with env.sh (export put in front), we don't know what to add there.

          That is why we asked if somebody has already done this successfully so that he can send the summarized steps, if possible

          Screenshot from 2026-01-01 15-56-40.png

          1 Reply Last reply
          0
          • jamesJ Offline
            jamesJ Offline
            james
            Staff
            wrote last edited by james
            #4

            Hello @creative567145

            You have been misguided by this video.

            1. ExecuteCommand and LocalFileTrigger have been disabled by default for N8N 2.0 and above, documented here: https://docs.n8n.io/2-0-breaking-changes/#disable-executecommand-and-localfiletrigger-nodes-by-default
              You can edit your /app/data/env.sh file and add export NODES_EXCLUDE="[]" save the file and restart your N8N app, to re-enable all disabled nodes.
              But be advised, ExecuteCommand and LocalFileTrigger nodes have been disabled by default because they pose security risks
            2. since N8N on Cloudron is running inside docker and not on the system itself you will not find ffmpeg on the system but inside the docker container of N8N.

            After you have followed step 1. above, following up referring to the video, you can skip to the last part and test it with ExecuteCommand and ffmpeg -version since ffpmeg is installed in docker.

            I have confirmed this is working with the Cloudron N8N package version 4.1.1 (screenshot below number (1)) packaging N8N version 2.1.4 (screenshot below number (2)).

            86fc2996-59e6-47d1-9039-3ae78fceef49-image.png

            Running ffpemg -version in the Cloudron app after adding export NODES_EXCLUDE="[]" to /app/data/env.sh and restarting the app.

            4f871639-81ff-492f-9d35-1cccbc260e78-image.png

            1 Reply Last reply
            3
            • jamesJ Offline
              jamesJ Offline
              james
              Staff
              wrote last edited by
              #5

              Hello @creative567145
              Did this resolve your question?

              1 Reply Last reply
              1
              • C Offline
                C Offline
                creative567145
                wrote last edited by creative567145
                #6

                Thank you @james

                We performed these steps and it was successful:

                1. Add these lines in env.sh
                  export NODES_EXCLUDE="["ExecuteCommand", "LocalFileTrigger"]"

                2. Restarted N8N

                3. Performed the test using these steps:

                • (+) - Execute command
                • Execute Once: ON
                • Command: ffmpeg -version
                • Test step
                • Check the OUTPUT - ok (screenshot attached)

                Screenshot from 2026-01-02 13-03-11.png

                1 Reply Last reply
                1
                • jamesJ james has marked this topic as solved
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search