Toku here.
I've been without GitHub for 2 years now, and I'm getting sick of it.
In terms of web connection, I get a basic "This site can't be reached" - ERR_CONNECTION_REFUSED.
Attempting to use the desktop app results in more information
Image of 443 port error - more connection refusals.
Image of curl command result
I'm running Win10 Home build 19044, connected to a private home network with no restrictions. What would be causing this?
Tried reconfiguring DNS, and it simply didn't change anything.
At the suggestion of FiddlingAway, I resynced my system time, to no effect.
For reference, I am living in the US, so there should be no issues connecting due to a countrywide ban. The web interface does not load, even on a VPN.
I have set up a WAMP development server on a Windows 8 machine and it works very well when accessed by http://localhost, however when accessing same page by IP address (whether from the same machine on which WAMP server is hosted or from different machine on the network) it is incredibly slow.
For example, a typical page takes 0.2 seconds to load through localhost, and 9 seconds to load through IP address.
Would anyone know what could be the issue?
I've set up a website on my localhost but I want to test out how multiple users will use the site, so I'd like to be able to connect another computer for this. I've looked at a number of tutorials including How do I connect to this localhost from another computer on the same network?. I have done steps 1 & 2 but step 3 doens't seem to be working. I'm running windows XP on my localhost machine and Windows 7 on the external computer and would really appreciate your help with this, thank you.
Scenario: I have an ASP.NET MVC application developed in Visual Studio 2008. There is a root folder named "Content" that stores images and stylesheets. When I run locally (using Cassini) and browse my application, every resource from the "Content" directory is always downloaded. Using Firebug, I can verify that the web server returns an HTTP 200 ("ok").
Desired: I would like for Cassini to return HTTP 304 ("not modified") instead of 200. This is the behavior when running the site under IIS7.
Reasoning: The site I am working on has a large number of static resources (often as many as 40 per page). Browsing the site is very fast on IIS7, because these resources are (correctly) cached by the browser. However, browsing the site on my local machine is painfully slow.
Pages that render in under 1 second on IIS7 take over 30 seconds to render on Cassini. It's actually faster for me to upload the entire website every few minutes and test from there. (Yes, I recognize that this is perverse and crazy.)
So: how can I instruct/trick Cassini into treating the "Content" directory like IIS7 does?
Are you sure the problem is caching? Because the content does get cached correctly on my machine when I run the application on Cassini.
I think the problem you're having could be Firefox's under-performance with resolving IPv6 addresses, which causes a very annoying delay on loads with addresses like http://localhost:55555.
What I did to change this behaviour was to change the network.dns.disableIPv6 preference on about:config to true on Firefox. I suggest trying that.
I've had a similar problem in Chrome. To resolve this uncomment the IPv4 localhost line in you hosts file. Apparently these are commented by default in Windows 7.
127.0.0.1 localhost
#::1 localhost
Another option for you is to simply skip Cassini and debug under IIS. It's pretty straightforward, and won't take you ten minutes to get up and running. Browse 20 of your pages on Cassini, and you've used that time anyway ;)
One thing I've noticed isn't always in the guides, is that if you want to debug on a different address than http://localhost/ you need to manually set the host to your local IIS. This is done by adding a line in the hosts file, located at
C:\Windows\system32\drivers\etc\hosts
Open the file with notepad (you need to "Run as Administrator" in order to be able to save if you're using Windows Vista and have User Account Control turned on...) and add your host. For example, to debug under http://mysite/ you add
mysite 127.0.0.1
I have some pages on my local machine, accessed via localhost, that are horribly slow to open/load using IE8, but very fast using Firefox, Opera, Chrome and Safari.
They used to load really quickly using IE7.
I produced a cut down page to test - to see what was causing the problem - and seriously, the most simple page possible causes it! I.e:
<html>
<head></head>
<body>
Hello!
</body>
</html>
Takes about 15 seconds to open on localhost in IE8, and is instant on all other browsers! Why? What can I do to resolve this?
By the way, tried this on a Web server, connecting via a URL via IE8, and it was basically instant when opened via IE8 via the Web/Web server!
I have Windows Update enabled, so should have the latest of everything.
Note: I only noticed this after my internet connection changed, which was about 2 weeks after IE8 was installed. Possibly that is coincidence, it MAY have started with the install of IE8, I am actually not sure. It is definitely happening now though.
The URL I am using is: http://localhost/fb/starttest.htm
Help!
Try the following:
1- Navigate to C:\Windows\System32\drivers\etc
2- Open the file hosts using any text editor
3- Add this line to the end of the file
127.0.0.1 localhost
4- Before you save this file, you need to make sure that any program that access the internet (browsers etc.) is closed - Save the file and test it
Under Tools -> Internet Options -> Connections -> LAN Settings, is the box "Automatically detect proxy servers" checked?
If so, that does a DNS request to wpad.(domain search suffix) to discover proxy servers via their Auto Discovery Protocol.
If nothing responds, the query will have to timeout before it gives up.
I also had this exact same problem recently - 'localhost' taking 15 seconds to load, but 127.0.0.1 loading instantly.
However, I have now fully solved my problem, so I write here in the hope that it will help someone.
My problem coincided with the purchase of a D-Link DIR-655 wireless router, so after trying many of the kindly offered 'fixes' on this forum, I turned back to my router settings in search of an answer.
I eventually discovered a setting on the SETUP - NETWORK SETTINGS page. The 'Enable DNS Relay' box was checked, so I read about it, and it apparently allows the router to lookup DNS addresses from the ISP's server. This is obviously not desired for a 'local' address on my own PC, and so I tried unticking it.... and HEY PRESTO, IT WORKED!!!
I hope this work for some of you, too!
All the best,
Rob
I have exactly the same problem as you do, except I'm using IE7 (IE takes about 16 seconds to load localhost, while Firefox and Google Chrome loads it in an instant).
I don't have the autodiscovery for proxy checked either.
I also tried starting IE without add-ons (From Accessories->System Tools) and it didn't make a difference.
I found out that using 127.0.0.1 instead of localhost greatly improved the speed (like 2 seconds instead of 16 seconds!). However, I edited hosts file and I left only the line
127.0.0.1 localhost
and this didn't fix the problem. Need to dig some further.
Regards,
Nicolae