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
  • 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. Cannot set environment variables

Cannot set environment variables

Scheduled Pinned Locked Moved Solved N8N
7 Posts 2 Posters 1.7k Views 3 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.
  • G Offline
    G Offline
    garza
    wrote on last edited by
    #1

    Hello everyone,
    I'd like to know what is the way to set custom env variables in this app.
    I tried setting them in the /app/data/env and restarting the app, but that didn't seem to work. Specifically, I exported N8N_BLOCK_ENV_ACCESS_IN_NODE as false (that should be the default), but still no luck.
    How could this be achieved?

    girishG 1 Reply Last reply
    0
    • G garza

      Hello everyone,
      I'd like to know what is the way to set custom env variables in this app.
      I tried setting them in the /app/data/env and restarting the app, but that didn't seem to work. Specifically, I exported N8N_BLOCK_ENV_ACCESS_IN_NODE as false (that should be the default), but still no luck.
      How could this be achieved?

      girishG Do not disturb
      girishG Do not disturb
      girish
      Staff
      wrote on last edited by
      #2

      @garza Did you put the export in the front? Like this:

      export N8N_BLOCK_ENV_ACCESS_IN_NODE=false
      
      G 1 Reply Last reply
      0
      • girishG girish

        @garza Did you put the export in the front? Like this:

        export N8N_BLOCK_ENV_ACCESS_IN_NODE=false
        
        G Offline
        G Offline
        garza
        wrote on last edited by
        #3

        @girish Yes, I put it that way, but that doesn't seem to work.

        girishG 1 Reply Last reply
        0
        • G garza

          @girish Yes, I put it that way, but that doesn't seem to work.

          girishG Do not disturb
          girishG Do not disturb
          girish
          Staff
          wrote on last edited by
          #4

          @garza Do other variables work ? Maybe try to change something which is easy to check and check if that works. How are you reproducing the issue ? I can check in a test installation and we can see if it's a package issue or upstream bug.

          G 1 Reply Last reply
          0
          • girishG girish

            @garza Do other variables work ? Maybe try to change something which is easy to check and check if that works. How are you reproducing the issue ? I can check in a test installation and we can see if it's a package issue or upstream bug.

            G Offline
            G Offline
            garza
            wrote on last edited by
            #5

            @girish Yes, at least I tried with N8N_LOG_LEVEL to change it to the debug level and that worked without any problem.

            I'm testing the env updates the regular way, changing the /app/data/env (now /app/data/env.sh in today's app update) and restarting the app. Then, specifically for the N8N_BLOCK_ENV_ACCESS_IN_NODE flag, I'm testing in node fields that accept an expression, but still without access (please refer to the screenshot attached).

            9c76f151-b1f1-4c42-9406-ad92f86611fd-image.png

            girishG 1 Reply Last reply
            0
            • G garza

              @girish Yes, at least I tried with N8N_LOG_LEVEL to change it to the debug level and that worked without any problem.

              I'm testing the env updates the regular way, changing the /app/data/env (now /app/data/env.sh in today's app update) and restarting the app. Then, specifically for the N8N_BLOCK_ENV_ACCESS_IN_NODE flag, I'm testing in node fields that accept an expression, but still without access (please refer to the screenshot attached).

              9c76f151-b1f1-4c42-9406-ad92f86611fd-image.png

              girishG Do not disturb
              girishG Do not disturb
              girish
              Staff
              wrote on last edited by
              #6

              @garza Looks like this is a known issue. See https://community.n8n.io/t/no-access-to-env/20665/ . Using the environment variable will work it seems, just the preview in the UI does not work.

              G 1 Reply Last reply
              0
              • girishG girish has marked this topic as solved on
              • girishG girish

                @garza Looks like this is a known issue. See https://community.n8n.io/t/no-access-to-env/20665/ . Using the environment variable will work it seems, just the preview in the UI does not work.

                G Offline
                G Offline
                garza
                wrote on last edited by
                #7

                @girish Thank you, I can corroborate it works even if it's showing an error in the node field.

                1 Reply Last reply
                0
                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