You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Syncthing Tray command "Open" and Preferences window button "Open Syncthing Web Interface" defaults to 127.0.0.1:8384 irrespectively of actually entered value. As a result "Connection refused"/"Couldn't connect" message appears as the Web browser is directed to open the default 127.0.0.1:8384 address. The manual entry directly in address line works correctly
The text was updated successfully, but these errors were encountered:
Sorry for the delay. It seems indeed a bit odd. When de URI is input + checked and saved with the Test button in the Preferences window. The Icon -> Open menu item and Open Syncthing Web Interface use the old value and probably not the default 127.0.0.1:8384.
There is a workaround (yes it is very odd):
Click the icon -> Go to Preferences -> enter URI -> Test (click to check Syncthing connection OK), the button bullet must be green (then the URI is saved
Click the icon -> Quit Syncthing
Start Syncthing
Thanks for reporting, it is easy reproducable.
EDIT:
It is even more weird after further testing. Setting the URI, then Test OK with green bullet in the button. Then the preference window is closed. And reopened and the old URI is in the input box. That is what is happening...
xor-gate
changed the title
Syncthing tray/preferences not opening correct web interface
Syncthing URI address not correctly updated after test (implicit save), must restart Syncthing
May 29, 2023
Syncthing Tray command "Open" and Preferences window button "Open Syncthing Web Interface" defaults to 127.0.0.1:8384 irrespectively of actually entered value. As a result "Connection refused"/"Couldn't connect" message appears as the Web browser is directed to open the default 127.0.0.1:8384 address. The manual entry directly in address line works correctly
The text was updated successfully, but these errors were encountered: