Error autheticating with Insyc-Headless



I’m having issues authenticating with the headless Linux client.
I’m able to add_account successfully, however after doing so no syncing occurs and ‘manage_selective_sync’ throws a error saying ‘authError’.

Starting with the ‘–no-daemon’ flag returns the following error message.

INFO     2017-02-09 10:51:03,059 [__init__:info:1610] insync version:
INFO     2017-02-09 10:51:03,060 [__init__:info:1610] client created <ideskmain.client.Client object at 0x22ebb90>
INFO     2017-02-09 10:51:03,061 [__init__:info:1610] unix socket server thread start
INFO     2017-02-09 10:51:03,061 [__init__:info:1610] starting client
INFO     2017-02-09 10:51:03,065 [__init__:info:1610] LinuxFSWatcher._start
INFO     2017-02-09 10:51:03,066 [__init__:info:1610] Inotify loop enter
INFO     2017-02-09 10:51:03,068 [__init__:info:1610] Syncing GDUser(id=u'104202020526293411761', email=u'', name=u'FuBar').
INFO     2017-02-09 10:51:03,090 [__init__:info:1610] watch origin: /mass
ERROR    2017-02-09 10:51:03,093 [__init__:error:1584] Uncaught error from <Greenlet at 0x2116910: <bound method GDState.get_user_info of <idesksyncer.gdstate.GDState object at 0x7f93c4086a90>>>
Traceback (most recent call last):
  File "gevent/", line 390, in run
  File "idesksyncer/", line 201, in get_user_info
  File "idesksyncer/", line 1040, in get_user_info
  File "idesksyncer/", line 540, in __request
  File "idesksyncer/", line 354, in get_token
  File "gevent/", line 223, in get
GDAuthError: Access token refresher stopped.
INFO     2017-02-09 10:51:03,096 [__init__:info:1610] unwatching /mass
INFO     2017-02-09 10:51:03,097 [__init__:info:1610] GDUser(id=u'104202020526293411761', email=u'', name=u'FuBar') (existing) is now being synced.

Removing the account, refreshing the token, and adding it again produces the same results.


@Beryllium: Apologies for the trouble. Please send a copy of the folder ~/.config/Insync to for investigation. You can compress it before sending to save space.


I’m having the same problem. Was there a solution to this?


I’m also having this error now and I can no longer sync any files or even use the UI as a result.


So sorry for the trouble! Tagging our engineer @Kurt_Ko for further assistance.