n8n self-hosted definitely has a lot of troubles with caching of community nodes… Please try to remove the ScrapeNinja node, rebuild docker container and re-install the node. 0.4.1 is the correct version and operations list should look different.
Hi Anthony
That did the trick. I had to wait until I got home to upgrade the server and rebuild. Will now test out the new nodes.
1 Like
Hi @Anthony,
I’m super excited about your scraper. Fantastic work!
I tried to run it on my self-hosted instance and got an error during installation. When I tried to remove it for reinstallation, I got another error, in which I can’t remove it. I also tried to remove it via npm but no luck with that either. I’m getting a lot of bans on Reddit and my only alternative to running this easily is here on n8n with your community node. Any suggestions?
1 Like
Hey @Carlos_Guimaraes did you manage to find a fix for this? It looks like cleaning cache of your n8n instance, and re-installing the n8n ScrapeNinja package might help.
Hi Anthony,
I couldn’t solve the problem. I’m going to clear the cache to see what’s happening. The error must be in my instance, because the problem doesn’t only occur with your node.
Thanks for the feedback.