Two different syncthing configs running. Help to fix

Hi All

I am new to syncthing and some how did something I am having trouble fixing.

So maybe a couple weeks ago I decided to start syncthing manually from the command line and apparently, that started a whole new syncthing instance with a different device ID. I did not know this was possible. Without thinking much, I configured everything to work with all the computers and this time got it all working smoothly.

Well what I didn’t know, or forgot about, was that every time I reboot the server, Syncthing has a Syncthing service that starts automatically with a different device ID and my original test folders when I was fooling around learning the software. This device ID and config is no longer needed.

I would like my new config to start with the service. How can I point the syncthing service to the new config?

The new config I can get to and start easily by manually starting syncthing. It starts under a different port number as well. But I need to keep the command box open for syncthing to run the new config.

Thank you all Justin

The server is running Windows 10. Syncthing Ver 1.27.9

This is probably caused by the service running as a different user compared to the user you were logged in via the command line. Syncthing’s configuration and database directories typically depend on the user.

When you start syncthing and open the web GUI, you can figure out the config & database location it is using under Help → About → Paths. You can start syncthing via your different methods and note the paths used in each case. You can then simply copy the files from one location to the other, overwriting the old data.

Note: You can also manually specify config & data locations with the command line switches --config and --data, but for simplicity, I would suggest to copy files such that everything works with the default locations. For more information on syncthing’s configuration, refer to the documentation.

Thank you! I will look into this more.

1 Like

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