Roout cause for "Failed Elements (2)" message

So I’ve set up Syncthing to sync my Android’s /storage/emulated/0 directory. All is fine, except, that I have this annoying red message “Failed Elements (2)” in the top right corner of that folder in the Syncthing(-fork) client on Android.

I’d like to add whatever fails (due access rights, locking, whatever) to the ignorelist, but I just can’t seem to find out which 2 elements actually failed.

There’s nothing in the last changes list and the protocol in the settings doesn’t shed any light either.

Any idea where else I could look?

Please post a screenshot of your Syncthing UI and your recent logs. I’m willing to take a swing at it.

There’s nothing sticking out in that log (also not further down)

Thanks. My apologies – I don’t know if this is something I can help with. I’m not a member of the Syncthing team, just someone who tries to help out on the forum when I can. My non-English language skills are poor, I have never owned an Android device, and I’ve only been using Syncthing for a few months. Hopefully someone else on the forum can help you figure this out.

1 Like

Please check the specific error messages in the Web GUI (available from the left slide-out menu in the app). Screenshots from the Web GUI would be helpful too.

2 Likes

Thank you, I wasn’t aware of that. That clearly shows me where it gets the permission denied.

1 Like

On Android, this can mean that you’ve got one of the "*/:<>?\| characters in your filenames. Android doesn’t support those on the user storage.

1 Like

You shouldn’t share your whole profile although you tame the “ignore” syntax, at least in Windows/Linux. For Android I’m not sure, but be aware that some files may be hidden (not the same way depending on the OS - .filename vs H attribute).

Also take note that ST now defaults to case-unsensitive for new folder shares, which is the Windows/MAC behaviour but not Linux. ST is a great piece of soft, so please give some effort to learn and know some specific things. Sharing the whole profile is a use case that makes learning ST a bit deeper more mandatory than a classical folder sharing with the intuitive GUI requires.

Enjoy

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