Permanent unsynched status for selective file and folder sync

Bugs and issues
1

Hi,

I’ve been using Insync to bring keep a small number of files and folders for several years on a number of Linux machines.

After a recent installation of Kubuntu 24.04 I’ve found that v3.9.6.60027 permanently shows the files I’ve selected with the two arrow (sync in progress) icon.

Screenshot_20250817_182629
Screenshot_20250817_1826291007×898 114 KB

I managed to ‘trick’ it into syncing once by clicking the 2-way sync button at the top of the window but this now seems to setup a new folder.

I did wonder if it is just the UI but no, I have created new files server side and client side in synced folders and they are never synced.

The log file contains many similar messages such as below if that helps?

js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1755452496989&ver=1.110.0' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1755452498432&ver=1.110.0' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1755452496989&ver=1.110.0&retry_count=1' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1755452498432&ver=1.110.0&retry_count=1' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1755452496989&ver=1.110.0&retry_count=1&' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1755452498432&ver=1.110.0&retry_count=1&' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
2

My apologies for the trouble! PostHog errors should be benign and won’t cause any issues on your Insync setup.

Could you please let me know if you see “scanning…” or “syncing…” at the bottom right of the app whenever this perpetual blue circle happens? Please also send your logs.db and out.txt files to support@insynchq.com with the following information:

  • Name of affected folders
  • Link to this forums post

Thank you!