Getting lots of 503 responses from RSS-Bridge Server

[Dean-Corso]

Hello @dvikan,

since a while now I'm getting very much 503 responses (503 Service Temporarily Unavailable) from my created RSS Bridges every time when I update my feeds in my RSS tool. But Why? Did you set any request value X to your server to limit them? Just wonder about it because before everything was working without that issue and now I get it all the time. Why did you change that?

Example: I made a feed folder with ~30 feeds bridges and normally I update the entire feed folder at once in my RSS tool and just a few of them getting checked successfully and the rest gets marked with an red cross (failed) and in debugger I see the response reason 503. That's pretty annoying because I have to check the other feeds then manually one by one or select them manually to do another checks till all feeds was checked successfully. Not very comfortable of course.

How to deal with that annoying problem now and why did you limit the requests? So unfortunately I can not set any custom request timeout to wait a second +/- before sending next request in my RSS app (QuiteRSS) you know. So now the handling is not good anymore as before. Can you change that back or increase the requests counts or anything to make it better? Thanks.

[dvikan]

yeah sorry about that. it is rate limiting enabled on nginx in order to not overload the server.

have upped the limits a bit.

[Dean-Corso]

Hi @dvikan,

thanks for checking this problem and adjusting it. So on first test today it seems to work better now. 😃 I will check out the results for the next few days to see whether I got some issues or not and will send some feedback about it when I still get some bad results. Otherwise for the moment I just wanna say thank you again.

[Dean-Corso]

Hi @dvikan,

so I got some new trouble when updating my bridges. Now I get new fail responses from RSS Server called "429 Too Many Requests" or "500 Internal Server Error". Not good. Same problem as before only with an other response messages. Still not working better or good as before the whole problem thing started (before you changed your Server setup). I will show you an example. I created some Youtube bridges using the RSS made "YouTube Bridge". I made 15 YT feeds in my RSS tool and today I did log the entire send & responses of all request my RSS tool does send. I got 10 feeds checked correctly and the rest of 5 feeds did fail (429) from your Server. In total QuiteRSS did send 40 requests to your Server to check 15 feeds...

Total Feeds:    15
Total Requests: 40
----------------------------------------
HEAD    10  Success     200
GET 10  Success     200

HEAD     5  Failing     429
GET 15  Failing     429
----------------------------------------

The QuiteRSS tool does maximal send 3 requests a feed... ...and summarized it look so in total requests for those 15 RSS YT bridges.... ...and that's pretty disappointing of course to get those fails every time with any RSS bridges (also others). As I said, a while ago I had no problems with any RSS bridges but the Server changes you made are a problem now. Even in case when I increase the requests tries to 3 instead of 2 your Server will send response error "500 Internal Server Error". All in all I can not check all my RSS created bridges at once (one flow) and I get those feed checking fails and all failing feeds I have to check manually. So my request to you is whether you can adjust your Server into a more user friendly request handling condition? Don't setup it so sensitive to send quickly 429 to many requests status back or any other 500 codes you know. Somehow this problem sucks and I hope that you can turn it back (more or less) to receive a better feed checking flow without errors. Would be nice if you could do something about it. Thanks.

[dvikan]

i changed rate limting status code from 503 to 429.

your reader does 40 http requests in under 1 second. this is what triggers nginx rate limting.

the 500 error error code indicates an actual error.

i have increased rate limits again, but as you can imagine the server is getting lots of traffic in total and im paying for the server out of my own pocket.

[Dean-Corso]

Hi @dvikan,

thank you for adjusting your server again. So I tried the same again today and now it seems to work without any error responses. By the way, I was checking out the network options in QuiteRSS and see that I can change the send requests for all feeds. In default state the value is set to 10 and now I did lower it to 5. So this should work better now to reduce sending to much requests at once. Sorry about that and thank you again.

[dvikan]

okay cool