Troubleshooting
What to do when a lnk bucket command refuses or misses files (Your
folders, in your backends).
"is in none of Link's folders"
Move the files into ~/Link/Personal or an agent's folder: lnk bucket takes only paths in them.
clean or pull refuses in an agent's folder
pull and clean refuse while the agent runs, or when Link can't
tell, so stop it first: lnk agent stop --agent <name>.
"no backend here that signs links"
Push the files to an AWS or S3 backend, not archived: lnk bucket push <path> --backend <name>.
A share's download answers 403
The link or its signing credentials expired: URLs signed with an SSO
or aws sts session stop working when that session ends. Share the
files again.
tree misses files from another machine
tree works offline, from the manifest this machine keeps. lnk bucket tree --refresh lists the backends again first, and finds them.
"that password doesn't open the files already in ..."
backend connect and adopt refuse a password that doesn't decrypt a file
already there: use the bucket's original password.