I updated to 1.9
After starting keepass and creating a new entry i want to store.
That fails.
At the next open there was no keepass.kdbx anymore.
I renamed the temp File keepass.kdbx.temp to keepass.kdbx.
Than next try with the same result. gone back to 1.8, that work fine
Last edit: telemaxx 2014-09-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having the same issue. I've attached my error output. I noticed that in the error reference it mentions moving the .tmp file back to the original directory but the leading / has been dropped. I don't know if that's just the presentation or the actual raw output.
I had this issue. Fixed it by unchecking 'Use File transactions for writing Database' Then it worked like a charm. The problem probably lies in that when this is ON it removes the kdbx and creates a kdbx.temp file instead and for some reason after that KP2 doesn't know where to save. Unchecking this box solves the problem.
The 1.10 version did break something in the path resolution in the SFTP. My keepass gives the following error.
Are the previous versions of the IOProtocolExt available? Where can I download the version 1.8?
UPDATE1: I checked the file with FileZilla and verified that it still exists in the current location. There is no change in the Keepass or configuration except the IOProtocolExt update from 1.8 to 1.10.
UPDATE2: I found the v1.8 from my other computer and copied to the current one overwriting v1.10. The problem is fixed so, confirmed that the error is due to new version.
Searching for host...
Connecting to host...
Authenticating...
WARNING! Giving up security and accepting any key as configured!
Using username "<user>".
Authenticating with pre-entered password.
Authenticated.
Starting the session...
Reading remote directory...
Session started.
Active session: [1] <session>
Error listing directory '<remote directory="">'.
No such file or directory.
Error code: 2
Error message from server: No such file
(A)bort, (R)etry, (S)kip: Abort
Best,
Can
Last edit: Can Komar 2014-09-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As 1.10 works fine with all servers that I tested, I'll keep listing this as latest version. If anyone can provide/point to a server for reproducing any issue, I'll happily look into it.
Version 1.10 in some cases interprets paths differently than 1.8. The fact that 1.8 worked for you, but not 1.10, doesn't necessarily indicate a bug in 1.10; maybe you need to adjust your URL.
Best regards,
Dominik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried replacing the last / with a space. It didn't help. The url is only numbers and letters except for an underscore _ in the NAS path and two colons: as above
The kbdx was just a typo in my post.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you sure that your home directory is / ? With 1.10, your URL only works if this is the case. 1.8 incorrectly always interpreted paths as being relative to / instead of the home directory.
If your home directory is e.g. /home/username, you instead have to use an URL like sftp://myddnsserver/../../mnt/HD/HD_a2/KeePass/keepass.kdbx or sftp://myddnsserver//mnt/HD/HD_a2/KeePass/keepass.kdbx
Best regards,
Dominik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is it possible that your directory "home2" is not off the root of the server?
Can you connect the server with an SFTP program (WinSCP) and see what your home folder is called?
Try these URLs:
sftp://ftp.chitown.name:34890/../home2/dhynes/public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/./dhynes/public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/./public_html/keepazz_48.kdbx
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I doubt '/' is your home directory; '/home2/dhynes' more likely is. If this is the case, your URL should be
sftp://ftp.chitown.name:34890/public_html/keepazz_48.kdbx
Best regards,
Dominik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the alternative URLs, I tried them, and found two URLs work exclusively with 1.8:
sftp://ftp.chitown.name:34890/home2/dhynes/public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/../home2/dhynes/public_html/keepazz_48.kdbx
And two will not work with 1.8, but work exclusively with 1.10:
sftp://ftp.chitown.name:34890/./public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/public_html/keepazz_48.kdbx
Importantly, when I navigate to the database with WinSCP and Filezilla, the path in the folder window is the 1.8 style: “/home2/dhynes/public_html/keepazz_48.kdbx”
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From the responses it seems that IOProtocolExt splits the file path from the server/port using forward slash as the delimiter. e.g. sftp://ftp.chitown.name:34890/public_html/keepazz_48.kdbx would be split and uses as follows:
Connect to sftp://ftp.chitown.name on port 34890
Open public_html/keepazz_48.kdbx
To make the access relative to the root you would need to add an extra forward slash to your URL after the server/port, e.g. sftp://ftp.chitown.name:34890//home2/dhynes/public_html/keepazz_48.kdbx
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a same problem and took me 2 hours to find that I need extra / to make the URL working, next time I will search here first once I got some error message.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Because keepass seems to be able to connect, you won't immediately try to add the (default) port. The description says that you need to fill in 'The complete URL [...] including protocol, server and full path to the file', which is in this case a bit misleading, as you might skip the default port.
Besides these small issues, thanks for a great tool! :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have test it w. 1.10 (Qnap NAS Server)
not work: sftp://mynas:22/share/HDA_DATA/Qsoft/KeePass-2.28/myfile.kdbx
work: ftp://mynas:21/Qsoft/KeePass-2.28/myfile.kdbx
So with underscore it does not work.
Thanks for a great tool.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The path that is shown in eg WinSCP cannot be simply copied and pasted into Keepass since IOProtocolEXT 1.10. It used to work with 1.08 but not any more. You need to add an extra slash in the path after the port.
eg old path used in Keepass with IOProtocolEXT 1.08 and earlier:
These did not work for me either:
sftp://dyndns:port/Folder1/Folder2/Filename.kdbx
sftp://dyndns:port//Folder1/Folder2/Filename.kdbx
sftp://dyndns:port/./Folder1/Folder2/Filename.kdbx
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I updated to 1.9
After starting keepass and creating a new entry i want to store.
That fails.
At the next open there was no keepass.kdbx anymore.
I renamed the temp File keepass.kdbx.temp to keepass.kdbx.
Than next try with the same result. gone back to 1.8, that work fine
Last edit: telemaxx 2014-09-21
I will have a look at this tomorrow.
Thanks and best regards,
Dominik
I confirm the 1.9 is broken.
Thank you for your support.
Having the same issue. I've attached my error output. I noticed that in the error reference it mentions moving the .tmp file back to the original directory but the leading / has been dropped. I don't know if that's just the presentation or the actual raw output.
I had this issue. Fixed it by unchecking 'Use File transactions for writing Database' Then it worked like a charm. The problem probably lies in that when this is ON it removes the kdbx and creates a kdbx.temp file instead and for some reason after that KP2 doesn't know where to save. Unchecking this box solves the problem.
IOProtocolExt 1.10 has been released, which improves support for paths with subdirectories relative to the initial working directory.
The new version is available on
http://keepass.info/plugins.html#ioprotocolext
Best regards,
Dominik
Hi Dominik,
The 1.10 version did break something in the path resolution in the SFTP. My keepass gives the following error.
Are the previous versions of the IOProtocolExt available? Where can I download the version 1.8?
UPDATE1: I checked the file with FileZilla and verified that it still exists in the current location. There is no change in the Keepass or configuration except the IOProtocolExt update from 1.8 to 1.10.
UPDATE2: I found the v1.8 from my other computer and copied to the current one overwriting v1.10. The problem is fixed so, confirmed that the error is due to new version.
ERROR >>>
KeePass
sftp://<remote host="">/<remote directory="">/db.kdbx (keepass)
An exception occurred during a WebClient request.
Searching for host...
Connecting to host...
Authenticating...
WARNING! Giving up security and accepting any key as configured!
Using username "<user>".
Authenticating with pre-entered password.
Authenticated.
Starting the session...
Reading remote directory...
Session started.
Active session: [1] <session>
Error listing directory '<remote directory="">'.
No such file or directory.
Error code: 2
Error message from server: No such file
(A)bort, (R)etry, (S)kip: Abort
Best,
Can
Last edit: Can Komar 2014-09-23
Hi,
I have the same problem here with the 1.10 version.
Regards,
Gregory
dito.
gone back to 1.8
The old version 1.8 of IOProtocolExt is available on
http://keepass.info/plugins_old.html
As 1.10 works fine with all servers that I tested, I'll keep listing this as latest version. If anyone can provide/point to a server for reproducing any issue, I'll happily look into it.
Version 1.10 in some cases interprets paths differently than 1.8. The fact that 1.8 worked for you, but not 1.10, doesn't necessarily indicate a bug in 1.10; maybe you need to adjust your URL.
Best regards,
Dominik
Hi,
Similar problem for me too. SFTP through company proxy is OK with v1.8 but not with v1.10.
How should the url be adjusted?
url looks like this
sftp://DDNS address:443/path to file on NAS/filename.kdbx
Last edit: Mark 2014-09-24
Try removing one of the last slashes. Furthermore, the usual database file extension is KDBX, not KBDX.
Best regards,
Dominik
I tried replacing the last / with a space. It didn't help. The url is only numbers and letters except for an underscore _ in the NAS path and two colons: as above
The kbdx was just a typo in my post.
My not working path:
sftp://myddnsserver/mnt/HD/HD_a2/KeePass/keepass.kdbx
Works with 1.8
Are you sure that your home directory is / ? With 1.10, your URL only works if this is the case. 1.8 incorrectly always interpreted paths as being relative to / instead of the home directory.
If your home directory is e.g. /home/username, you instead have to use an URL like sftp://myddnsserver/../../mnt/HD/HD_a2/KeePass/keepass.kdbx or sftp://myddnsserver//mnt/HD/HD_a2/KeePass/keepass.kdbx
Best regards,
Dominik
IOProtocolExt 1.10 fails to open documents on my server, previous versions to 1.8 worked fine.
The request URL looks like
sftp://ftp.chitown.name:34890/home2/dhynes/public_html/keepazz_48.kdbx
If IOProtocolExt breakes on URLs that specify the port, that's a dealbreaker (and a bug)
Is it possible that your directory "home2" is not off the root of the server?
Can you connect the server with an SFTP program (WinSCP) and see what your home folder is called?
Try these URLs:
sftp://ftp.chitown.name:34890/../home2/dhynes/public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/./dhynes/public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/./public_html/keepazz_48.kdbx
cheers, Paul
I doubt '/' is your home directory; '/home2/dhynes' more likely is. If this is the case, your URL should be
sftp://ftp.chitown.name:34890/public_html/keepazz_48.kdbx
Best regards,
Dominik
Thanks for the alternative URLs, I tried them, and found two URLs work exclusively with 1.8:
sftp://ftp.chitown.name:34890/home2/dhynes/public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/../home2/dhynes/public_html/keepazz_48.kdbx
And two will not work with 1.8, but work exclusively with 1.10:
sftp://ftp.chitown.name:34890/./public_html/keepazz_48.kdbx
sftp://ftp.chitown.name:34890/public_html/keepazz_48.kdbx
Importantly, when I navigate to the database with WinSCP and Filezilla, the path in the folder window is the 1.8 style: “/home2/dhynes/public_html/keepazz_48.kdbx”
Thanks for testing this. Like I guessed, your home directory is '/home2/dhynes', and the behavior of 1.10 is correct (and 1.8 is incorrect). Great :-)
Best regards,
Dominik
From the responses it seems that IOProtocolExt splits the file path from the server/port using forward slash as the delimiter. e.g. sftp://ftp.chitown.name:34890/public_html/keepazz_48.kdbx would be split and uses as follows:
Connect to sftp://ftp.chitown.name on port 34890
Open public_html/keepazz_48.kdbx
To make the access relative to the root you would need to add an extra forward slash to your URL after the server/port, e.g. sftp://ftp.chitown.name:34890//home2/dhynes/public_html/keepazz_48.kdbx
cheers, Paul
Thanks for your experience.
I have a same problem and took me 2 hours to find that I need extra / to make the URL working, next time I will search here first once I got some error message.
After some trial-and-error, I found out that the following URL, without port number, does not work with 1.10:
sftp://my.server/dir-in-homedir/passwordsafe.kdbx
But after adding the default SSH port 22, I get access again:
sftp://my.server:22/dir-in-homedir/passwordsafe.kdbx
Because keepass seems to be able to connect, you won't immediately try to add the (default) port. The description says that you need to fill in 'The complete URL [...] including protocol, server and full path to the file', which is in this case a bit misleading, as you might skip the default port.
Besides these small issues, thanks for a great tool! :-)
I have test it w. 1.10 (Qnap NAS Server)
not work: sftp://mynas:22/share/HDA_DATA/Qsoft/KeePass-2.28/myfile.kdbx
work: ftp://mynas:21/Qsoft/KeePass-2.28/myfile.kdbx
So with underscore it does not work.
Thanks for a great tool.
Hi,
The path that is shown in eg WinSCP cannot be simply copied and pasted into Keepass since IOProtocolEXT 1.10. It used to work with 1.08 but not any more. You need to add an extra slash in the path after the port.
eg old path used in Keepass with IOProtocolEXT 1.08 and earlier:
sftp://dyndns:port/share/MD0_DATA/Folder1/Folder2/filename.kdbx
New path to use since 1.10:
sftp://dyndns:port//share/MD0_DATA//Folder1/Folder2/filename.kdbx
These did not work for me either:
sftp://dyndns:port/Folder1/Folder2/Filename.kdbx
sftp://dyndns:port//Folder1/Folder2/Filename.kdbx
sftp://dyndns:port/./Folder1/Folder2/Filename.kdbx