Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port change is not reflected in usage of Syncthing (manual restart is needed) #198

Open
ineiti opened this issue Jul 31, 2023 · 5 comments
Labels
bug docs Documentation

Comments

@ineiti
Copy link

ineiti commented Jul 31, 2023

On my mac I have two syncthing instances, one for each user. So I changed the port of one of the instances in order for them to run in parallel. Now the following happens for the syncthing with the changed port:

  • it seems to me that the status icon follows the syncthing of the other user with the default port
  • when I click on the icon and choose Open, it opens the syncthing with the default port. Same thing if I click the icon, choose Preferences and then Open Syncthing in Browser
@xor-gate
Copy link
Member

you need to click on the icon -> Preferences -> enter the URI -> click test. Then close syncthing and restart it. Then the non default port should be used. Keep in mind you should also set the API key based on the instance.

@ineiti
Copy link
Author

ineiti commented Aug 14, 2023

OK, seems I didn't quit and start Syncthing again.

@ineiti ineiti closed this as completed Aug 14, 2023
@xor-gate xor-gate reopened this Aug 19, 2023
@xor-gate
Copy link
Member

xor-gate commented Aug 19, 2023

Reopened because we should at least document this behaviour. And probably we should fix it so it is live changed and it doesn't need restarted. For my own administration: this behaviour is probably due to the default functionality and syncthing daemon background process are not synced when updating. Then the background process should be stopped/killed and then started again after the change and given the new setting.

@xor-gate xor-gate added bug docs Documentation labels Aug 19, 2023
@ineiti
Copy link
Author

ineiti commented Aug 21, 2023

There might be other configuration changes that need to be reloaded, no? So perhaps for every configuration change, do this reloading of the daemon.

@xor-gate
Copy link
Member

xor-gate commented Aug 21, 2023

Exactly, like the environment variables and the hidden commandline arguments.

@xor-gate xor-gate changed the title Port change is not reflected in usage of syncthing Port change is not reflected in usage of Syncthing (manual restart is needed) Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug docs Documentation
Projects
None yet
Development

No branches or pull requests

2 participants