Hi all,
i have a connection Problem. Socket error. See the picture.
Any ideas?
Thank you all!
Is it possible that another process is using TCP/8384?
How can i see this? In the firewall rules?
What operating system?
On Windows, you can use Resource Monitor or netstat -a -n. Using Linux, I would use netstat -lntup. On MacOS it’s netstat -a | grep -i "listen".
Please keep in mind I wrote this on my iPad with no immediate access to any of the aforementioned operating systems — I apologize if I got any command line switches wrong.
1 Like
Win 10
Ports.txt (19.4 KB)
So, no.
If Google Translate serves, something is preventing access by the process to the socket (the port on that IP). I have not seen that before with regard to Syncthing. If I am remembering correctly, the built-in firewall on Win10 does not prohibit software from accessing ports, but rather permits the access to the process and prohibits the access on the network to the process.
My suggestion is twofold:
- Try configuring a different port for the GUI (Syncthing Configuration — Syncthing documentation, search for 8384 and change it in the GUI section of config.xml) and restarting Syncthing. You may want to choose a high port (10000+) for this test.
- Figure out why you have initial scan errors.
According to the list of network ports in use, several are in the 7000 range plus 8307, which is pretty close to 8384.
There’s a good chance that some software has reserved a block of ports that includes 8384.
Any other server software, Docker, etc.?
1 Like
No noting. I have change the port, to over 10000. Dont work. Same problem. I have uninstall the software and install a new version. Dont work.
And the funny thing is, I haven’t used the software for a month. And before that it worked without any problems.
New antivirus?
No. Only use windows defender.
Given the timeline, it’s either due to a monthly Windows update, or some other software. Chances are other network software that needs to bind to a network port will also fail similarly, so it’s not limited to Syncthing (unless Syncthing is now running under a user with no privileges).
Open a command-prompt, windows terminal, PowerShell, or other suitable command-line interface and list the reserved ports with the following command:
netsh interface ipv4 show excludedportrange protocol=tcp
1 Like
Startport Endport
80 80
2740 2839
2869 2869
2870 2969
2970 3069
3070 3169
3218 3317
3318 3417
3418 3517
3518 3617
3618 3717
3828 3927
3928 4027
4028 4127
4128 4227
4228 4327
4328 4427
4428 4527
4528 4627
4628 4727
5041 5140
5141 5240
5241 5340
5357 5357
5358 5457
5458 5557
5558 5657
5658 5757
5758 5857
5940 6039
6399 6498
6499 6598
6599 6698
6699 6798
6799 6898
6899 6998
6999 7098
7099 7198
7199 7298
7700 7799
7800 7899
7900 7999
8000 8099
8100 8199
8200 8299
8300 8399
8400 8499
8501 8501
8502 8601
9114 9213
9214 9313
9314 9413
9414 9513
9514 9613
9614 9713
9714 9813
9814 9913
9914 10013
10243 10243
10429 10528
10529 10628
10629 10728
10729 10828
10829 10928
10929 11028
50000 50059 *
Maybe another instance of Syncthing is already running and using the same port? Can you check how many Syncthing processes there are in the Task Manager?
Yeah, that’s what I suspected. Something – other than Syncthing – has reserved a chunk of ports from 8300 thru 8399.
If my count is correct, ports 6399 to 7298 and 7700 to 8499 are all reserved.
The one denoted by the asterisk is an admin-level reservation.
1 Like
And witch port, can i use now?
.
No witchcraft required – even though sometimes it seems like it does… 
So, there are 2^16 ports (0 to 65535) available.
0 to 1024 are usually reserved for system use and common ports for FTP/21, SMTP/25, SSH/22, HTTP/80, HTTPS/433, and so on, so although your port list doesn’t show any reservations except for port 80, best to steer clear of the entire range. Otherwise you can pick any unused (and unreserved) port.
Before picking another port, be sure to read Syncthing’s The GUI Listen Address page for important details.
Ideally, you should track down what reserved port 8384 since you last successfully used Syncthing. If 8384 had originally been in use, Syncthing would have automatically picked another unused port.
If you’re not aware of any new software, it wouldn’t be a bad idea to do a scan with another malware scanner besides Windows Defender to rule out missed issues.
1 Like
Thank you. I change the port to 10080. It doesnt work. But when i click, start syncting, i get a message, that it run. But how can it run and the config page dont work?
What’s the output from the following command?
(Note that you might need to launch a command prompt / windows terminal with elevated privileges.)
netstat -abn -p tcp
The command above lists all TCP ports that are currently being listened by a running process.
You’ll have to post a screenshot because I’m unsure of what you mean by that.
1 Like
Programms.txt (7.7 KB)
It runs. But i cant open the config page. And the port is changed. Sorry for my stupid questions guys, but I have no idea about network configurations.
Some lines extracted from your list of in-use network ports:
TCP 0.0.0.0:22000 0.0.0.0:0 ABHĂ–REN
[syncthing.exe]
--
TCP 127.0.0.1:10080 0.0.0.0:0 ABHĂ–REN
[syncthing.exe]
--
TCP 192.168.1.250:13725 89.58.60.208:22067 HERGESTELLT
[syncthing.exe]
Other than the web GUI listening on port 10080 instead of the default 8384, it looks like a typical Syncthing setup:
- Syncthing is listening on the default port 22000 for sync connections.
- Syncthing’s web GUI is on port 10080 matching your custom config.xml.
- There’s a live Syncthing connection on port 13725 to a peer that appears to be a VPS (virtual private server).
Your screenshot of the “Syncthing is already running.” warning dialog box is most likely because you tried to launch Syncthing more than once. Since Syncthing doesn’t have a native Windows UI widget, I’m guessing you’re using some kind of wrapper for launching and possibly for monitoring.
Point your web browser of choice at http://127.0.0.1:10080/ and you should be able to access Syncthing’s web GUI.
So, this is really more about Windows management rather than a network configuration issue. You’ve clearly got something on your Windows 10 system reserving a large number of network ports including port 8384. You’ve also got reading to do of Syncthing’s documentation because your Windows system configuration isn’t normal, so Syncthing’s safe defaults don’t work out-of-the-box.
2 Likes