Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to fix/retry on this error "The proxy responded with 590 UPSTREAM503" ? #542

Open
geminigeek opened this issue Jul 22, 2024 · 3 comments

Comments

@geminigeek
Copy link

geminigeek commented Jul 22, 2024

hi,

i am using got-scraping with proxy-chain , when i make a request from got-scraping , i get a burst of these errors some time , not always.

is there a way to diagnose and fix this ? or is this a got-scraping issue ?

error.message

The proxy responded with 590 UPSTREAM503
The proxy server rejected the request with status code 590 (UPSTREAM503)

i am thinking about two options/way to fix this.

  1. with a retry option that can detect it and retry with got built in retry mechanism, How to do this ?
  2. an option to catch this error in try catch block and retrying the request. this i have implemented but i want got to handle this with its retry! How to handle this
@jancurn
Copy link
Member

jancurn commented Jul 22, 2024

The upstream proxy is failing with HTTP 503 error.

Currently, it's not possible to automatically fallback to another proxy server, this needs to be done on the client level. But it would be an interesting feature to support...

@geminigeek
Copy link
Author

hi,
thanks for a quick reply , is there a way i can send a different error code from proxy-chain to got-scraping so got will retry the request , the issue is i am not getting any error code in got , so i cannot put it in retriable error codes

@jancurn
Copy link
Member

jancurn commented Jul 22, 2024

I don't think so. You should be able to get the 590 error in got though

@fnesveda fnesveda added the t-platform Issues with this label are in the ownership of the platform team. label Jul 31, 2024
@fnesveda fnesveda removed the t-platform Issues with this label are in the ownership of the platform team. label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants