YouTube Feeds &/Or Timeout

katsimbris

I've had my Youtube feeds return with "server replied: 202 (Forbidden)" They were working a few hours ago.

Would anyone have an idea as to the nature of such an error? I have my feeds set to refresh every 30 minutes. Maybe with 75 Youtube feeds, I tapped their server too much, and they blocked my IP address? And I should set the YouTube feeds to update farther apart?

Thank you for any input.

Sheldon
Hi,

Hi,

this seems to be an access problem.

How did you create your Youtube feeds?

Are they related to an account? If so maybe there is something wrong with the authorization.

Did you configure the feed authorization.in QuiteRSS?

Kind regards,

Sheldon

katsimbris
Thank you for replying,

Thank you for replying, Sheldon. Please allow me to update the situation. I have changed physical locations (work to home), and updated the database file from the backup I made. When I updated, the Youtube RSS started working. I'm not sure why it's working here, or now. Nevertheless, I will post some of the rss feeds I am working with. They require no special 

Let me post some examples:

https://www.youtube.com/feeds/videos.xml?channel_id=UCznXuWp59-geC7F-jaF...

https://www.youtube.com/feeds/videos.xml?channel_id=UC3LqW4ijMoENQ2Wv17Z...

https://www.youtube.com/feeds/videos.xml?channel_id=UCi7GJNg51C3jgmYTUwq...

Thanks for any advice you can give.

katsimbris
Update:

Update:

Back at my work location, receive the same "server replied: 202 (Forbidden)" error.

Whatever is happening it's based on my locatIon and not the fault of Quite RSS.

Mike K

 

Sheldon
Hi,

Hi,

I just tested all your feeds and they worked fine. So the problem doesn't seem to be directly related to QuiteRSS.

Youtube requires the https protocol. If your feeds work at one location and not at another as described by you I assume the problem to be related to https..

This can be caused by

- a missing or expired SSL certificate

- a firewall blocking or restricting the https traffic.or especially Youtube (very common in company networks)

You mentioned that the problem just occured so maybe there have been made some changes to the security settings at your working location.

Kind regards,

Sheldon.

katsimbris
Agreed. Thank you for

Agreed. Thank you for verifying!

Mike K