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

Error: request error from target (GET http://api.ipify.org/ #97

Closed
ghost opened this issue Feb 7, 2018 · 12 comments
Closed

Error: request error from target (GET http://api.ipify.org/ #97

ghost opened this issue Feb 7, 2018 · 12 comments
Labels

Comments

@ghost
Copy link

ghost commented Feb 7, 2018

Scrapoxy worked once with me

scrapoxy

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

@ghost
Copy link
Author

ghost commented Feb 7, 2018

Update: it works but not stable! works with some requests but returns error 500 with others!

@law2004
Copy link

law2004 commented Feb 7, 2018

use amazon aws. It works perfectly.

@ghost
Copy link
Author

ghost commented Feb 7, 2018

@law2004 how much does it cost? roughly, don't send me their pricing page :)

@ghost
Copy link
Author

ghost commented Feb 9, 2018

@law2004 well, same behavior on AWS :)

@fabienvauchelles
Copy link
Owner

Hello @mielguindi ,
is it always happening ?
thanks,
fabien.

This was referenced Jul 29, 2018
@fabienvauchelles fabienvauchelles changed the title Problem Error: request error from target (GET http://api.ipify.org/ Jul 29, 2018
@fabienvauchelles fabienvauchelles added bug and removed bug labels Jul 29, 2018
@wdmtech
Copy link

wdmtech commented Jul 31, 2018

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)

@wdmtech
Copy link

wdmtech commented Jul 31, 2018

I'm not sure if this is a firewall issue - I added the following rules to my server running Scrapoxy:

image

@fabienvauchelles
Copy link
Owner

hello @wdmtech ,

can you remove all rules and test ?

thanks,
fabien

@wdmtech
Copy link

wdmtech commented Jul 31, 2018

Hi @fabienvauchelles

Now I'm getting [Master] Error: No running instance found consistently, even though I can see instances with ✅in the GUI

-- edit

Actually, this was not the case, instances seem to keep being removed/added

@wdmtech
Copy link

wdmtech commented Jul 31, 2018

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)

@wdmtech
Copy link

wdmtech commented Jul 31, 2018

It seems that when there's an instance ready to use, curling results in:

[Master] Error: request error from target (GET / on instance i-048e563502f5a44d9@34.246.172.241:3128): Error: socket hang up

@wdmtech
Copy link

wdmtech commented Aug 4, 2018

I have this working now - seems to have been a problem running as a Dokku app instead of a stand-alone Docker container :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants