When i try to open any place with local server, I get the error below.
Sorry, this place could not be loaded. Details: “Failed to start network server, port:53640, error:SOCKET_PORT_PRIVILEGED”
If you continue to encounter this error, please report it on the Developer Forum.
Incident ID: 2837375727260943326
Place ID: 95206881
I have uninstalled roblox, restarted the machine, re-installed roblox.
Tried several ways of “editing” a roblox place.
But clicking “start local server” makes this error every time.
Expected Behavior
For the studio to open a local server.
Actual Behavior
First, you get this window.
Then you get this in the studio.
Workaround
Went into Windows restore, canceled that, and restarted the machine.
Restoring the machine to an earlier stage could also fix the issue.
Issue Area: Studio Issue Type: Connectivity Impact: High Frequency: Rarely Date First Experienced: 2022-07-17 03:07:00 (+02:00) Date Last Experienced: 2022-07-17 04:07:00 (+02:00) A private message is associated with this bug report
I ended up having to revert my whole PC back 1 day, to an earlier Roblox installation.
I then uninstalled Roblox, and removed Roblox from all regedit strings.
Then restarted the PC.
Then re-installed roblox, and it works.
It only happens on my laptop, never happened on my desktop before. I’m not sure what information I should put here, but I have gotten this error about 5 days ago and it’s still happening on my end, and only with my laptop.
Any solution to this problem?
It happen again today, when I tried starting studio in test mode with 2 players.
I also tried starting it with 0 players, and still got the same error.
Sorry, this place could not be loaded. Details: “Failed to start network server, port:53640, error:SOCKET_PORT_PRIVILEGED”
If you continue to encounter this error, please report it on the Developer Forum.
Incident ID: 1049753130822029292
Place ID: 801672905
Place name:
I’ve been experiencing this issue here and there and I finally got tired of it, enough to look into it.
Roblox statically uses port 53640 to start a server in a local multiplayer test, which is fine except it doesn’t check if it’s already reserved.
This usually isn’t a problem unless you have services/applications that reserve these ports such as:
WSL
Hyper-V
Windows Sandbox
Docker for Windows / Docker Desktop
If you are a user affected by this you can do the following to work around this issue:
Open a command prompt window as an administrator and run the following commands These may mess with utilities I listed above (and maybe more) so run with caution
net stop winnat
net start winnat
To verify that the port is now open run the following command
netsh int ipv4 show excludedportrange protocol=udp
The other option is to just reboot your PC and hope that it doesn’t get the range reallocated.
Demo showing the issue being resolved:
(EDIT: I accidentally highlighted the wrong range, ignore that and look for the range yourself)