What is the matter with syncthing on my vps?

I have installed syncthing both on my local pc and vps,there is an account named debian both on my local pc and my vps.

In my local pc:

 sudo systemctl status syncthing@debian
● syncthing@debian.service - Syncthing - Open Source Continuous File Synchronization for debian
   Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-06-02 16:51:26 CST; 37min ago
     Docs: man:syncthing(1)
 Main PID: 6088 (syncthing)
    Tasks: 20 (limit: 4915)
   CGroup: /system.slice/system-syncthing.slice/syncthing@debian.service
           ├─6088 /usr/bin/syncthing -no-browser -no-restart -logflags=0
           └─6097 /usr/bin/syncthing -no-browser -no-restart -logflags=0

Check port 8384.

sudo netstat -tunlp|grep  8384
tcp        0      0 127.0.0.1:8384          0.0.0.0:*               LISTEN      6097/syncthing      

In my vps:

systemctl status syncthing@debian.service
● syncthing@debian.service - Syncthing - Open Source Continuous File Synchronization for vultr
   Loaded: loaded (/lib/systemd/system/syncthing@.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-06-01 10:11:27 UTC; 23h ago
     Docs: man:syncthing(1)
 Main PID: 5189 (syncthing)
   CGroup: /system.slice/system-syncthing.slice/syncthing@debian.service
           ├─5189 /usr/bin/syncthing -no-browser -no-restart -logflags=0
           └─5194 /usr/bin/syncthing -no-browser -no-restart -logflags=0

Check port 8384 on my vps.

sudo netstat -tunlp|grep  8384
#nothing as output

The syncthing is running on my vps–systemctl status syncthing@debian.service shows that,why it can’t listen on port 8384 in my vps?The port 8384 is listened on my local pc.

Grep for syncthing instead. Maybe it’s configured to use another port. (It does that automatically on first startup if 8384 is already taken by someone else, including another instance of Syncthing.)

1 Like
netstat -tunlp|grep syncthing
tcp        0      0 127.0.0.1:34375         0.0.0.0:*               LISTEN      614/syncthing       
tcp6       0      0 :::38949                :::*                    LISTEN      614/syncthing       
udp        0      0 0.0.0.0:21027           0.0.0.0:*                           614/syncthing       
udp        0      0 0.0.0.0:42119           0.0.0.0:*                           614/syncthing       
udp6       0      0 :::21027                :::*                                614/syncthing       
udp6       0      0 :::51838                :::*                                614/syncthing

Seems like port 8384 was taken on first startup, so now it’s using a different port. It prints the UI address in the logs, so you should just check/follow that.

1 Like

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