ExpanDrive not displaying server subdomain directory content correctly
I've configured ExpanDrive for a subdomain on one of my Media Temple servers. In the ExpandDrive settings, the server and password are set. Manually browsing through the server subdomains/subname I am expecting to find an httpdocs folder but ExpanDrive only loads a conf and error_docs directory. For some reason it is not making the httpdocs folder available.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hi, Derek,
If you connect to the your Media Temple site using the same parameters (host name, password, remote path, etc.), but using the command-line "sftp" program, do you see the httpdocs folder you are expecting?
You should be able to write something like this in the Terminal:
sftp yourname@mediatemplehost.com:/remote/path/name
Once you're connected, you can type "ls" at the SFTP prompt to see what it thinks the contents of that directory might be.
-M
I’m curious
-
Inappropriate?From the Terminal the connection is immediately closed. Does this mean it is a Media Temple issue? Transmit has access.
-
Inappropriate?I can't yet tell whether it's a Media Temple issue, but one thing I forgot to ask before was: Are you connecting with SFTP, or with FTP, in ExpanDrive?
From the Terminal the connection is immediately closed. Does this mean it is a Media Temple issue? Transmit has access.
Does the connection close before you provide your password, or after? And, when it closes, does it give an error message of any kind? Perhaps you could try running the same command again, but adding the "-v" option to get verbose output---that might give you some indication of what's gone wrong. -
Inappropriate?
Are you connecting with SFTP, or with FTP, in ExpanDrive?
If I specified sFTP, ExpanDrive immediately prompted me with a message stating that the channel had been closed (after attempting to connect).
Output via Terminal after entering my password when prompted:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending subsystem: sftp
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
Transferred: sent 1744, received 1912 bytes, in 0.3 seconds
Bytes per second: sent 5312.5, received 5824.3
debug1: Exit status 1
Connection closed
-
Inappropriate?
If I specified sFTP, ExpanDrive immediately prompted me with a message stating that the channel had been closed (after attempting to connect).
So, does that mean that in the original connection, where you reported it was not showing your "httpdocs" folder correctly---you were using an FTP drive, rather than SFTP? I just want to make sure I'm correctly understanding the nature of the error. -
Inappropriate?Sorry I wasn't clear. Yes, the original request was made when attempting to connect via FTP. The only reason was because attempting to do so via sFTP was the channel closed message.
-
Inappropriate?Great, thanks! I just wanted us to be on the same page.
Can you please try running the following sequence of commands in the Terminal, and copy and paste the results into an e-mail message to <support@expandrive.com> for me?
% ftp yourlogin@your.ftphost.com
ftp> cd /remote/path/name
ftp> ls -a -l
-
Inappropriate?Thanks for your help, Derek! This will be fixed in our next release.
The company says
this answers the question
Loading Profile...


EMPLOYEE