Oops! Google Chrome could not connect to localhost:55067 about appjs-deskshell HOT 7 CLOSED

Since nodejs got an exception it closed down and did not start the webserver and that is the reason for the localhost error.

For now kill all versions of nodejs and chrome that are running. I suspect you have both a windows installer deskshell and a source code deskshell and both are trying to use port 9223. To fix this edit bin/win/deskshell-env.js change the port from 9223 to 9224. That way the two versions of deskshell can run independently.

If this does not fix the problem comment again and we can try a different solution.

from appjs-deskshell.

Clarification: change port in deskshell-env.js for the source code version of deskshell.

from appjs-deskshell.

As a side note, i am using my freeport function in PHP to generate a new rdebug port. That way I never got an issue so far. Consider it becoming a setting to have a fixed or dynamic port? It'd be useful for apps that want to determine multiple instances, or something like that... just a random idea o.o
Am 03.10.2013 um 19:18 schrieb sihorton [email protected]:

Since nodejs got an exception it closed down and did not start the webserver and that is the reason for the localhost error.

For now kill all versions of nodejs and chrome that are running. I suspect you have both a windows installer deskshell and a source code deskshell and both are trying to use port 9223. To fix this edit bin/win/deskshell-env.js change the port from 9223 to 9224. That way the two versions of deskshell can run independently.

If this does not fix the problem comment again and we can try a different solution.

—
Reply to this email directly or view it on GitHub.

from appjs-deskshell.

I did that at first. The problem is when you launch multiple apps at the same time. The second app that runs ignores the debug port you gave to it and instead reuses the debug port you gave to the first app! This caused problems for me at first but now that is fixed by having one set debug port per chromium binary that is launched.

My guess in this case is that there is the windows installer deskshell installed with its chromium binary and then the checked out source code in a second folder with its chromium binary and both are trying to use same port. I have this setup on my windows dev machine. Solution is to change port for the source code version then both can run side by side. This solved problem for me -- to begin with I often got the same error reported here, now it launches every time.

Still we should copy your connection algorithm to windows port and then add better error handling - not so nice at the moment that we just crash.

from appjs-deskshell.

Still having some difficulty. Closed all versions of chrome and node.js.

When I restarted deskshell I looked at Task Manager and found 3x instances of Chrome.exe running and I didn't have any instances of chrome open.

So Deskshell starts but when I click on the demo button I get the error again. This might be due to the way I've pulled from the upstream repo ... let me start again

from appjs-deskshell.

I created a totally clean checkout of the source code and then I got the exact same issue. The problem was caused by a missing file if running from a github checkout. I added a simple test for that and now I no longer get the issue.

Please pull the latest changes from github to fix this issue.

from appjs-deskshell.

Thanks Simon. I'll test tonight Australian time.
On Oct 9, 2013 8:43 AM, "sihorton" [email protected] wrote:

I created a totally clean checkout of the source code and then I got the
exact same issue. The problem was caused by a missing file if running from
a github checkout. I added a simple test for that and now I no longer get
the issue.

Please pull the latest changes from github to fix this issue.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-25934035
.

from appjs-deskshell.