Resetting A Secret


atte

Recommended Posts

I have three clients that seems to have gotten a bit confused, at least they each state that one secret (143G) is unsynced, and leaving them on for a loooong time doesn't help.

 

What's the easiest way to the secret in question on all three nodes? Could it  for instance be done by deleting one of the .db* files in .btsync? How do I find the right one?

 

I'm on linux running btsync-gui version 0.8.5-1 installed from debian repos (not sure how to deduct the actual btsync version)

Link to comment
Share on other sites

What's the easiest way to the secret in question on all three nodes? Could it  for instance be done by deleting one of the .db* files in .btsync? How do I find the right one?

The easiest way would be to remove the folder from Sync on your devices, and then re-add it back to your devices with a new key (secret) that's the same on each device.

By removing and re-adding a folder, it will trigger a re-index of the folder, which should resolve any indexing-related issues you might be facing.

Link to comment
Share on other sites

Thanks!

 

This would leave unused .db* in .btsync, but I assume those would not be updated anymore, and so after a week it's pretty obvious which ones are in use...

 

What about the .sync dir in the root of the added folder, it's no problem when re-adding, that this (and maybe other) traces of a previous sync is present in the folder?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.