How to troubleshoot an RSS trigger error when the feed URL works in a browser tab?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi there, just signed up and started an RSS trigger, but it errors out on the source feed, so I’m stuck.

The feed URL works fine in a browser tab.

2

Hello , could you share your error you faced?

3

HI Sure… let me get back to it… uhh it’s been removed… hold on let me remake it…

would it be helpful to give you the feed url or the workflow url ?

4

> would it be helpful to give you the feed url or the workflow url ?
Yeah this would be great

5

https://www.disclosurenews.it/category/lev/feed

6

it’s odd that the workflow lost my trigger info…

7

any maintenance going on that lost state?

8 
Pipedream detected that component was still running code. Make sure you await all promises. (Reason: TLSSocket)
9

Not something that helps one resolve the error ;-/

10

Hello , the link to the feed is returning error. Would you mind checking again?

11

I have the same message, check the url in a browser, works for me

12

I tried to access it from my browser but couldn’t

13

Or maybe the feed is not using RSS format?

14

image.png

15

Weird.

Hello , as you’re familiar with the RSS feed, could you check this issue when you have time?

16

sure, let me see…

17

yeah definitely seems like a bug! I can access the URL just fine via the HTTP request action (so the request works from our AWS environment), but I see the server error issue when using the RSS trigger, as well.

I may have been the last one to touch that RSS trigger, so apologies if it was buggy!

18

thanks for looking into it Alyson

19

perhaps it’s the difference between the feed xml file and the feed/ dir with an index file

20

I found the error, when we fetch the RSS from the URL, our code is adding the header user-agent=@PipedreamHQ/pipedream v0.1 which seems incompatible with the webserver that this RSS is hosted, but the code who adds this header seems to be added by and I’m not sure the reason… when I commented this section, the source worked for me, I’m adding a screenshot as evidence.