search

bdkjones / CodeKit2

CodeKit 2 Beta
98 stars 4 forks source link

CodeKit server issues #589

Closed ghost closed 8 years ago

ghost commented 8 years ago

Hi Bryan!

I Started having big issues last week half way through a project, when CodeKit's auto-reload went bad. After saving an asset, the browser most often will start waiting for an available socket before CodeKit will inject the new files. Sometimes this can take up to 20 seconds.

I'm mainly accessing CodeKit's server through localhost:5757, but issues also remain accessing through IP-address and Bonjour name.

The system hasn't been modified recently apart from latest version bumps of Chrome and Firefox (both after issues started appearing). I have also already ruled out possible local networking issues.

I'm happy to provide you with additional details and eager to sort this out rather quickly, since the issue has a big footprint on my workflow.

Cheers!

bdkjones commented 8 years ago

How, precisely, have you ruled out "local networking issues"?

bdkjones commented 8 years ago

None of those things have to do with name resolution. Try these three things:

  1. Use WiFi instead of ethernet. Same symptoms?
  2. Try a different network. Coffeeshop, work, etc.
  3. Reboot your networking devices (router, modem, etc.)

-Bryan

On 1Nov 2015, at 22:39, indrekpaas notifications@github.com wrote:

I guess generally -- I'm connected through ethernet as opposed to wifi, ping tests have no packets lost and other connections don't have difficulties.

Let me know if there's something more precise you'd recommend.

Cheers!

— Reply to this email directly or view it on GitHub https://github.com/bdkjones/CodeKit/issues/589#issuecomment-152931264.

sharvilak11 commented 6 years ago

I am facing the same issue at the moment. Chrome is giving me Waiting for Available socket , although it works fine in Firefox. Uninstalled chrome, deleted all chrome associated data. Still no success!

Did you get to know anytime later what had happened ? @indrekpaas

bdkjones commented 6 years ago

Have you rebooted?

Sent from my iPhone

On Feb 26, 2018, at 05:41, Sharvilak notifications@github.com wrote:

I am facing the same issue at the moment. Chrome is giving me Waiting for Available socket , although it works fine in Firefox. Uninstalled chrome, deleted all chrome associated data. Still no success!

Did you get to know anytime later what had happened ? @indrekpaas

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.