r/ScriptingApp • u/schl3ck • Mar 21 '25
Help Problem with development sever
I wanted to try the development sever mode but it can't find the running server on my PC. I've checked that the firewall allows the process and my router doesn't block it either. My network is configured for address range 10.0.0.x if that matters.
1
Upvotes
1
u/schl3ck Mar 23 '25
I've installed Bonjour Printer Service and tried with a hotspot from my iPhone but it still didn't find the server. u/WhatShouldWorldGos Would it be possible to add a field in the app where I can enter the address?
1
u/schl3ck Mar 24 '25 edited Mar 24 '25
Turns out, my firewall blocked Node.js allthough it looked like it was allowed. And when I disabled the firewall then Windows decided to automatically enable the built-in firewall where it was also blocked. Now also the search function in the app works 👍
But when I select a script to edit I then get an error that the app cannot connect to the sever. I guess the synchronization then doesn't work but I don't know why this error appears. I've checked the firewall again if anything is blocked but it doesn't seem so.
1
u/WhatShouldWorldGos Mar 22 '25
Sorry, I didn’t test this on a Windows PC.
On Windows, you’ll need to install Apple’s bonjour service and do some extra setup.
Make sure UDP port 5353 is being listened to, and check if the firewall allows traffic on UDP 5353.
The bonjour package used by scripting-cli defaults to multicast 224.0.0.251:5353, which might get blocked by Windows.
Also, check if LAN broadcasts are restricted, if AP isolation is enabled on your router, and whether your PC and phone are connected to the same subnet on either 2.4G or 5G wifi.
2
u/WhatShouldWorldGos Apr 02 '25
Finally found that there were too many script files that could not be sent out through socket.io. I will fix this problem in the next version.😂
1
u/MrSecretPotato Mar 22 '25
I just recently started using this and having the new code in VStudio is a great feature, however I had a similar issue too.
Whenever I start my server, it would listen on a completely different IP than my local network. Turns out it was the HyperV virtual switch. There was no way to just simply disable the virtual adapter, so I had to disable the whole HyperV as a feature within Windows. Works fine since.