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


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
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

Cloudron Forum

Apps | Demo | Docs | Install

n8n: execute-node-never-end

Scheduled Pinned Locked Moved Solved N8N
22 Posts 5 Posters 1.3k Views
    • 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.
  • JOduMonTJ Offline
    JOduMonTJ Offline
    JOduMonT
    replied to BrutalBirdie on last edited by JOduMonT
    #7

    @brutalbirdie thank you for your digging, but I just see a bunch of line with code and could only deduce you want to tell me than the issue somewhere in the process/task_queues.js so on their side 😉

    oh! I see you posted it also on their community 😉
    the strange thing, is this is not happening if I use SQLite as DB, but happen with Postgres and MySQL.

    1 Reply Last reply
    0
  • JOduMonTJ Offline
    JOduMonTJ Offline
    JOduMonT
    wrote on last edited by JOduMonT
    #8

    It seems to be the NGINX cache, because on my side

    I opened the port 5678 and access it directly with this port instead of behind NGINX
    and n8n + mysql or postgres works well if we abstract the proxy (NGINX).

    and now it works well, even behind NGINX if I use

    proxy_pass http://localhost:5678;
    proxy_set_header Connection '';
    proxy_http_version 1.1;
    chunked_transfer_encoding off;
    proxy_buffering off;
    proxy_cache off;
    

    @BrutalBirdie please modify the nginx proxy in consequence.

    nebulonN BrutalBirdieB 2 Replies Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    replied to JOduMonT on last edited by nebulon
    #9

    @jodumont nice, so I guess that was already part of the nginx within the app container https://git.cloudron.io/cloudron/n8n-app/-/blob/master/docker/app/pkg/nginx.conf#L64

    However Cloudron also has another reverse proxy nginx instance on the system, which lacks those tweaks. Have to see how can tell the system about this.

    Is there a good way to reproduce the problem in the first place, that way we can see which nginx setting fixes it and maybe it could be set normally in the system config as well then.

    BrutalBirdieB 1 Reply Last reply
    1
  • BrutalBirdieB Offline
    BrutalBirdieB Offline
    BrutalBirdie Staff
    replied to nebulon on last edited by
    #10

    @JOduMonT not sure if this is really solved tho since the issue still persists on cloudron site.

    Like my work? Consider donating a drink. Cheers!

    nebulonN 1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    replied to BrutalBirdie on last edited by
    #11

    @brutalbirdie I guess @JOduMonT has also tweaked the system nginx config for the app manually. Of course this won't be persistent for the moment, but good to know. We have to find a solution on the platform for this though.

    BrutalBirdieB JOduMonTJ 2 Replies Last reply
    0
  • BrutalBirdieB Offline
    BrutalBirdieB Offline
    BrutalBirdie Staff
    replied to nebulon on last edited by
    #12

    @nebulon huh I got to test this.
    Since @JOduMonT wrote this:

    @BrutalBirdie please modify the nginx proxy in consequence.

    I got the impression he did this fix for his local docker-compose setup.

    https://community.n8n.io/t/execute-node-never-end/6899/17?u=brutalbirdie

    Now I am even more confused. @JOduMonT could you please clear up what you exactly did?

    Like my work? Consider donating a drink. Cheers!

    1 Reply Last reply
    0
  • BrutalBirdieB Offline
    BrutalBirdieB Offline
    BrutalBirdie Staff
    replied to JOduMonT on last edited by
    #13

    @jodumont I did fix the manual execution.
    Update coming out soon.

    Like my work? Consider donating a drink. Cheers!

    girishG 1 Reply Last reply
    1
  • girishG Offline
    girishG Offline
    girish Staff
    replied to BrutalBirdie on last edited by
    #14

    @brutalbirdie Ah great. Does this also fix (or is it even related to) https://forum.cloudron.io/topic/5415/connection-lost-n8n/ ?

    BrutalBirdieB 1 Reply Last reply
    0
  • BrutalBirdieB Offline
    BrutalBirdieB Offline
    BrutalBirdie Staff
    replied to girish on last edited by
    #15

    @girish not sure about that since this issue is already resolved and in the automated tests and I cant reproduce his error.

    Like my work? Consider donating a drink. Cheers!

    bencreynoldsB 1 Reply Last reply
    1
  • bencreynoldsB Offline
    bencreynoldsB Offline
    bencreynolds
    replied to BrutalBirdie on last edited by
    #16

    @brutalbirdie I am having this issue as well. Is there going to be a fix implemented? I have no idea how to edit my Nginx settings in cloudron.

    girishG 2 Replies Last reply
    1
  • girishG Offline
    girishG Offline
    girish Staff
    replied to bencreynolds on last edited by
    #17

    @bencreynolds The fix is ready. We will publish a new package asap.

    1 Reply Last reply
    3
  • JOduMonTJ Offline
    JOduMonTJ Offline
    JOduMonT
    replied to nebulon on last edited by
    #18

    @nebulon said in n8n: execute-node-never-end:

    I guess @JOduMonT has also tweaked the system nginx config for the app manually.

    no I didn't, of course I could build another Cloudron at home (as development and test it) but in Prod I touch nothing, you are the master of my ProdMachine 😛

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to bencreynolds on last edited by
    #19

    @bencreynolds I have pushed an update, can you please check?

    bencreynoldsB 1 Reply Last reply
    0
  • bencreynoldsB Offline
    bencreynoldsB Offline
    bencreynolds
    replied to girish on last edited by
    #20

    @girish I haven't had time to come back to this until now. This update did not fix the issue. Replicate the issue by creating an n8n instance and attempting to execute a GET request on google.com. It just spins forever and it's impossible to stop the execution.

    Stopping the server while its infinitely executing will return the expected result of the GET request.

    girishG 1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to bencreynolds on last edited by
    #21

    @bencreynolds Is this using the HTTP Request node? Seems to work for me. The URL i tried is https://api.cloudron.io/api/v1/apps/io.n8n.cloudronapp (this gives info of the n8n package in JSON format)

    bbee4f82-8f62-4171-ab3c-866aa0aa65dd-image.png

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #22

    I tried google.com as well. One thing is search engines usually block "crawlers" based on the IP address. They don't like crawlers from VPS usually (same goes for most services like yelp etc). So, can you check if you have GET requests fail to normal services and not to google?

    63b2598e-257d-4fef-beb9-be610489b4b2-image.png

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

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