Syncthing will restart, and since we have changed the Web GUI port to 8385, it will immediately become unavailable – Jay will have to browse to, from now on. Scroll down, and press the Save button.The field Listen Addresses will have default as its content – change that to 22001, the value defined for Jay in the table above. Similarly, click on the Options accordion tab to open it. Click on the GUI accordion tab to open it.In the top right corner, open the Actions dropdown menu and click on Advanced, to access the Advanced Configuration screen. We’ll now change the default settings to Jay’s, taken from the table above.Sadly, by default no login will be required. Open it in a browser, and the Web GUI should show up. Additional instances started by other users will also be considered a »device«, although all of them run on the same physical machine. Unfortunately, every private instance of Syncthing like the one we just have started is called a »device«, in Syncthing’s terminology. After a few seconds, Jay’s instance of Syncthing will be listening to the world on the default port, and offer a Web GUI under a second port, also the default. (How to make Syncthing autostart is beyond the scope of this text). On most Linux distributions, the installation will have added a menu entry for that. It doesn’t matter which user you pick first from the table above – in our example, it’ll be Jay. Log in, as a user (or ask a user to do so).Now, reboot the device, to make sure no personal instance of Syncthing is running yet. To keep things simple, we suggest that you use these parameters for all machines where Jay, Robin, and others have accounts. It’s a good idea to maintain this list in a document. Let’s say you have scribbled down this table: User That’s why you shouldn’t assign them to any user. The default ports are 830, respectively – every freshly installed Syncthing instance will grab those defaults, upon start. Step 1: Set up a list of users, and their private Syncthing portsĮvery instance of Sycthing, Jay’s as well as Robin’s, needs their own private listener port, and their own private Web GUI port. Pick the appropriate installation option on Syncthing’s website, and follow the instructions. Step 0: Install Syncthing, if you haven’t so far You need to modify each user’s configuration of Syncthing, immediately after having installed Syncthing for that user, when calling the Web GUI for the first time. This can’t possibly work, so Robin’s instance won’t start.Įven worse: If you haven’t enabled user names and passwords for the Jay’s Web GUI, Robin will erroneously access Jay’s file synchronization settings – and be granted full access. Robin’s instance of Syncthing will try to grab the same default ports, like Jay’s. When you do the same for Robin, their instance of Syncthing will try to start, but doesn’t know anything about Jay already being logged in. Unfortunately, in Syncthing terminology, Jay’s Syncthing instance is called a »device«. That instance will listen to the world on a specific port, and its Web GUI for Jay will be available on a second port. When you install Syncthing, and have it auto-start upon Jay’s login, Jay gets their own personal instance of it. Consider Jay and Robin, two users who may be logged in to the same PC, each wanting privacy and file synchronization, without interference from the other one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |