-
Notifications
You must be signed in to change notification settings - Fork 233
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
Error: request error from target (GET http://api.ipify.org/ #97
Comments
Update: it works but not stable! works with some requests but returns error 500 with others! |
use amazon aws. It works perfectly. |
@law2004 how much does it cost? roughly, don't send me their pricing page :) |
@law2004 well, same behavior on AWS :) |
Hello @mielguindi , |
I am getting the same error. Works perfectly from my machine using same credentials, but on my server I get the following: root@server:~ curl --proxy http://localhost:8888 http://api.ipify.org
[Master] Error: request error from target (GET / on instance i-031e7e4af6bdeeda2@34.250.68.251:3128): Error: socket hang up Looking at the logs: 2018-07-31T14:24:04.070121082Z app[web.1]: 2018-07-31T14:24:04.069Z - error: [Master] Error: request error from target (GET / on instance i-031e7e4af6bdeeda2@34.250.68.251:3128): Error: socket hang up
2018-07-31T14:24:04.070198465Z app[web.1]: at createHangUpError (_http_client.js:331:15)
2018-07-31T14:24:04.070232328Z app[web.1]: at Socket.socketOnEnd (_http_client.js:423:23)
2018-07-31T14:24:04.070265132Z app[web.1]: at emitNone (events.js:111:20)
2018-07-31T14:24:04.070304193Z app[web.1]: at Socket.emit (events.js:208:7)
2018-07-31T14:24:04.070337002Z app[web.1]: at endReadableNT (_stream_readable.js:1056:12)
2018-07-31T14:24:04.070369498Z app[web.1]: at _combinedTickCallback (internal/process/next_tick.js:138:11)
2018-07-31T14:24:04.070402511Z app[web.1]: at process._tickDomainCallback (internal/process/next_tick.js:218:9) |
hello @wdmtech , can you remove all rules and test ? thanks, |
Now I'm getting -- edit Actually, this was not the case, instances seem to keep being removed/added |
Hmm, instances seem to keep being removed and added. I'm using all the default config, as I just used the Dockerfile method (running on Dokku) |
It seems that when there's an instance ready to use,
|
I have this working now - seems to have been a problem running as a Dokku app instead of a stand-alone Docker container :-) |
Scrapoxy worked once with me
then after a while, when I run
scrapoxy http://localhost:8888
it returns the following:
2018-02-07T10:23:18.646Z - error: [Test] Error: Cannot get IP address: 500: [Master] Error: request error from target (GET http://api.ipify.org/ on instance 81613183@46.101.79.64:3128): Error: socket hang up
Do you have any idea how to fix this?
Thanks in advance,
Mostafa
The text was updated successfully, but these errors were encountered: