+ Reply to Thread
Results 1 to 10 of 10

Thread: Cannot access localhost

  1. #1
    Join Date
    Jun 2009
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Question Cannot access localhost

    For some reason, chrome prompts me for a username and password when I try to access localhost, as part of my development effort.

    I tried entering every username and pass I could think of, but nothing worked. I tried accessing localhost with internet explorer and firefox and had no problem at all.

    I also tried reinstalling chrome...didn't work. BTW, my hosts file looks fine and the IIS is configured properly to allow anonymous access.

    Everything was working fine until today. I used it yesterday with no problems whatsoever.

    Any suggestions?

  2. #2
    Join Date
    Sep 2008
    Location
    Bangkok
    Posts
    1,259
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    check the proxy settings of your browser

  3. #3
    Join Date
    Jun 2009
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Quote Originally Posted by sulasno View Post
    check the proxy settings of your browser
    Thanks for the reply.
    Could you please elaborate? I'm not sure how and what I'm supposed to be looking for.

  4. #4
    Join Date
    Sep 2008
    Posts
    103
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Chrome 2.xx ignores the Windows proxy settings...


  5. #5
    Join Date
    Jun 2009
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Thanks. I chose options >> under the hood >> change proxy settings.

    I then clicked on LAN settings, checked the use proxy server and entered 127.0.0.1 port 8118. It did not work. Now, when I try to reach localhost, I get a message saying the page is not available.

    Any suggestions?

  6. #6
    Join Date
    Sep 2008
    Posts
    103
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Quote Originally Posted by NoamBarz View Post
    Thanks. I chose options >> under the hood >> change proxy settings.

    I then clicked on LAN settings, checked the use proxy server and entered 127.0.0.1 port 8118. It did not work. Now, when I try to reach localhost, I get a message saying the page is not available.

    Any suggestions?
    As I said, the new versions of Chrome seem to ignore the Windows proxy settings, so the procedure you followed no longer works. You now are forced to use the "--proxy-server" command line switch.

    1. Create a shortcut for Chrome
    2. Right click the shortcut and choose "Properties"
    3. In the Target box, you'll see something like
    Code:
    "C:\Documents and Settings\...\Local Settings\Application Data\Google\Chrome\Application\chrome.exe"
    4. Outside of the last quote mark, add a space and then the something like the following
    Code:
    --proxy-server=xxx.xx.xx.xx:yyyy
    where xxx.xx.xx.xx is the proxy ip address and yyyy is the port. (to use Privoxy, that would be: --proxy-server=127.0.0.1:811.

  7. #7
    Join Date
    Jun 2009
    Posts
    39
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Cool

    Quote Originally Posted by NoamBarz View Post
    For some reason, chrome prompts me for a username and password when I try to access localhost, as part of my development effort.

    I tried entering every username and pass I could think of, but nothing worked. I tried accessing localhost with internet explorer and firefox and had no problem at all.

    I also tried reinstalling chrome...didn't work. BTW, my hosts file looks fine and the IIS is configured properly to allow anonymous access.

    Everything was working fine until today. I used it yesterday with no problems whatsoever.

    Any suggestions?
    What version of Chrome? (IIS/VS?, OS, FF, IE versions wouldn't hurt also)

    Where is the folder IIS is using located? (NTFS vs FAT32 or a UNC path can/does make a difference)

    Does FF prompt you at all for a password?
    Note: While I don't doubt your statement "IIS is configured properly to allow anonymous", my experience has been that, that is not always as clear an obvious as it should be. Allowing "anonymous" access is only one part. Clear text login and I_USER needs to be in the everyone group AND/OR the NT ACL needs to explicitly allow I_USER rights to ALL folders (root and virtual) the configured web site is using. If under NTFS or not does make a difference, as there a few not so obvious gotchas' there too.

    While the above comments about proxy support are at the very least informative, I am struggling to understand how they are relevant. I mean localHost is the last thing you would ever want to use a proxy for, right? Are you using a proxy at all? If so I missed that...

    Note: I have .NET (VS 2008 Enterprise) + XP Pro and cannot duplicate your problem using Dev Channel Release 3.0.187.1. with DNS prefetching enabled and the phishing filter is not. (both seem like they could be issues here)

    While I do not have I_USER and full anonymous access enabled, my local username/password works fine. And is also required, as would it be normally, for FF to access it as well while IE by default does not require it using integrated authentication.

    Glad you are testing this issue against FF as well since the clear text login is a big part of this puzzle and generally the 1st suspect.

    If our software versions are similar, I would suggest that you and I both, step by step, create a new website instance under IIS, disable the default one, and use identical folder location, rights and so on.

  8. #8
    Join Date
    Jul 2009
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Try:

    IIS
    Propiedades del sitio virtual - Properties of the virtual site
    Seguridad de directorios - Directories security
    Control de autenticación y acceso anónimo - modificar - modify
    Marcar: Acceso anónimo y desmarcar el resto. - Check anonymous and uncheck any other.

    This worked for me.

  9. #9
    Join Date
    May 2011
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default maybe you need to add some exceptions that....

    maybe you need to add some exceptions(addresses) that you do not need to access via proxy.
    Just like the pic attached.


    Last edited by zzlydm; 05-17-2011 at 09:07 PM.

  10. #10
    Join Date
    Nov 2011
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi , I have the same issue , I wanna use 127.0.0.1 : 1080 , it works well for firefox but not in chrome with 15.0.874.106 m version
    I've tried all the things said above , but still not working , can you help me please ? :/

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Search Engine Optimization by vBSEO 3.6.0