You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Suncatcher16 <su...@outlook.com> on 2017/06/15 17:13:46 UTC
SFTP error "unable to open file XXX" on Win8 RDP host
I set up OpenSSH for Windows by advice of Erik Berndt
<http://apache-guacamole-incubating-users.2363388.n4.nabble.com/Recommended-SFTP-server-for-RDP-hosts-tp1150p1151.html>
and connected succesfully, but I am not able to upload files, only download.
Here is the error I get
<http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n1155/Untitled.png>
And here is what I see in log
> Jun 15 16:45:20 ip-172-31-21-70 guacd[4156]: Unable to close file
> Jun 15 16:45:20 ip-172-31-21-70 guacd[4156]: Unable to open file
> "/D:/HA300_EN_Col97_FV_A4.pdf"
> Jun 15 16:46:48 ip-172-31-21-70 guacd[4156]: Unable to close file
> Jun 15 16:46:48 ip-172-31-21-70 guacd[4156]: Unable to open file
> "./putty.exe"
> Jun 15 16:55:05 ip-172-31-21-70 guacd[4156]: Unable to close file
> Jun 15 16:55:05 ip-172-31-21-70 guacd[4156]: Unable to open file
> "/D:/RegistryCleaner.reg"
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by halcyon <sr...@gmail.com>.
Here is a simple way to reproduce this issue:
On the Windows machine using Powershell/OpenSSH edit c:\Program
Files\OpenSSH\sshd_config and change:
Subsystem sftp sftp-server.exe
to this:
Subsystem sftp sftp-server.exe -l VERBOSE
If not already created, create C:\Program Files\OpenSSH\logs\sftp-server.log
and grant Users write privileges.
Restart Windows sshd daemon
Open a Powershell on the Windows machine and enter the following:
Get-Content C:\Program Files\OpenSSH\logs\sftp-server.log -wait
On a client, use an SFTP client to copy a file to the Windows machine. If
you use OpenSSH sftp client, the log on the Windows machine will look
something like this:
17456 15:07:28:380 session opened for local user user@computername from
[192.168.5.144]
17456 15:07:28:380 received client version 3
17456 15:07:28:380 realpath "."
17456 15:09:56:241 stat name "/C:/Users/user/Documents/test.txt"
17456 15:09:56:241 sent status No such file
17456 15:09:56:241 open "/C:/Users/user/Documents/test.txt" flags
WRITE,CREATE,TRUNCATE mode 0755
17456 15:09:56:241 close "/C:/Users/user/Documents/test.txt" bytes read 0
written 586
17456 15:11:02:320 session closed for local user user@computername from
[192.168.5.144]
Note the permission 0755 - these are octal values for what is essentially
user RWX, Group RX, Others RX
Now, if you use the libssh2 sftp_write example, source located in:
/usr/share/doc/libssh2-1-dev/examples
On Debian based systems. This source code is very similar to Guacamoles sftp
functionality:
See https://github.com/libssh2/libssh2/blob/master/example/sftp_write.c and
https://github.com/apache/incubator-guacamole-server/blob/master/src/common-ssh/sftp.c
(Look at the libssh2_sft_open methods )
Using this tool to test libssh2 SFTP library using for example:
./sftp_write 192.168.5.206 user password123 /tmp/test.txt
/C:/Users/user/Documents/test.txt
The logs will look like this:
18016 15:22:23:407 session opened for local user user@computername from
[192.168.5.144]
18016 15:22:23:407 received client version 3
18016 15:22:23:407 open "/C:/Users/user/Documents/test.txt" flags
WRITE,CREATE,TRUNCATE mode 0100644
18016 15:22:23:407 sent status Failure
18016 15:22:23:407 session closed for local user user@computername from
[192.168.5.144]
and sftp_write will output this:
Fingerprint: AC 26 92 D0 DC 08 28 34 9A 22 AE 0E A3 DD 9C 7A E8 97 5B 00
libssh2_sftp_init()!
libssh2_sftp_open()!
Unable to open file with SFTP
all done
NOTE: the mode bits are now 0100644, this is due to the Or'ing of the
original permission bits with LIBSSH2_SFTP_ATTR_PFILETYPE_FILE which is
defined in libssh2's sftp.c file as and octal value:
/* S_IFREG */
#define LIBSSH2_SFTP_ATTR_PFILETYPE_FILE 0100000
/* Filetype in SFTP 3 and earlier */
attrs.permissions = mode |
(open_file ? LIBSSH2_SFTP_ATTR_PFILETYPE_FILE :
LIBSSH2_SFTP_ATTR_PFILETYPE_DIR);
When Powershell/OpenSSH get's this extended permission bits, it can't cope.
This is why I have removed the Or'ing of the permission bits from libssh2's
sftp.c to get mode flags OpenSSH can cope with. A work around only, as I
have not rolled out to prod. Waiting for 0.9.14 to migrate app served in
Windows to Linux via NX
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by vnick <vn...@apache.org>.
Suncatcher16 wrote
> Excellent!
Microsoft (or whomever it is that develops OpenSSH for Windows) has marked
the bug as fixed. Fix should be available in latest build:
https://github.com/PowerShell/Win32-OpenSSH/releases/tag/v0.0.22.0
-Nick
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
Excellent!
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by vnick <vn...@apache.org>.
vnick wrote
> Have opened an issue on Github for this:
>
> https://github.com/PowerShell/Win32-OpenSSH/issues/883
>
> -Nick
FYI, got a response on the Win32 OpenSSH github Issue:
> We'll fix this for Oct-Mid drop.
-Nick
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by vnick <vn...@apache.org>.
vnick wrote
> halcyon wrote
>> I have been running into this issue. In my case it is an incompatibility
>> between libssh2 and openssh (Win32 ). To get around this I downloaded the
>> libssh2 code from Github and made the following changes:
>>
>> around line 1060 in sftp_open in sftp.c
>>
>> change:
>>
>> attrs.permissions = mode |
>> (open_file ? LIBSSH2_SFTP_ATTR_PFILETYPE_FILE :
>> LIBSSH2_SFTP_ATTR_PFILETYPE_DIR);
>>
>> to
>> attrs.permissions = mode;
>
> Hmmm...so looks like it's something specific to how Microsoft has
> implemented OpenSSH for Win32, since it works fine against Linux SSH
> servers
> and against at least the SolarWindows SFTP/SCP server. I'm not sure the
> above change is a good long-term fix, but it does help to narrow down the
> issue and may point to what's actually going on here. I'm tempted to open
> up an issue on the Github page for that OpenSSH implementation with this
> information, as I think there's probably something Microsoft is not doing
> quite right in their implementation that is causing this.
Have opened an issue on Github for this:
https://github.com/PowerShell/Win32-OpenSSH/issues/883
-Nick
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by vnick <vn...@apache.org>.
halcyon wrote
> I have been running into this issue. In my case it is an incompatibility
> between libssh2 and openssh (Win32 ). To get around this I downloaded the
> libssh2 code from Github and made the following changes:
>
> around line 1060 in sftp_open in sftp.c
>
> change:
>
> attrs.permissions = mode |
> (open_file ? LIBSSH2_SFTP_ATTR_PFILETYPE_FILE :
> LIBSSH2_SFTP_ATTR_PFILETYPE_DIR);
>
> to
> attrs.permissions = mode;
Hmmm...so looks like it's something specific to how Microsoft has
implemented OpenSSH for Win32, since it works fine against Linux SSH servers
and against at least the SolarWindows SFTP/SCP server. I'm not sure the
above change is a good long-term fix, but it does help to narrow down the
issue and may point to what's actually going on here. I'm tempted to open
up an issue on the Github page for that OpenSSH implementation with this
information, as I think there's probably something Microsoft is not doing
quite right in their implementation that is causing this.
Thank you for the info, halcyon!
-Nick
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by vnick <vn...@apache.org>.
Suncatcher16 wrote
> I appreciate your willingness to assist but I am still waiting any comment
> from Devs about this issue.
I downloaded OpenSSH for Windows (the Microsoft version) and installed it,
and encountered the same issue you did trying to upload a file. I
downloaded the Free SolarWinds SFTP/SCP Server for Windows[1] and installed
it, and it works perfectly fine for me (note: I am not making any claim
about compatibility of Guacamole, Windows, and SolarWindows SFTP/SCP server,
nor am I endorsing it - I just said, it works for me). So, as halcyon
already mentioned in trying to help you with this:
> I have been running into this issue. In my case it is an incompatibility
> between libssh2 and openssh (Win32 ). To get around this I downloaded the
> libssh2 code from Github and made the following changes...
This does, indeed, seem to be an issue specific to Microsoft's
implementation of OpenSSH, and, in particular, with permission translation
between libssh2 and OpenSSH on Windows. In Microsoft's defense (a rare
thing for me to do), when you go to download OpenSSH from their Github page,
it specifically says, in rather bold type:
> This is a pre-release (non-production ready)
So you should not be surprised that there are issues, particularly
compatibility issues, between more mature software (libssh2) and Microsoft's
port of OpenSSH.
> If they claim some functionality to be presented
> (SFTP for Windows hosts), they should be able to explain how it should
> work,
> which SSH-servers are supported on windows platforms and etc.
You seem to be treating Guacamole like a piece of commercial software and
not like an ongoing, open source, community-driven project. We don't have
access to every possible platform and combination of software, so we make it
as compatible as we know how, and we rely on the community to bring issues
to our attention, to provide the information necessary to help resolve those
problems, and to support each other and share our experiences, which is what
halcyon has been trying to do.
-Nick
[1] www.solarwinds.com/free-tools/free-sftp-server
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
halcyon wrote
> I can post comprehensive steps to reproduce my solution to this error. If
> you
> can copy files from the Windows sftp-server but not put file onto the
> Windows sftp-server, then you have the same problems I have. It takes
> about
> 10 mins to fix. You just need to make sure libssh2 is no longer in your
> apt
> / yum history.
I appreciate your willingness to assist but I am still waiting any comment
from Devs about this issue. If they claim some functionality to be presented
(SFTP for Windows hosts), they should be able to explain how it should work,
which SSH-servers are supported on windows platforms and etc.
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by halcyon <sr...@gmail.com>.
I can post comprehensive steps to reproduce my solution to this error. If you
can copy files from the Windows sftp-server but not put file onto the
Windows sftp-server, then you have the same problems I have. It takes about
10 mins to fix. You just need to make sure libssh2 is no longer in your apt
/ yum history.
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by vnick <vn...@apache.org>.
Suncatcher16 wrote
> Too complex solution. Maybe its better to adapt Guacamole library to make
> it
> more universal, and to support more SSH-severs?
I think there have been a few recent changes targeted at this. Have you
tried rebuilding the Guacamole code (both client and server) from git
master, yet?
Another potential solution, one that I use in my environment, is to have the
SFTP server be Linux-based, and use the sftp-root-directory to restrict
uploads to a certain directory, then make the SFTP Server available via CIFS
(Samba). That way, the users can upload files to a folder on the SFTP
server, then access those files via a UNC path or mapped drive. I'm not
certain this will work in your scenario, but it's another potential
work-around while the Windows SSH/SFTP support in Guacamole gets tweaked.
-Nick
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
Too complex solution. Maybe its better to adapt Guacamole library to make it
more universal, and to support more SSH-severs?
I asked
<http://apache-guacamole-incubating-users.2363388.n4.nabble.com/Recommended-SFTP-server-for-RDP-hosts-td1150.html#a1151>
which SSH-servers are recommended for use with Guacamole but got no response
from devs.
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by halcyon <sr...@gmail.com>.
I have been running into this issue. In my case it is an incompatibility
between libssh2 and openssh (Win32 ). To get around this I downloaded the
libssh2 code from Github and made the following changes:
around line 1060 in sftp_open in sftp.c
change:
attrs.permissions = mode |
(open_file ? LIBSSH2_SFTP_ATTR_PFILETYPE_FILE :
LIBSSH2_SFTP_ATTR_PFILETYPE_DIR);
to
attrs.permissions = mode;
Run automke tools, run configure, make libssh2, make install libssh2. Then
recompile guacamole server from source against this modified libssh2
library, install guacamole server, restart guacamole client and everything
worked. Issue is current libssh2 performing this OR with
LIBSSH2_SFTP_ATTR_PFILETYPE_FILE makes the permissions something like
0100755 instead of 0755 and the Win32 OpenSSH server can't cope. Turn on
logs in Win32 OpenSSH to see what the sftp server is doing. Add l VERBOSE to
the sftp-server command line args in sshd_config.
You may also need to change Windows permission on the sftp-server.log file
if anyone other than Administrator or SYSTEM\sshd is performing the file
transfer. Ironically, the OpenSSH sftp client works.
--
Sent from: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
So what I steps I can take further to narrow the problem?
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1349.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
> I mean the body of code which builds guacd, libguac, the various
> supported protocols, etc.:
I built them, guacd and guacamole-server at the same time, so they
definitely match each other.
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1312.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
Mike Jumper wrote
> When testing Guacamole vs. other SFTP clients, are you using the same
> user account on the RDP server in all cases?
>
> - Mike
Yes, indeed.
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1311.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Mike Jumper <mi...@guac-dev.org>.
On Fri, Jul 14, 2017 at 11:10 AM, Suncatcher16 <su...@outlook.com> wrote:
>
>> Is it possible that you're only using a recent build of
>> guacamole-client, and not guacamole-server, thus the new SFTP root
>> directory parameter is being ignored?
>
> What do you mean by /guacamole-server/? WAR-file?
I mean the body of code which builds guacd, libguac, the various
supported protocols, etc.:
http://guacamole.incubator.apache.org/doc/gug/installing-guacamole.html#building-guacamole-server
The WAR file (part of guacamole-client) is somewhat relevant, too, as
only an up-to-date web application would have the definition of the
new "sftp-root-directory" parameter, but that would only make defining
a connection which uses that parameter more difficult for users of the
database authentication. The key piece which determines whether the
parameter works is guacamole-server. If too old, the
"sftp-root-directory" parameter will not exist for the protocol
plugins loaded by guacd, and specifying it will have no effect.
> My guacd is
>
>> Starting guacd: guacd[1889]: INFO: Guacamole proxy daemon (guacd)
>> version 0.9.12-incubating started
>> SUCCESS
>
> And my Tomcat app is 0.9.12 too.
>
> <http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n1309/Sketch.png>
>
Ah, OK - that definitely would not have the necessary parameter then.
The changes from GUACAMOLE-303 were merged in after the version
numbers were bumped to 0.9.13-incubating in anticipation of the first
RC. To be able to use the new parameter, you will need to build from
git master.
The new "sftp-root-directory" parameter only affects the directories
displayed in the file browser, however. If you are already able to
navigate through the file browser without error, then that isn't the
problem.
I agree that if the only SFTP client that fails in your case is
Guacamole, then that suggests the problem is within Guacamole. It is
unlikely that the SFTP requests are not reaching your SSH server at
all - if the SFTP connection had failed, then Guacamole would have
aborted the connection entirely.
When testing Guacamole vs. other SFTP clients, are you using the same
user account on the RDP server in all cases?
- Mike
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
> Is it possible that you're only using a recent build of
> guacamole-client, and not guacamole-server, thus the new SFTP root
> directory parameter is being ignored?
What do you mean by /guacamole-server/? WAR-file?
My guacd is
> Starting guacd: guacd[1889]: INFO: Guacamole proxy daemon (guacd)
> version 0.9.12-incubating started
> SUCCESS
And my Tomcat app is 0.9.12 too.
<http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n1309/Sketch.png>
> My first guess would be
> permissions, but the SSH server logs may have specifics on what is
> failing.
sshd server log contains no SFTP-related strings at all. It looks like this:
> 876 12:24:44:934 Accepted password for JohnDoe from 52.52.52.52 port 35256
> ssh2
> 2432 12:25:11:287 Accepted password for JohnDoe from 52.52.52.52 port
> 35252 ssh2
> 2432 12:25:11:569 Received disconnect from 52.52.52.52 port 35252:11: Bye
> 2432 12:25:11:569 Disconnected from user JohnDoe 52.52.52.52 port 35252
> 876 14:17:51:136 Received disconnect from 52.52.52.52 port 35256:11: Bye
> 876 14:17:51:136 Disconnected from user JohnDoe 52.52.52.52 port 35256
> 1860 14:18:02:308 Received signal 8; terminating.
> 1768 14:16:33:352 Server listening on :: port 95.
> 1768 14:16:33:352 Server listening on 0.0.0.0 port 95.
> 600 14:23:08:025 Accepted password for JohnDoe from 52.52.52.52 port 35626
> ssh2
> 1768 18:38:26:763 Received signal 8; terminating.
> 1872 18:38:42:227 Server listening on :: port 95.
> 1872 18:38:42:227 Server listening on 0.0.0.0 port 95.
> 2704 19:22:30:922 Accepted password for JohnDoe from 52.52.52.52 port
> 36236 ssh2
> 812 19:33:52:611 Accepted password for JohnDoe from 192.168.137.122 port
> 42868 ssh2
> 812 19:36:25:345 Received disconnect from 192.168.137.122 port 42868:11:
> disconnected by user
> 812 19:36:25:345 Disconnected from user JohnDoe 192.168.137.122 port 42868
> 1976 19:38:15:657 Accepted password for JohnDoe from 192.168.137.122 port
> 42870 ssh2
> 1976 19:39:39:845 Received disconnect from 192.168.137.122 port 42870:11:
> disconnected by user
> 1976 19:39:39:845 Disconnected from user JohnDoe 192.168.137.122 port
> 42870
> 2524 19:40:59:876 Accepted password for JohnDoe from 192.168.137.122 port
> 42876 ssh2
> 2524 19:40:59:954 Received disconnect from 192.168.137.122 port 42876:11:
> disconnected by user
> 2524 19:40:59:954 Disconnected from user JohnDoe 192.168.137.122 port
> 42876
> 1668 19:41:32:423 Accepted password for JohnDoe from 192.168.137.122 port
> 42878 ssh2
> 1668 19:41:39:548 Received disconnect from 192.168.137.122 port 42878:11:
> disconnected by user
> 1668 19:41:39:548 Disconnected from user JohnDoe 192.168.137.122 port
> 42878
> 1232 19:42:20:751 Accepted password for JohnDoe from 192.168.137.122 port
> 42880 ssh2
> 1232 19:42:20:861 Received disconnect from 192.168.137.122 port 42880:11:
> disconnected by user
> 1232 19:42:20:861 Disconnected from user JohnDoe 192.168.137.122 port
> 42880
> 2704 19:44:34:780 Received disconnect from 52.52.52.52 port 36236:11: Bye
> 2704 19:44:34:780 Disconnected from user JohnDoe 52.52.52.52 port 36236
> 1872 19:44:41:484 Received signal 8; terminating.
> 1804 19:45:04:882 Server listening on :: port 95.
> 1804 19:45:04:882 Server listening on 0.0.0.0 port 95.
> 1848 19:58:27:493 Accepted password for JohnDoe from 52.52.52.52 port
> 36306 ssh2
> 1848 20:00:11:456 Received disconnect from 52.52.52.52 port 36306:11: Bye
> 1848 20:00:11:456 Disconnected from user JohnDoe 52.52.52.52 port 36306
> 1804 20:00:17:816 Received signal 8; terminating.
> 1828 11:18:47:748 Server listening on :: port 95.
> 1828 11:18:47:748 Server listening on 0.0.0.0 port 95.
> 872 11:29:25:329 Accepted password for JohnDoe from 192.168.137.153 port
> 60476 ssh2
> 2852 11:30:23:127 Accepted password for JohnDoe from 52.52.52.52 port
> 38010 ssh2
> 2852 11:31:26:315 Received disconnect from 52.52.52.52 port 38010:11: Bye
> 2852 11:31:26:315 Disconnected from user JohnDoe 52.52.52.52 port 38010
> 2836 11:31:30:779 Accepted password for JohnDoe from 52.52.52.52 port
> 38016 ssh2
> 2836 11:33:41:022 Received disconnect from 52.52.52.52 port 38016:11: Bye
> 2836 11:33:41:022 Disconnected from user JohnDoe 52.52.52.52 port 38016
> 2892 11:33:43:273 Accepted password for JohnDoe from 52.52.52.52 port
> 38028 ssh2
> 2892 11:34:56:569 Received disconnect from 52.52.52.52 port 38028:11: Bye
> 2892 11:34:56:569 Disconnected from user JohnDoe 52.52.52.52 port 38028
> 348 11:34:59:531 Accepted password for JohnDoe from 52.52.52.52 port 38034
> ssh2
> 348 11:37:44:273 Received disconnect from 52.52.52.52 port 38034:11: Bye
> 348 11:37:44:273 Disconnected from user JohnDoe 52.52.52.52 port 38034
> 280 11:37:49:240 Accepted password for JohnDoe from 52.52.52.52 port 38046
> ssh2
> 280 11:41:58:959 Received disconnect from 52.52.52.52 port 38046:11: Bye
> 280 11:41:58:959 Disconnected from user JohnDoe 52.52.52.52 port 38046
> 872 11:42:02:297 Received disconnect from 192.168.137.153 port 60476:11:
> disconnected by user
> 872 11:42:02:297 Disconnected from user JohnDoe 192.168.137.153 port 60476
> 1828 19:03:31:465 Received signal 8; terminating.
> 1824 19:03:45:773 Server listening on :: port 95.
> 1824 19:03:45:773 Server listening on 0.0.0.0 port 95.
> 800 19:06:13:305 Accepted password for JohnDoe from 52.52.52.52 port 41844
> ssh2
> 800 19:08:55:160 Received disconnect from 52.52.52.52 port 41844:11: Bye
> 800 19:08:55:160 Disconnected from user JohnDoe 52.52.52.52 port 41844
> 1832 19:08:58:192 Accepted password for JohnDoe from 52.52.52.52 port
> 41850 ssh2
> 1832 19:18:00:793 Received disconnect from 52.52.52.52 port 41850:11: Bye
> 1832 19:18:00:793 Disconnected from user JohnDoe 52.52.52.52 port 41850
> 2916 19:18:03:279 Accepted password for JohnDoe from 52.52.52.52 port
> 41868 ssh2
> 1824 19:33:53:857 Received signal 8; terminating.
> 1820 19:34:06:612 Server listening on :: port 95.
> 1820 19:34:06:612 Server listening on 0.0.0.0 port 95.
> 1820 19:44:10:451 Received signal 8; terminating.
> 1848 21:02:44:275 Server listening on :: port 95.
> 1848 21:02:44:291 Server listening on 0.0.0.0 port 95.
> 3608 21:09:34:737 Accepted password for JohnDoe from 52.52.52.52 port
> 49830 ssh2
If this is a permissions issue on server, why do all other clients work
fine? For me it's clearly guacamole issue, as empty server log tells use
that SFTP requests from Guacamole *are not even reached the server*.
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1309.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Mike Jumper <mi...@guac-dev.org>.
On Fri, Jul 14, 2017 at 9:08 AM, Suncatcher16 <su...@outlook.com> wrote:
>
>> I'm not sure exactly what you're saying here. What do you mean by
>> "forward to a specific directory (not root)"?
>
> Forward to specific directory means "changing directory in built-in browser
> dir explorer". In my understanding when I specify dir in this built-in
> browser, the upload should go into this particular directory.
> For example, this picture denotes that upload will go into the root of C
> folder.
>
> <http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n1302/Sketch.png>
>
> Am i right?
>
Yes, that's correct.
>
>> but it's not clear to me which method you're using in each
>> case, and some of the specifics of the log messages don't match up
>> with what would be expected.
>
> Here is table of tests I made just now. Two sets of tests were made: w/ set
> default dir in connection and w/o. Terms:
> *Current directory* is *C:\64*. This is directory specified in the opened
> inline file browser, default upload directory in connection settings is
> empty in this case.
> *Default directory* is also */C:/64*, it is a default upload directory in
> connection settings, built-in file browser is not opened in this case.
>
> Current directory drag'n'drop:
>
>> Jul 14 16:12:00 ip-172-31-21-9 guacd[1185]: Unable to open file
>> "./file.docx"
>
> Current directory button upload:
>
>> Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to close file
>> Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to open file
>> "/C:/64/file.docx"
>
As the path is correct in these cases, there must be something else
preventing the upload from succeeding. My first guess would be
permissions, but the SSH server logs may have specifics on what is
failing.
>
> As you noticed, specifying directory gives nothing and upload goes into root
> folder anyway.
>
>> This is odd, as specifying the root
>
> So yes, this is odd for me too.
>
Is it possible that you're only using a recent build of
guacamole-client, and not guacamole-server, thus the new SFTP root
directory parameter is being ignored?
- Mike
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
> I'm not sure exactly what you're saying here. What do you mean by
> "forward to a specific directory (not root)"?
Forward to specific directory means "changing directory in built-in browser
dir explorer". In my understanding when I specify dir in this built-in
browser, the upload should go into this particular directory.
For example, this picture denotes that upload will go into the root of C
folder.
<http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n1302/Sketch.png>
Am i right?
> but it's not clear to me which method you're using in each
> case, and some of the specifics of the log messages don't match up
> with what would be expected.
Here is table of tests I made just now. Two sets of tests were made: w/ set
default dir in connection and w/o. Terms:
*Current directory* is *C:\64*. This is directory specified in the opened
inline file browser, default upload directory in connection settings is
empty in this case.
*Default directory* is also */C:/64*, it is a default upload directory in
connection settings, built-in file browser is not opened in this case.
Current directory drag'n'drop:
> Jul 14 16:12:00 ip-172-31-21-9 guacd[1185]: Unable to open file
> "./file.docx"
Current directory button upload:
> Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to close file
> Jul 14 16:13:07 ip-172-31-21-9 guacd[1185]: Unable to open file
> "/C:/64/file.docx"
Default directory drag-n-drop:
> Jul 14 16:18:16 ip-172-31-21-9 guacd[1264]: Unable to open file
> "./file.docx"
Default directory button upload:
> Jul 14 16:23:26 ip-172-31-21-9 guacd[1264]: Unable to close file
> Jul 14 16:23:26 ip-172-31-21-9 guacd[1264]: Unable to open file
> "//file.docx"
As you noticed, specifying directory gives nothing and upload goes into root
folder anyway.
> This is odd, as specifying the root
So yes, this is odd for me too.
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1302.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Mike Jumper <mi...@guac-dev.org>.
On Thu, Jul 13, 2017 at 7:48 AM, Suncatcher16 <su...@outlook.com> wrote:
>
>> When you're uploading the file, are you uploading by dragging the file
>> into
>> the browser window, or through clicking the upload button in Guacamole's
>> file browser?
>
> It doesn't work either way.
>
Understood, but it's not clear to me which method you're using in each
case, and some of the specifics of the log messages don't match up
with what would be expected.
From what you posted previously:
>
> Even when I specify */C:/Users/UserXXX* as a root folder, it gives me in
> the log
>
> *Jul 13 08:38:00 ip-172-31-21-9 guacd[21177]: Unable to open
> file "//Sketch.png"*
>
This is odd, as specifying the root folder as "/C:/Users/UserXXX"
would result in uploads via the file browser going to that directory,
or subdirectories of that directory, like
"/C:/Users/UserXXX/Sketch.png". It shouldn't be "//Sketch.png".
If uploaded via dragging the file into the window, which would use the
default upload directory (which is independent of the file browser
root), this would be possible, and it would make sense that it fails
(as "//" is no doubt non-existent).
>
> When I forward to specific directory (not root) it gives as usual
>
> *Jul 13 08:35:52 ip-172-31-21-9 guacd[21147]: Unable to open file
> "/C:/64/Sketch.png"
>
I'm not sure exactly what you're saying here. What do you mean by
"forward to a specific directory (not root)"? Is this different from
what you were doing previously when specifying a specific folder like
"/C:/Users/UserXXX" for the root?
Is the "/C:/64/" folder writable by the account being used for SFTP?
Does the SSH server list any errors in its logs when these operations fail?
Thanks,
- Mike
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
> When you're uploading the file, are you uploading by dragging the file
> into
> the browser window, or through clicking the upload button in Guacamole's
> file browser?
It doesn't work either way.
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1294.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Mike Jumper <mi...@guac-dev.org>.
When you're uploading the file, are you uploading by dragging the file into
the browser window, or through clicking the upload button in Guacamole's
file browser?
On Thu, Jul 13, 2017 at 1:22 AM, Suncatcher16 <su...@outlook.com>
wrote:
> Marko Nikolić wrote
> > Maybe it is related to
> > https://issues.apache.org/jira/plugins/servlet/mobile#
> issue/GUACAMOLE-222.
> > The file was remaining locked after download and no operation on this
> file
> > were possible any more.
>
> I download and upload different files, so it's probably not an issue.
>
>
> > Another possibility is
> > https://issues.apache.org/jira/browse/GUACAMOLE-303, which was recently
> > merged. Guacamole's SFTP implementation assumes "/" exists and is
> > listable, which is not necessarily the case, particularly on Windows.
>
> Even when I specify */C:/Users/UserXXX* as a root folder, it gives me in
> the
> log
>
> *Jul 13 08:38:00 ip-172-31-21-9 guacd[21177]: Unable to open file
> "//Sketch.png"*
>
> When I forward to specific directory (not root) it gives as usual
>
> *Jul 13 08:35:52 ip-172-31-21-9 guacd[21147]: Unable to open file
> "/C:/64/Sketch.png"
> Jul 13 08:37:41 ip-172-31-21-9 guacd[21147]: Unable to close file*
>
>
>
> --
> View this message in context: http://apache-guacamole-
> incubating-users.2363388.n4.nabble.com/SFTP-error-unable-
> to-open-file-XXX-on-Win8-RDP-host-tp1155p1289.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive
> at Nabble.com.
>
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
Marko Nikolić wrote
> Maybe it is related to
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/GUACAMOLE-222.
> The file was remaining locked after download and no operation on this file
> were possible any more.
I download and upload different files, so it's probably not an issue.
> Another possibility is
> https://issues.apache.org/jira/browse/GUACAMOLE-303, which was recently
> merged. Guacamole's SFTP implementation assumes "/" exists and is
> listable, which is not necessarily the case, particularly on Windows.
Even when I specify */C:/Users/UserXXX* as a root folder, it gives me in the
log
*Jul 13 08:38:00 ip-172-31-21-9 guacd[21177]: Unable to open file
"//Sketch.png"*
When I forward to specific directory (not root) it gives as usual
*Jul 13 08:35:52 ip-172-31-21-9 guacd[21147]: Unable to open file
"/C:/64/Sketch.png"
Jul 13 08:37:41 ip-172-31-21-9 guacd[21147]: Unable to close file*
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1289.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Mike Jumper <mi...@guac-dev.org>.
Another possibility is https://issues.apache.org/jira/browse/GUACAMOLE-303,
which was recently merged. Guacamole's SFTP implementation assumes "/"
exists and is listable, which is not necessarily the case, particularly on
Windows.
- Mike
On Jul 12, 2017 10:49, "Marko Nikolić" <ma...@gmail.com> wrote:
> Maybe it is related to https://issues.apache.org/
> jira/plugins/servlet/mobile#issue/GUACAMOLE-222. The file was remaining
> locked after download and no operation on this file were possible any more.
>
> Regards,
> Marko
>
> On Wed, 12 Jul 2017, 18:50 Suncatcher16, <su...@outlook.com> wrote:
>
>> Could anybody help? The problem is still unsolved. It affects both on Win8
>> and Win7.
>> Upload/download via linux scp goes fine, WInSCP also goes OK. The reason
>> is
>> in Guacamole.
>>
>>
>>
>> --
>> View this message in context: http://apache-guacamole-
>> incubating-users.2363388.n4.nabble.com/SFTP-error-unable-
>> to-open-file-XXX-on-Win8-RDP-host-tp1155p1280.html
>> Sent from the Apache Guacamole (incubating) - Users mailing list archive
>> at Nabble.com.
>>
>
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Marko Nikolić <ma...@gmail.com>.
Maybe it is related to
https://issues.apache.org/jira/plugins/servlet/mobile#issue/GUACAMOLE-222.
The file was remaining locked after download and no operation on this file
were possible any more.
Regards,
Marko
On Wed, 12 Jul 2017, 18:50 Suncatcher16, <su...@outlook.com> wrote:
> Could anybody help? The problem is still unsolved. It affects both on Win8
> and Win7.
> Upload/download via linux scp goes fine, WInSCP also goes OK. The reason is
> in Guacamole.
>
>
>
> --
> View this message in context:
> http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1280.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive
> at Nabble.com.
>
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
Could anybody help? The problem is still unsolved. It affects both on Win8
and Win7.
Upload/download via linux scp goes fine, WInSCP also goes OK. The reason is
in Guacamole.
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1280.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
The same error is throwing on Win7 RDP host. It looks like some
(mis)configuration of the server, when it tries to open with wrong slash
(like in Linux) or so-so.
> Unable to open file
*
> "//
*
Nobody have meet this?
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1182.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
Erik Berndt wrote
> Is the SFTP server set to allow passive or active transfers?
How to check that?
I tried WinSCP client and it both downloads and uploads files like a charm.
I investigated Passive/Active setting and wasn't able to change it, as it
stated here <https://winscp.net/forum/viewtopic.php?t=10965> , Passive
mode is relevant only for FTP, whilst SFTP connection is always *active*.
And if it is firewall issue, then WinSCP client will be blocked too. Any
other suggeestions?
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1171.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Erik Berndt <er...@superiorpaving.net>.
Is the SFTP server set to allow passive or active transfers?
Are you able to upload files or view directories with an ftp client? If
not, It may be a firewall issue on the RDP host.
On Friday, June 16, 2017, Suncatcher16 <su...@outlook.com> wrote:
> Nobody ever faced such error?
>
>
>
> --
> View this message in context:
http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1169.html
> Sent from the Apache Guacamole (incubating) - Users mailing list archive
at Nabble.com.
>
--
Erik Berndt / Systems Administrator
5551 Wellington Rd, Gainesville, VA 20155
703.631.0004 x520 (Phone) / 703.257.1725 (Fax)
http://www.superiorpaving.net
Need to open an IT support ticket?
http://FixIT.superiorpaving.net/portal or FixIT@superiorpaving.net
Re: SFTP error "unable to open file XXX" on Win8 RDP host
Posted by Suncatcher16 <su...@outlook.com>.
Nobody ever faced such error?
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/SFTP-error-unable-to-open-file-XXX-on-Win8-RDP-host-tp1155p1169.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.