Upgraded to 1.112.5 and getting constant ngrok 120 requests per minute issues

Questions
1

Hi,

I have been using the community edition of n8n for a couple of months now and today updated to 1.112.5. I use free ngrok which has a request limit of 120 requests per minute.

Since upgrading, I keep blowing the 120 requests per minute limit. If I do 3-4 things in the menus (e.g. look at flows, personal flows, look at settings) it blows within about 30 seconds of use. I don’t have and flows running.

Is this a bug in the upgrade (I just let npx n8n do its thing) or in this version? I’ve never had this error before and the only thing I did was upgrade.

Any advice on how I can debug this? As I said, I have no active flows running.

Thanks

Describe the problem/error/question

What is the error message (if any)? 403

Please share your workflow - not specific to a workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.112.5
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npx
  • Operating system: ubuntu
2

Hey, revert to previous version to test and confirm if it’s not version related. You can also check the Network tab in the dev tools while navigating around the UI to check which requests are getting called a lot.

Another thing to try would be starting n8n with N8N_RUNNERS_ENABLED=false as a test.

3

Hey,

what’s happening here is the editor itself is eating up your ngrok quota. Even with no flows running, the UI makes a lot of background requests (polling, session checks, metadata). In version 1.112.5 this seems to have gotten a bit heavier – before the upgrade those calls were either less frequent or batched differently, which is why you didn’t hit the 120 req/min cap.

The usual fix is to keep the editor local and let ngrok handle only the webhooks. For example:

WEBHOOK_URL=https://<your-subdomain>.ngrok.io \
npx n8n start

Then open the editor at http://127.0.0.1:5678. That keeps the constant UI chatter off ngrok and leaves the quota for actual webhook calls.

If it still spikes after that, check the browser network tab to see which endpoints are firing most, and run with N8N_LOG_LEVEL=debug so you can catch if something in this release is polling too aggressively.

4

I downgraded to a previous version and switch the variable as you said, but still had the issue. Tracking the interactions, looks like I just need to be careful when jumping between menu options when using free ngrok.

Closing for now

1 Like