PhilippC / PhilippC/keepass2android
[QUESTION] Issue: 'No such File': Empty directories, SFTP via local NAS
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
Hi,
I've stumbled into an issue where K2A can no longer "see" my local server files and therefore cannot access my password file.
I updated my NAS OS recently to TOS 6.0 (TerraMaster F4-423) and I have always used SFTP just fine with K2A.
I use the correct credentials to login, and the connection is successful. My file password and fingerprint is successful (there is a local backup on my phone) but when trying to sync the file, I have started to get the error 'no such file'.
I've spent some time searching, including the forum, and tried the suggested single slash / to bring up the file explorer. I can see directories in my root folder, but they are incorrectly empty. It looks like a permission issue, but considering I'm using the correct credentials for my server, of which there's no issues from my Linux machines, I'm confused.
I installed a different app on my phone to test SFTP, and I can successfully login using it with the same credentials, being able to fully browse the NAS and see my password file just fine. I can't work out why K2A cannot.
Any help would be appreciated, thanks.
What version of Keepass2Android are you using?
1.12r5
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified in the issue. Start by reproducing the SFTP sync on Keepass2Android 1.12r5 with the TerraMaster F4-423 running TOS 6.0, comparing its directory listing with another SFTP app using the same credentials. Done means the password file is visible and synchronization succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100