RSS Feed returns 403

Dear community,

I have an RSS Feed Trigger node set up where I am watching all of Airtable’s announcements:

I am self-hosting n8n on DigitalOcean and when trying to run the node it returns a 403 error.

The feed is not auth-protected, I can access it on the web, get it on make.com, AND even get it with the cloud-hosted n8n version.

I also tried the regular RSS node, but unfortunately with the same output. Weirdly I can get the content when making a regular HTTP call, so I assume it’s not a firewall issue with self-hosting.

Has anyone had a similar issue in the past or knows how to solve this bug? Thanks in advance! :slight_smile:
———
Node type

n8n-nodes-base.rssFeedReadTrigger

Node version

1 (Latest)

n8n version

1.74.3 (Self Hosted)

Time

03/02/2025, 11:23:58

Stack trace

NodeOperationError: Status code 403 at PollContext.poll (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/RssFeedRead/RssFeedReadTrigger.node.js:56:19) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:651:32) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:872:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1206:20

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Information is included

Hmm,

This runs just fine on my own self-hosted instance (see below). I wonder if your server is blacklisted for some reason - could you try the following from the commandline on your server?

curl https://community.airtable.com/idgpi83864/rss/board?board.id=announcements

Do you see the RSS feed, or the 403 error?

As I mentioned before, I am using DigitalOcean and somehow it shows me the regular RSS Feed, so I assume its a n8n issue

@bartv any idea on how to fix this?

Hi @zynera

I would recommend to update your n8n version, as I was also not able to recreate your issue on self-hosted.

can you guide me toward upgrading the n8n instance, I am running it on Digital Ocean, but I couldn’t find a guide to do it

and if this doesn’t work, is there another approach to fix?

Hi @zynera

Please follow the guide in our documentation here:

This isn’t explain at all the procedure for DigitalOcean?

We only support Docker or NPM installations. If DigitalOcean uses a different method, you need to ask them.

i just installed the newest version, the error still exists

Hi @zynera

Can you get any more information in the DigitalOcean logs? I’m afraid this may be something out of scope for n8n and you may have to reach out to the DigitalOcean support.

I am able to access the RSS feed through the DO console. so I doubt that this is the case to be honest… What kind of information do you need?

You can look into the execution logs of n8n on your instance and see if it’s throwing any errors that could point in the right direction.

Yeah this is the error message

Node type

n8n-nodes-base.rssFeedReadTrigger

Node version

1 (Latest)

n8n version

1.78.1 (Self Hosted)

Time

19/02/2025, 22:10:36

Stack trace

NodeOperationError: Status code 403 at PollContext.poll (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/RssFeedRead/RssFeedReadTrigger.node.js:56:19) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:652:32) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:882:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1216:20

I would really appreciate if anyone would be able to help me out with this one, been struggling with that for weeks now… @bartv @ria

I am getting the same thing on a substack RSS feed. I looked at the xml and the file is fine. It must somehow be blocking it is my guess.

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