Some protected files may be overwritten and cause issues.

Support
1

Getting the following error:

2017-02-13 16:07:19: Some protected files may be overwritten and cause issues. See http://docs.syncthing.net/users/config.html#syncing-configuration-files for more information. The at risk files are: /Users//Library/Application Support/Syncthing/index-v0.14.0.db, /Users//Library/Application Support/Syncthing/config.xml, /Users//Library/Application Support/Syncthing/cert.pem, /Users//Library/Application Support/Syncthing/key.pem

Not sure what this is?

2

Did you follow the link to the page that tries to answer exactly your question?

Edit: it looks like the https redirect may eat the anchor link: https://docs.syncthing.net/users/config.html#syncing-configuration-files works better. This is already fixed in Syncthing, but not in the current release.

But you seem to have a weird setup. From the error message you have either an empty username or something is strangely configured.

3

So I believe I discovered a bug. When you re-add a share, when you go to enter the path, it will ostensibly autofill the path based on what you typed in the past.

So I entered ~/Users/ and it autofilled the rest of the path. I hit enter, the full path remained in the slot. But when I hit OK and then examined the resultant share, the path was only the portion I had typed manually.

As a result I was syncing my entire user profile directory with my coworkers machine, hence the error.

It seems the autofill is useless and you have to make sure to type the entire path matter what.

4

I think I remember that this autofill issue is caused by Safari and doesn’t happen in other browsers.

1 Like
5

Yeah, there was a bug about this a while back in the tracker, but I couldn’t find it now. Basically, the browser doesn’t tell us when it changes the text field based on the autocomplete, so it never reaches Syncthing.

6

Could you point us to issue/pull request? I found open issue lib/model: “overwriting protected files” warning doesn’t properly take ignores into account for this. Or by fixed you mean that these configuration directories/files are somehow automatically ignored now?

7

I mean that the http link in the warning message is now an https link.

8

Is there any way to suppress this warning? Shouldn’t it be suppressed automatically if someone ignored configuration directory in all shared directories which include it?

EDIT

Well, I guess issue https://github.com/syncthing/syncthing/issues/3183 answers the second question.

9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.