New Linux PC: Syncthing not initating at browser invocation

Support
1

Hello,

I have been using Syncthing for 3 or 4 years now and had to install a new mobo and upgraded

my Linux Ubuntu OS at the same time.

All of this has disrupted the Syncthing app and it refuses to link up when initated in the Chrome browser.

Here is what I have done:

I determined in terminal mode the address assignment:

ed@ed-B760M-DS3H-DDR4:~$ ifconfig enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.218 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::e0a4:8809:81e:1955 prefixlen 64 scopeid 0x20 ether 74:56:3c:bf:f3:28 txqueuelen 1000 (Ethernet) RX packets 33789 bytes 17172023 (17.1 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 14579 bytes 4617299 (4.6 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 1545 bytes 150318 (150.3 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1545 bytes 150318 (150.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

_______________________________________

I then changed the addressing in the config file [syncthing@.service] under etc/systemd/system to the addresss returned from ifconfig:

[Unit] Description=Syncthing - Open Source Continuous File Synchronization for %I Documentation=man:syncthing(1) After=network.target

[Service] User=%i ExecStart=/usr/bin/syncthing -no-browser -gui-address=“192.168.0.218” -no-restart -logflags=0 Restart=on-failure SuccessExitStatus=3 4 RestartForceExitStatus=3 4

[Install] WantedBy=multi-user.target

______________________________________________

I reloaded the reference file and reinitiated syncthing:

ed@ed-B760M-DS3H-DDR4:~$ systemctl daemon-reload ed@ed-B760M-DS3H-DDR4:~$ sudo systemctl start syncthing@ed && sudo systemctl enable syncthing@ed ed@ed-B760M-DS3H-DDR4:~$

________________________________________

No errors or any hangups through the whole process. But when I type in 192.168.0.218 (:8384)

I receive the browser error:

This site can’t be reached

192.168.0.218 refused to connect.

Try:

ERR_CONNECTION_REFUSED

Have I missed a step somewhere? In the past this process was always successful.

???

Thanks for any input,

Mister Ed

2

Editing the systemd config is an unusual way of setting the GUI listen address. I wouldn’t do that, but edit the config.xml instead.

Since you are using systemd to start it, your best bet would to investigate what it has to say about the started process and any log entries in the journal.

1 Like
3

The way I explained was how I understood to do it after talking with Syncthing afficiandos and it has worked well until I made this new desktop.

I can look at the config,xml instead and if I understand what is necessary to modify I can try that.

What is the command to see the systemd journal entries. I am not proficient with the internals of the Linux operating system and have a very limited understanding about the “guts” of Linux but can usually get when in terminal mode.

Syncthing has always been rock solid after setting it up initially so it has just ran in the background without issues. I did get it working on another new PC with a Windows 11 based system. I use Syncthing between the two.

4

I wanted to add this bit of information:

ed@ed-B760M-DS3H-DDR4:~$ systemctl status syncthing@youruser.service
â—‹ syncthing@youruser.service - Syncthing - Open Source Continuous File Synchronization for youruser
     Loaded: loaded (/etc/systemd/system/syncthing@.service; disabled; preset: enabled)
     Active: inactive (dead)
       Docs: man:syncthing(1)

I believe this suggest Syncthing is loaded but is inactive (dead).

Also I realized I initially failed to add the :8384 at the end of the address in the service@.service file. THat has been corrected.

6 
ed@ed-B760M-DS3H-DDR4:~$ journalctl -u syncthing@youruser.service
Feb 14 21:15:05 ed-B760M-DS3H-DDR4 systemd[1]: Started syncthing@youruser.service - Syncthing - Open Source Continuous File Synchronization for youruser.
Feb 14 21:15:05 ed-B760M-DS3H-DDR4 systemd[1]: syncthing@youruser.service: Main process exited, code=exited, status=217/USER
Feb 14 21:15:05 ed-B760M-DS3H-DDR4 systemd[1]: syncthing@youruser.service: Failed with result 'exit-code'.
Feb 14 21:15:06 ed-B760M-DS3H-DDR4 systemd[1]: syncthing@youruser.service: Scheduled restart job, restart counter is at 1.
Feb 14 21:15:06 ed-B760M-DS3H-DDR4 systemd[1]: Started syncthing@youruser.service - Syncthing - Open Source Continuous File Synchronization for youruser.
Feb 14 21:15:06 ed-B760M-DS3H-DDR4 (yncthing)[18119]: syncthing@youruser.service: Failed to determine user credentials: No such process
7

Moderators:

This thread can be closed now. OP deleted and reloaded Syncthing to get app working again.

8

Support topics are closed automatically after 30 days if there is no activity.

9

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