Closed alexpgates closed 2 years ago
I'm getting the HTTP error (presumably from using Node 16) with n8n-nodes-tidbyt on n8n installed via Docker using
docker run -it --rm \ --name n8n \ -p 5678:5678 \ -v ~/.n8n:/home/node/.n8n \ n8nio/n8n
I was still having issues after passing —experimental-fetch like this:
—experimental-fetch
docker run -it —rm \ —name n8n \ -p 5678:5678 \ -v ~/.n8n:/home/node/.n8n \ n8nio/n8n node —experimental-fetch
Does that seem right?
Is this the install method you recommend for n8n? Or do you recommend building my own image with Node 18?
Thanks for all your work in the Tidbyt community - - pretty jazzed with my new Tidbyt!
I'm getting the HTTP error (presumably from using Node 16) with n8n-nodes-tidbyt on n8n installed via Docker using
I was still having issues after passing
—experimental-fetch
like this:Does that seem right?
Is this the install method you recommend for n8n? Or do you recommend building my own image with Node 18?
Thanks for all your work in the Tidbyt community - - pretty jazzed with my new Tidbyt!