Failed to connect id17 = Failed to start network server, port 54640, error:socket_port_privileged

Reproduction Steps

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.
unknown

Then you get this in the studio.
unknown

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

4 Likes

This issue has already been reported:

1 Like

In 2021 and closed i know.
I got it today.
Never had that problem before.

And yes I did check that post before posting this one.

I have also made sure that I don’t have that port active at all.

Summary
Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            pc:0              LISTENING
  TCP    0.0.0.0:445            pc:0              LISTENING
  TCP    0.0.0.0:1462           pc:0              LISTENING
  TCP    0.0.0.0:1487           pc:0              LISTENING
  TCP    0.0.0.0:2179           pc:0              LISTENING
  TCP    0.0.0.0:3389           pc:0              LISTENING
  TCP    0.0.0.0:5040           pc:0              LISTENING
  TCP    0.0.0.0:5357           pc:0              LISTENING
  TCP    0.0.0.0:5426           pc:0              LISTENING
  TCP    0.0.0.0:7680           pc:0              LISTENING
  TCP    0.0.0.0:49664          pc:0              LISTENING
  TCP    0.0.0.0:49665          pc:0              LISTENING
  TCP    0.0.0.0:49666          pc:0              LISTENING
  TCP    0.0.0.0:49667          pc:0              LISTENING
  TCP    0.0.0.0:49673          pc:0              LISTENING
  TCP    0.0.0.0:49718          pc:0              LISTENING
  TCP    0.0.0.0:54235          pc:0              LISTENING
  TCP    0.0.0.0:54236          pc:0              LISTENING
  TCP    0.0.0.0:55045          pc:0              LISTENING
  TCP    127.0.0.1:1337         pc:0              LISTENING
  TCP    127.0.0.1:5939         pc:0              LISTENING
  TCP    127.0.0.1:5939         kubernetes:49737       ESTABLISHED
  TCP    127.0.0.1:13339        pc:0              LISTENING
  TCP    127.0.0.1:13340        pc:0              LISTENING
  TCP    127.0.0.1:14622        pc:0              LISTENING
  TCP    127.0.0.1:14622        kubernetes:57981       ESTABLISHED
  TCP    127.0.0.1:14630        pc:0              LISTENING
  TCP    127.0.0.1:26822        pc:0              LISTENING
  TCP    127.0.0.1:28385        pc:0              LISTENING
  TCP    127.0.0.1:28390        pc:0              LISTENING
  TCP    127.0.0.1:32682        pc:0              LISTENING
  TCP    127.0.0.1:37014        pc:0              LISTENING
  TCP    127.0.0.1:37114        pc:0              LISTENING
  TCP    127.0.0.1:49350        pc:0              LISTENING
  TCP    127.0.0.1:49351        pc:0              LISTENING
  TCP    127.0.0.1:49680        pc:0              LISTENING
  TCP    127.0.0.1:49680        kubernetes:55001       ESTABLISHED
  TCP    127.0.0.1:49737        kubernetes:5939        ESTABLISHED
  TCP    127.0.0.1:49747        kubernetes:49748       ESTABLISHED
  TCP    127.0.0.1:49748        kubernetes:49747       ESTABLISHED
  TCP    127.0.0.1:49763        kubernetes:49764       ESTABLISHED
  TCP    127.0.0.1:49764        kubernetes:49763       ESTABLISHED
  TCP    127.0.0.1:53251        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53252        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53253        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53254        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53256        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53257        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53258        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53260        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53262        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53263        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53265        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53266        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53267        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53269        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53270        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53271        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53272        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53276        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53277        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53282        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53284        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53286        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53288        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53289        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53291        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53292        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53294        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53295        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53296        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53297        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53298        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53299        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53300        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53301        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53302        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53304        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53305        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53307        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53308        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53309        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53310        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53311        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53312        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53314        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53315        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53316        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:53317        kubernetes:49350       TIME_WAIT
  TCP    127.0.0.1:54982        kubernetes:65001       ESTABLISHED
  TCP    127.0.0.1:54983        pc:0              LISTENING
  TCP    127.0.0.1:55000        pc:0              LISTENING
  TCP    127.0.0.1:55001        kubernetes:49680       ESTABLISHED
  TCP    127.0.0.1:57981        kubernetes:14622       ESTABLISHED
  TCP    127.0.0.1:65001        pc:0              LISTENING
  TCP    127.0.0.1:65001        kubernetes:54982       ESTABLISHED
  TCP    172.22.112.1:139       pc:0              LISTENING
  TCP    172.22.192.1:139       pc:0              LISTENING
  TCP    172.24.96.1:139        pc:0              LISTENING
  TCP    172.29.176.1:139       pc:0              LISTENING
  TCP    192.168.1.3:139       pc:0              LISTENING
  TCP    192.168.1.3:51635     ec2-18-209-201-158:https  ESTABLISHED
  TCP    192.168.1.3:52086     20.199.120.85:https    ESTABLISHED
  TCP    192.168.1.3:52106     128.116.121.3:https    ESTABLISHED
  TCP    192.168.1.3:52294     ec2-107-21-61-159:https  ESTABLISHED
  TCP    192.168.1.3:52327     104.244.42.193:https   ESTABLISHED
3 Likes

Thanks for the report and sorry for the late response. Are you still experiencing this issue?

Hello.

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.

1 Like

Hello, the issue still occurs on my end:
image

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.

1 Like

I see. Thanks, I filed a ticket to our internal database and I’ll come back with updates when possible.

2 Likes

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:

Hi,

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)

2 Likes

Hey guys! Thanks for reporting this issue.
Happy to share that we recently patched this, so you should no longer run into this issue.

Please let me know if it ever returns

3 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.