Starting and connection problems with Jamovi when using firewall

[Biochemist]

Hi,

I have problems with Jamovi when using my firewall software under Windows. This firewall software normally asks for explicit internet access for all programs that need or want internet access. I can then allow or disallow it permanently or temporarily.

I permanently allowed:
C:\program files\jamovi 2.5.4.0\bin\jamovi.exe
C:\Program Files\jamovi 2.5.4.0\bin\jamovi-engine.exe

But whenever the firewall is active, Jamovi doesn't start. It just hangs at "starting jamovi" forever.

The only solution is to completely disable my firewall software when I want to use Jamovi. Then, Jamovi starts.

After starting Jamovi and re-enabling the firewall, I also get an error message when I try to access the online library: "Failed to execute 'send' on 'WebSocket': Still in CONNECTING state."

Are there any other programs/executable files that need internet access for Jamovi to work (so that I can manually add these to the firewall software in case they were not detected by it)?

[Biochemist]

I now added these files to the firewall for full internect access:
C:\Program Files\jamovi 2.5.4.0\Frameworks\python\python.exe
C:\Program Files\jamovi 2.5.4.0\Frameworks\python\pythonw.exe

Unfortunately, it still doesn't start with the firewall being active.

[jonathon]

hey,

when jamovi starts up, it launches an embedded web server, and then launches what is effectively a web browser to connect to that. if you start jamovi at the terminal, you'll see something like:

jamovi.server.server - listening across origin(s): 127.0.0.1:57300 127.0.0.1:57301 127.0.0.1:57302
jamovi.server.server - jamovi accessible from: 127.0.0.1:57300/?access_key=XXXXXX

those are the ports it is listening on. you can actually just take the `127.0.0.1:57300/?access_key=XXXXXX` and paste that into a web browser, and access jamovi like that. but that's key, the firewall can't block access to the jamovi server.

cheers

jonathon

[Biochemist]

Thanks for the info.

So far, I haven't been able to figure out why Jamovi still doesn't start when the firewall grants all the previously mentioned executable files full access (nothing is restricted).

I started Jamovi in debug mode and when the firewall is enabled (while all Jamovil files should actually not be restricted at all), the starting hangs at get_event_loop(). I attached a screenshot of this stage.

As soon as I disable the firewall completely, the starting completes and I additionally get to see the code that you listed below. From there, I copied the part 127.0.0.1:57300/?access_key=XXXXXX with XXXXXX being the actualy key on my computer and pasted it into the URL field of my web browser. However, this did not start Jamovi, independently of whether or not the firewall was active.

[jonathon]

hi,

yes it looks as though the firewall is preventing jamovi from opening those ports.

it might be worth contacting the firewall vendor, as if it's going to block the ports, jamovi isn't going to run.

normally firewalls simply block/filter incoming network traffic, and leave access to the 'loopback'/'localhost' addresses alone. technically traffic to the loopback/localhost never touches the network, so this is unusual behaviour for a firewall.

here's info on the loopback if you're interested:

https://www.lifewire.com/network-comput ... ess-818385

jonathon

[Biochemist]

Thanks again for the reply.

I have been able to solve the problem now. In the software firewall I am using I can completely allow or disallow all connections for executable files.

As mentioned in my previous posts, I allowed connections for the following files:
C:\program files\jamovi 2.5.4.0\bin\jamovi.exe
C:\Program Files\jamovi 2.5.4.0\bin\jamovi-engine.exe
C:\Program Files\jamovi 2.5.4.0\Frameworks\python\python.exe
C:\Program Files\jamovi 2.5.4.0\Frameworks\python\pythonw.exe

For some reason, however, "python.exe" was now set to "disallow" again. I don't know how this happened. After allowing connections for the above four files, Jamovi starts again correctly.

[jonathon]

awesome!

yes, python.exe is probably the most important one.

cheers

jonathon