Getting status code 407 when using the proxy running on EC2 server, but works well when started on local machine

[sumanpoluri]

I installed and configured scrapoxy on my local machine (macOS) per the AWS / EC2 section in the documentation and it works well. I am able to run scripts using the proxy IP http://localhost:8888 without issues.

2018-05-11 01:49:28 [scrapy.core.engine] DEBUG: Crawled (200) <GET http://g20.bimmerpost.com/robots.txt> (referer: None)
2018-05-11 01:49:34 [scrapy.core.engine] DEBUG: Crawled (200) <GET http://g20.bimmerpost.com/forums/forumdisplay.php?f=701/> (referer: None)

Then, I installed and configured scrapoxy on an AWS EC2 instance the same way. I started scrapoxy and I see the EC2 instances getting created and managed by it. I can also access the GUI and view those instances at http://XX.XX.XXX.XXX:8889/#/home/instances, where XX.XX.XXX.XXXX is the IP of the EC2 machine scrapoxy is running on. However, my scripts are failing with the status code 407 when using the proxy IP http://XX.XX.XXX.XXX:8888.

2018-05-11 02:26:35 [scrapy.core.engine] DEBUG: Crawled (200) <GET http://g20.bimmerpost.com/robots.txt> (referer: None)
2018-05-11 02:26:42 [scrapy.core.engine] DEBUG: Crawled (407) <GET http://g20.bimmerpost.com/forums/forumdisplay.php?f=701/> (referer: None)

Is there something I need to configure differently either in my scrapy scripts (that are running on my local machine) or in the scrapoxy config that is running on the EC2 instance?

[fabienvauchelles]

Hello @sumanpoluri , did you tried to set a password ? Fabien.