felixfoertsch/syncthing
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

Local sessions

Browse Source
This commit is contained in:
Jakob Borg
2015-06-21 23:34:48 +02:00
parent 70734b42a1
commit c07414cda5
1 changed files with 19 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
users/faq.rst
+19 -23
View File
@@ -217,32 +217,28 @@ The CSRF tokens are stored using cookies. Therefore, if you get the message
``Syncthing seems to be experiencing a problem processing your request``, you ``Syncthing seems to be experiencing a problem processing your request``, you
should verify the cookie settings of your browser. should verify the cookie settings of your browser.
Why can I not open two Syncthing sessions in the same browser? Why can I not open two Syncthing sessions on localhost in the same browser?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Syncthing GUI uses cookies to maintain a session. You can't have more than
one session open against the same website in the same browser, much like you
can't log in as two different users on this forum at the same time from the
same browser, so that may cause this error message. This means you should not
browse a local Syncthing instance (typically localhost:8384) and a remote
Syncthing instance (e.g. localhost:9090 as suggested previously) at the same
time. Often, this results in partial functionality (e.g. ignore patterns cannot
be editted) or in an error message such as ``Syncthing seems to be experiencing
a problem processing your request`` when updating a particular setting.
In 99% of the cases of this issue are: The Syncthing GUI uses browser cookies to maintain a session. Browser cookies
are tied to the website domain. When navigating to two different websites on
the same domain, such as is the case for two Syncthing instances both
listening on ``127.0.0.1``, the cookies will get mixed up.
1. Using some sort of proxy/SSH tunneling which causes the cookies to be issued This means you should for example not browse a local Syncthing instance
under an incorrect domain causing the browser to refuse them. Close your (typically localhost:8384) and a remote Syncthing instance (e.g.
browser and only keep a single Syncthing Web GUI open at each time. localhost:9090 via an SSH forward) at the same time. Doing so results in
2. Having some privacy add-on enabled in the browser causing cookies to be partial functionality or in an error message such as *Syncthing seems to be
refused. experiencing a problem processing your request* when saving settings.
3. Browser failing to provide the initially provided Basic Auth header to
re-authenticate given syncthing was restarted and the session cookie is no
longer valid. Refreshing the page usually fixes this.
4. Having multiple sessions for the same site.
To resolve this, please use a seperate browser. For example use Firefox for one There are a few workarounds:
session and Konqueror/Chromium/.. for another.
- Use two separate browsers.
- Use the same browser, but one window in "incognito" or private mode.
- Use "reload" on the page prior to making changes, to ensure that the browser
has cookies from that instance specifically.
Why do I see Syncthing twice in task manager? Why do I see Syncthing twice in task manager?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~