If you forget to incude the id of the relay server, these are the errors you get (or at least I got) on the client side: Disconnecting from relay relay://:22067 due to error: EOF c.S.listenerSupervisor: Failed service 'relay://:22067' (2.985913 failures of 2. The key is output by the server on startup, which you can catch if you run it from the command line (if you have shell).
#Syncthing ubuntu server install#
For a systemd conf, see Ĭlients will not connect to the server unless they know the server's key, so you have to configure them with an id parameter and not just protocol, server and port: relay://:22067?id= Step 2 Install Syncthing on Both Servers By default, Syncthing is not available in the Ubuntu 18. One way of doing this is to supply the -keys parameter to ExecStart in systemd. You have to make sure the keys for the server are stored where the server can find them.
It can be good to know that the server is called "strelaysrv" on Ubuntu, which the Ubuntu man page does not mention, but instead uses the "relaysrv" name. It may also automagically work if you do everything right from the beginning. This will likely mean reinstalling the OS. I wish to upgrade the server to be able to do some more demanding tasks as well. I created a dedicated user with a shell so that I could easier see why things did not work. I run syncthing on most devices in our home, using it to sync files back to a home NAS PC running ubuntu.
0 kommentar(er)
