search

brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

Firewall Warning after the first start #12995

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by zaggino Tuesday Dec 16, 2014 at 03:37 GMT Originally opened as https://github.com/adobe/brackets/issues/10182

After the installation of Brackets.Release.1.1.msi, I got the firewall popup on my machine (never seen it before with previous versions). Not a big issue for me since I just allowed access for all networks, but might be for some users who have different firewall solutions installed which may block the node.exe without any popup. image

core-ai-bot commented 3 years ago

Comment by JeffryBooher Monday Jan 05, 2015 at 19:53 GMT

Low priority. Not sure there is anything we can do about it.

core-ai-bot commented 3 years ago

Comment by pthiess Monday Jan 05, 2015 at 19:58 GMT

I think we should investigate and understand why this warning is coming up -- it seems there were no changes on our end, so this may come up due to a Windows security update a change of policy etc.

core-ai-bot commented 3 years ago

Comment by MarcelGerber Sunday Jan 25, 2015 at 12:56 GMT

I also got this on a non-dev computer after installing Brackets 1.1 using the installer, so it's definitely not only a problem with dev builds.

core-ai-bot commented 3 years ago

Comment by abose Wednesday Jan 28, 2015 at 10:47 GMT

I see that as part of the new LiveDev implementation, a web server port has been opened in v1.1 see pull req: https://github.com/adobe/brackets/pull/10010/files , file:src/LiveDevelopment/MultiBrowserImpl/transports/node/node_modules/ws/lib/WebSocketServer.js

This would naturally bring up the UAC dialog if windows firewall is on; to request permission from the user to open the port . Choose the appropriate firewall permission from the dialog based on your security requirement as we need the port to be open for live preview to work.

core-ai-bot commented 3 years ago

Comment by davegear Thursday May 17, 2018 at 16:47 GMT

First web search result brought me here... not sure why this issue is still open. I got this after opening the latest Brackets for the first time; I already have Node installed but I'm not sure what Brackets is doing to prompt the Firewall alert.

Frankly I'd only like my local laptop server(s) to allow access from any requests on the laptop, not from anything else on the network. This means I don't even want the servers exposed to others on the network, private public or otherwise.

Maybe I'm missing something... can someone explain this better?

image

core-ai-bot commented 3 years ago

Comment by abose Saturday Jun 02, 2018 at 05:02 GMT

@vickramdhawal@swmitra Shouldn't bind the server to localhost resolve the issue? I don't think brackets support multi-device previews out of the machine to open an external port.

qwythebroken commented 2 years ago

Just a bump. I share Core-ai-bot's concern, and thought I'd confirm the identical prompt on the first run, under the following conditions;

Edition Windows 10 Home Version 21H2 Installed on ‎9/‎15/‎20 OS build 19044.2130 Experience Windows Feature Experience Pack 120.2212.4180.0

Brackets: Release 2.1 build 2.1.2-17937 (master 167640b53) build timestamp: Wed Jul 06 2022 18:43:26 GMT+0530

The first was link on a google search for, " allow node.js access networks brackets.io", goes to an unrelated Node.js thread on StackOverflow. The second brought me to the original, archived version, of this thread. I barely know enough to even be here, but from what I've read, I'm under the impression this can't be resolved without sacrificing live preview. The bump is just to give someone, smarter than myself, an opportunity to prove me wrong. They don't even have to be gentle about it, if they don't want to be. They won't be my first. I've been making mistakes for a while, now.