kryo Posted March 6, 2016 Report Posted March 6, 2016 I've noticed a lot of 500 errors recently, usually these errors only happen once or twice per offer but I've noticed some cases where I'm completely unable to send a trade offer because it returns a 500 error each time I retry it. These errors are very hard to debug. I'm wondering if this is a temporary issue that everyone is experiencing, since I used to notice a lot of descriptive errors with eresult params. Also if there is some way to get the error info that would be great to know. I've tried printing the err, response, and body which are { [Error: HTTP error 500] code: 500 }, undefined, and undefined, respectively. Quote
Dr. McKay Posted March 6, 2016 Report Posted March 6, 2016 https://httpstatuses.com/500 500 just means Steam is broken and you'll have to try again later. There isn't anything you can do. Quote
kryo Posted March 8, 2016 Author Report Posted March 8, 2016 I think this is a bug with the new http requester. On the master branch I was getting this error: { [Error: HTTP error 500] code: 500 } I rolled back to v1.19 and now I get this instead: { [Error: There was an error sending your trade offer. Please try again later. (26)] eresult: 26 } Quote
Dr. McKay Posted March 8, 2016 Report Posted March 8, 2016 Good catch, that's indeed a bug. Fixed in v1.20.2. Were you on the beta version when you first made this thread? Quote
kryo Posted March 8, 2016 Author Report Posted March 8, 2016 Yeah, I have my own fork so I was using the latest code. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.