FTP volumes won't mount!
After I add the FTP drive settings, I click connect, it turns yellow then green, the after 3 seconds, the status light disappears... And its not mounted anywhere.
8
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?This used to happen to me too but now all I'm getting is a 'could not connect' message and 'bad packet length 842149933, 2'
I’m confused
-
Inappropriate?Stavros -
That problem is generally when you're in SFTP mode intead of FTP/FTPS mode.
-Jeff -
Well, I am in FTP/FTPS mode and have exactly the same problem. Is there a way to enable some logging to see what is going on? -
Interested in doing an iChat screensharing session to demonstrate the problem? -
Sure, let me stop Adium and start iChat -
So, how do I contact you? -
Did y'all make any progress debugging this yesterday? -
Not really, but there is a SW update coming out soon, I was told. -
Inappropriate?Actually, I'm not getting as far as a green light. About all I see is a flash of yellow, then ... nothing.
I’m sad
-
Inappropriate?Same thing here - though only on some ftp-servers.
-
Inappropriate?We have a known problem with some configurations when there is an FTP-aware firewall between you and the server. The symptoms are the same as you are describing. If that does turn out to be your problem, I'm pleased to report it will be fixed by our next update.
-
Inappropriate?We just released 1.3.1 which addresses a lot of the FTP compatibility issues people were seeing. Give it a spin and let us k now how it goes.
-
Inappropriate?Great - fixed it for me!
However, people should know that the failed attempts left invisible directories named "ftp server", "ftp server 1", "ftp server 2", etc in the /Volumes folder which should be deleted using the terminal.
Otherwise the successful attempt will mount as "ftp server 6" or however many times you tried before.
Thanks for the quick fix, again! -
This issue with the additional directories is indeed troubling. Not only is the ftp still not working for me (some python issue), but now I have empty (mountpoint) directories for every entry in ExpanDrive for every time I started it ... -
Inappropriate?Yeah, verily, I have tasted of the FTP begat by ExpanDrive and I have wept for joy.
I’m enjoy-lated
-
Inappropriate?I'm running the 1.3.1 upgrade, and still getting the "blink... oh no wait.. that didn't work" thing. Trying both an ftp and an sftp connection. I can however connect straight through with Transmit or via browser. One thing which might help - I vaguely seem to recall something about using passive mode in Transmit...
Is there some log somewhere that I could be checking?
I’m sad
-
Inappropriate?Richard - Sorry you're having trouble!
I'm surprised you cannot access FTP or SFTP. Our FTP support is brand new, and there are some likely incompatibilities, but SFTP has been around and kicking for a while.
Could you check Console.app to see if anything interesting is being logged by ExpanDrive? -
I think I have figured out the problem for me :) - in looking at the console log I see ExpanDrive manipulating the userid it uses to signon - I am using Yahoo Hosting so my signon needs to be exactly what I put for the userid - if the site is ftp.xxx.com then either it needs to allow just the name I use (marvin) or allow me to enter the full name as marvin@xxx.com not use marvin@ftp.xxx.com - the error I get in the log isn't much help though - it's:
EXPANDRIVE_AUTH_PASSWORD:marvin^citycomber.com@ftp.citycomber.com
2008-10-16 17:56:57.232 ExpanDrive[1420] EXPANDRIVE_CONNECT_FAILURE:
2008-10-16 17:56:57.233 ExpanDrive[1420] Couldn't connect because
the time I tried to use marvin@citycomber.com - since normally a ftp client allows you to enter the full name yourself - notice y'all changed the @ to the ^ -
Inappropriate?See if this helps -
16/10/2008 22:49:32 ExpanDrive[158] EXPANDRIVE_AUTH_PASSWORD:u35107196@dyce.com
16/10/2008 22:49:32 ExpanDrive[158] EXPANDRIVE_CONNECT_PROGRESS:drive_connected
16/10/2008 22:49:32 ExpanDrive[158] EXPANDRIVE_MKDIR_MOUNTPOINT:/Volumes/motoproj 3
16/10/2008 22:49:32 ExpanDrive[158] Traceback (most recent call last):
16/10/2008 22:49:32 ExpanDrive[158] File "/expandrive/fs/ftpfs/Driver.py", line 257, in <module>
16/10/2008 22:49:32 ExpanDrive[158] File "/expandrive/fs/ftpfs/Driver.py", line 243, in main
File "/expandrive/fs/ftpfs/Driver.py", line 211, in start_ftpfs
File "/expandrive/fs/fstools/fuse.py", line 372, in __init__
File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 353, in __getattr__
File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 358, in __getitem__
AttributeError: dlsym(RTLD_DEFAULT, fuse_main_real): symbol not found
</module>
Seems like something awry with the fuse driver thingambob?
I’m puzzled
-
Inappropriate?Could you give the output for SFTP too?
thanks -
Any ideas yet? -
Inappropriate?Here's both together, one after the other...
16/10/2008 23:06:50 ExpanDrive[133] File "/expandrive/fs/ftpfs/Driver.py", line 257, in <module>
File "/expandrive/fs/ftpfs/Driver.py", line 243, in main
File "/expandrive/fs/ftpfs/Driver.py", line 211, in start_ftpfs
File "/expandrive/fs/fstools/fuse.py", line 372, in __init__
File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 353, in __getattr__
16/10/2008 23:06:50 ExpanDrive[133] File "/expandrive/python2.5.1/lib/python2.5/ctypes/__init__.py", line 358, in __getitem__
AttributeError: dlsym(RTLD_DEFAULT, fuse_main_real): symbol not found
16/10/2008 23:06:56 ExpanDrive[133] Traceback (most recent call last):
16/10/2008 23:06:56 ExpanDrive[133] File "/expandrive/ExpanDrive.py", line 9, in </module><module>
File "/expandrive/pyfuse/fuse.py", line 26, in </module><module>
ImportError: dlopen(/Applications/ExpanDrive.app/Contents/ExpanDrive/pyfuse/fuseparts/_fusemodule.so, 2): Library not loaded: /usr/local/lib/libfuse.0.dylib
Referenced from: /Applications/ExpanDrive.app/Contents/ExpanDrive/pyfuse/fuseparts/_fusemodule.so
Reason: image not found
</module>
Hope that helps -
Inappropriate?CityComber: The message you see after the label "EXPANDRIVE_AUTH_PASSWORD" is constructed merely for the purpose of prompting the human at the controls. The actual username sent to the FTP server is literally what you typed into the Username field in the New Drive window. So, if you entered "marvin^citycomber.com" that's what gets sent as the user name.
-
Thanks M.J. but it is changing my entry as noted in these messages:
2008-10-16 22:14:38.769 ExpanDrive[1420] EXPANDRIVE_AUTH_PASSWORD:marvin^citycomber.com@ftp.citycomber.com
2008-10-16 22:14:39.201 ExpanDrive[1420] EXPANDRIVE_CONNECT_FAILURE:
2008-10-16 22:14:39.202 ExpanDrive[1420] Couldn't connect because
I typed in marvin@citycomber.com & it changed the @ to ^ & appended the ftp.citycomber.com on its own! -
Inappropriate?CityComber: As I said before, the "@ftp.citycomber.com" is only shown in that message for the purpose of prompting you for the password---it's not sent to the server. However, if you didn't type in the ^ the first time, then that's something we have to look at!
-
Inappropriate?Hi,
Have tried the 1.3.2b3 update. Still no joy. I know that the connection details are ok, as Transmit works fine. Latest console for sftp connection gives:
29/10/2008 16:36:29 ExpanDrive[1502] Traceback (most recent call last):
29/10/2008 16:36:29 ExpanDrive[1502] File "/expandrive/ExpanDrive.py", line 9, in <module>
29/10/2008 16:36:29 ExpanDrive[1502] File "/expandrive/pyfuse/fuse.py", lin
Loading Profile...






EMPLOYEE


EMPLOYEE
