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. n8n cors

n8n cors

Scheduled Pinned Locked Moved N8N
4 Posts 3 Posters 116 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic was forked from Capability to tweak CORS config of an app joseph
    This topic has been deleted. Only users with topic management privileges can see it.
    • jordanurbsJ Offline
      jordanurbsJ Offline
      jordanurbs
      wrote last edited by jordanurbs
      #1

      Anyone ever resolve this yet? I can't get n8n to work with just the N8N_ALLOWED_ORIGINS in the .env

      1 Reply Last reply
      0
      • J Online
        J Online
        joseph
        Staff
        wrote last edited by
        #2

        @jordanurbs where did you find that option ? it's not in https://docs.n8n.io/ .

        Instead of having the frontend call n8n directly (which requires cors), call it via your backend instead . I think you will have to call it via the backend anyways to not expose any api tokens .

        1 Reply Last reply
        0
        • J joseph moved this topic from Feature Requests
        • robiR Offline
          robiR Offline
          robi
          wrote last edited by
          #3

          Webhooks FTW

          Conscious tech

          1 Reply Last reply
          1
          • jordanurbsJ Offline
            jordanurbsJ Offline
            jordanurbs
            wrote last edited by
            #4

            Well I feel stupid but I was using https://localhost:3000 instead of http://localhost:3000 in my .env file (on cloudron) and then it started working.

            May or may not have been a problem if I'd skipped that step and just put it in in the authorized header parameter on n8n

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