Setup question // n8n on Render.com + Supabase backend: polling problem

Questions
1
Does anyone familiar with n8n's backend tech have an idea what service could be hitting Render, and whether this is a configuration that can be set off?

Information on your n8n setup

  • n8n version: → latest version
  • Database (default: SQLite): → Postgress on Supabase
  • Running n8n via (Docker, npm, n8n cloud, desktop app): → Docker, on Render.com
  • Operating system: → Ubuntu
2

Hey @Wicked_AI_Ware would you like to expand on this question, it is not clear what you are referring to.

3

Sure:

So, I have explained my setup - I hope that is clear.
Render (for free accounts) works in this way: it spins the n8n docker instance down after a few seconds of not using it.
It is then ONLY spins up again when a WF is used/needs it.

The problem is this:

  • I have ZERO active WFs (I use this environment to prototype)
  • I had not used n8n at all in June. The only activity as on June 12th to update the Docked image to the latest n8n version.

Despite this month of inactivity, I saw my Render.com quota was almost maxed out.
So something was off. I reached out o Render to ask for more info and they explained their systems get hit non stop.
Hence my question: anyone know if this is normal n8n backend behavior / whether this is configurable?

Is this more clear?

4

Wouldn’t render people know what was hitting the instance?

5

Of course I asked - this is what I got back: “all the requests come from the 109.236.62.153 IP address. However, that IP address seems to belong to Packethub, so it is probably too generic to know exactly what is hitting your service.
Maybe posting on N8N forums may help. There may be something they know that would cause this.“

6

I am not aware of any relation between packethub and n8n (which doesn’t of course necessarily means there isn’t one). You could reach out to Packethub and try to request information about the source of the requests, but I wouldn’t hold your breath.

7

No you’re right (that was also the guess from the Render Helpdesk as you may have read).
There must be “something” from the n8n setup (either n8n itself or n8n’s backend on Supabase) that has some keep-alive mechanism (pointless, in my case). To keep the Date/Time correct or so? I have no idea, hence this post. Someone more familiar with what n8n does under the covers may know.

8

No one has any idea? (if someone from n8n is interested, I can bring you in contact with the engineer from Render)

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.