search

sjitech / proxy-login-automator

A single node.js script to automatically inject user/password to http proxy server via a local forwarder
MIT License
392 stars 89 forks source link

chrome unable to access localhost site when using proxy-login-automator as proxy server #11

Closed ZodsPlan closed 6 years ago

ZodsPlan commented 6 years ago

Awesome work! Thank you!! I ran into one issue...

I want to access http://localhost:3000 with google chrome (i'm running a local web application)...

I set google chrome's proxy server to the proxy-login-automator server. When I attempt to go to the "http://localhost:3000" in the browser, a popup occurs asking for authentication from "cfauth.com"

Any ideas? Keep up the great work!

jjqq2013 commented 6 years ago

Thanks for your feedback.

Are you using PAC?

You can specify a bypass list in chrome command line to avoid using proxy for localhost.

Regards

2017年11月29日(水) 0:58 ZodsPlan notifications@github.com:

Awesome work! Thank you!! I ran into one issue...

I want to access http://localhost:3000 with google chrome (i'm running a local web application)...

I set google chrome's proxy server to the proxy-login-automator server. When I attempt to go to the "http://localhost:3000" in the browser, a popup occurs asking for authentication from "cfauth.com"

Any ideas? Keep up the great work!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sjitech/proxy-login-automator/issues/11, or mute the thread https://github.com/notifications/unsubscribe-auth/AE_djO_fz5c_iQ2UOJqbBArXJNupapjwks5s7C2fgaJpZM4QteNc .

ZodsPlan commented 6 years ago

Thanks for the feedback. I am not sure if I am using PAC. To my understanding, PAC would be something configured at the server level? In that case, I am behind a corporate proxy so I do not have access to those configurations. I tried to specify --proxy-bypass-list="localhost:3000" and --proxy-bypass-list="localhost" with no luck.

jjqq2013 commented 6 years ago

You can check who is listening at port 3000, just by “netstat -an” or similar linux cmd, it might exists two or more processes catching 3000, and some listen the ipv6, some ipv4, so maybe an application happened to listen 3000 it overrided the existing one which really needed to do underline proxy work.

2017年12月7日(木) 0:10 ZodsPlan notifications@github.com:

Thanks for the feedback. I am not sure if I am using PAC. To my understanding, PAC would be something configured at the server level? In that case, I am behind a corporate proxy so I do not have access to those configurations. I tried to specify --proxy-bypass-list="localhost:3000" and --proxy-bypass-list="localhost" with no luck.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/sjitech/proxy-login-automator/issues/11#issuecomment-349668191, or mute the thread https://github.com/notifications/unsubscribe-auth/AE_djBNbPoH1Nj0G4k8HUG22SPm8ZF-Uks5s9q5ygaJpZM4QteNc .

jjqq2013 commented 6 years ago

Also check 8080 etc.

2017年12月7日(木) 8:16 Jin Qian osexp2003@gmail.com:

You can check who is listening at port 3000, just by “netstat -an” or similar linux cmd, it might exists two or more processes catching 3000, and some listen the ipv6, some ipv4, so maybe an application happened to listen 3000 it overrided the existing one which really needed to do underline proxy work.

2017年12月7日(木) 0:10 ZodsPlan notifications@github.com:

Thanks for the feedback. I am not sure if I am using PAC. To my understanding, PAC would be something configured at the server level? In that case, I am behind a corporate proxy so I do not have access to those configurations. I tried to specify --proxy-bypass-list="localhost:3000" and --proxy-bypass-list="localhost" with no luck.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/sjitech/proxy-login-automator/issues/11#issuecomment-349668191, or mute the thread https://github.com/notifications/unsubscribe-auth/AE_djBNbPoH1Nj0G4k8HUG22SPm8ZF-Uks5s9q5ygaJpZM4QteNc .

ZodsPlan commented 6 years ago

The PAC solution worked. I found out the PAC file being used here and configured everything according to your instructions for the PAC file. Worked like a charm. Good work! Thank you.