-
Notifications
You must be signed in to change notification settings - Fork 138
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
Internal Server Error #125
Comments
Requests looks the same so my gues would be spamming requests to fast/much, using the same account on few computers or simply ea server overloaded :-) |
I've learned that occurs when two users on the same network, no matter who are on two different computers. Maybe it could be avoided by using a bridge or something, not. |
Two users using different accounts? |
Yes. If using two accounts simultaneously on the same network Do you know any way to prevent this from happening? Proxy with Python? |
Why don't you use exceptions to catch it and retry request little bit later? |
Yup, proxy should help |
It happens from time to time, not working up to 30 minutes after. |
Again... Something happened strange. No search items on the web app or with class fut It is as if the account no longer seek leave ... always gives the same error since yesterday. Only occurs with an account. https://utas.s2.fut.ea.com/ut/game/fifa16/transfermarket?type=player&start=0&num=16 {"debug": "", "string": "", "code", "503", "reason": ""} |
Hello, Regards |
flagged account |
Market transfer is blocked on webapp...that's probably why i cannot retrieve search request |
Again I'm here ... sorry :)
Well, occasionally get this error. I've been looking at previous cases and from what I've read, we can not do anything.
On requests when it comes out that error, there is a difference. No, if this can help you fix it. I have attached the debug. I do not understand the request makes it different.
Maybe this will help, but the same code for two different users, one gives me the error, and one not.
The difference is this
Could verify this request well before sending?
All debug
Sorry for my English
The text was updated successfully, but these errors were encountered: