Windows: "dial tcp 127.0.0.1:2828: connectex: No connection could be made"

[tombh]

I don't how popular running Browsh on Windows is? But we might as well have it working if it's possible. At the moment Firefox crashes during boot, I don't know why.

Of course Windows users, as I suspect most users, will use Browsh over Mosh/SSH, where Browsh runs on a Linux VM.

[tombh]

As a user on Twitter reports, the issue seems to be;

dial tcp 127.0.0.1:2828: connectex: No connection could be made because the target machine actively refused it.

Which is Firefox's Marionette RPC. So this could be a port permissions error on Windows?

[dertuxmalwieder]

For me, browsh starts fine but crashes instantly after Firefox has been started:

panic: runtime error: invalid memory address or nil pointer dereference◙[signal 0xc0000005 code=0x0 addr=0x8 pc=0x4b4cdd]◙◙goroutine 19 [running]:◙os.(*Process).signal(0x0, 0x7cd560, 0x91c3c8, 0xc0422b4070, 0x0)◙    .go:58 +0x2d◙(0x0, , :◙
C:\>

Sometimes it manages to display the "waiting for Firefox to connect" screen, at least.

Windows 10, Firefox 64 Bit.

[tombh]

Thanks for extra info

[janmechtel]

Same herein Windows 10, Firefox 64 Bit.

1. I kill all firefox processes
2. Run browsh_1.2.3_windows_amd64

dial tcp 127.0.0.1:2828: connectex: No connection could be made because the target machine actively refused it.

3. Run browsh_1.2.3_windows_amd64 again:

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x4b4cdd]

goroutine 19 [running]:
os.(*Process).signal(0x0, 0x7d2540, 0x9233c8, 0xc042354070, 0x0)
	/home/travis/.gimme/versions/go1.10.3.linux.amd64/src/os/exec_windows.go:58 +

[jamespeace]

I have the same problem like @janmechtel on Windows7

[parasdsingh]

Same here! And as a windows user I'd prefer running it natively than wrapped in mosh tbh

[Structed]

Same here. I was using the -firefox option to specify the path for the x64 firefox executable.

When starting browsh via powershell, it opens a new Firefox window, spits out above panic message and the powershell process hangs. See screenshot

[tombh]

@janmechtel Thanks for clarifying. (1) is really the main problem, (2) is just the fact that Browsh was unable to close Firefox in the first attempt.

I'm afraid this isn't a top priority for me to fix. Mainly as Browsh's main target is to be run on a remote server (in order to get the bandwidth savings for people on slow/expensive bandwidth locally). Also I haven't used windows in nearly 20 years now, so I'm not at all familiar with how to start debugging this.

But I'll certainly leave this issue open. I'd love to see this fixed. Maybe there's someone else that has more Windows experience that can help?