N8n-nodes-puppeteer - error, please help me

Questions
1

The problem with the operation of the n8n-nodes-puppeteer node was described in detail here: Issue · GitHub

Information on your n8n setup

  • n8n version: 0.181.2
  • Database you’re using (default: SQLite): default:
  • Running n8n with the execution process [own(default), main]: default
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: npm
2

Hey @Faha, I am very sorry to hear you’re having trouble. This isn’t a node provided by n8n I am afraid and as such I am not very familiar with it. Your best bet is to wait for a response from the maintainer on GitHub here.

3

Hey @Faha
I was having the same issue getting n8n-nodes-puppeteer to work inside docker. I created the github repo n8n-puppeteer-docker to build and run a docker image.

4

Have a look at this gist from @drudge (the node creator) himself - Running puppeteer node in n8n · GitHub

5

Thanks @marcus, github repo saved me on the latest version ! The one from @drudge was not working for me.

6

Hey @marcus this discussion was so long ago, I don’t know if you will see this. But I am a noobie when it comes to coding, so I appreciate your patience. I am trying to host my n8n instance on Railway. I used the n8n template they provide which made it super simple to launch.

Screenshot 2025-03-03 at 2.24.10 PM
Screenshot 2025-03-03 at 2.24.10 PM1078×741 35.2 KB

I am now trying to figure out how to integrate puppeteer into this setup, and I am a little stuck. I can add a docker image to this current setup, but I don’t know how that would work if Railway already has it’s own docker image? Sorry, I don’t understand it all. Any guidance is super appreciated. I have been sending HTTP calls from N8n to Appify for a Loooooong time for some pretty simple Puppeteer scripts, so getting this in a n8n node form would be a life saver.