You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a directory on my web site which contains files for download ranging in size from 50,000 K to 4 MB and I access it by ftp. I have been adding files and symbolic links pointing within that directory. For instance W-TEXT.zip would point to TEXT.zip.
All was OK until recently, when all the sudden CyberDuck was not able to open 'delivery'. When I double click on it, it says :
Listing directory delivery
And the rotating symbol of activity shows it is working. After a couple minutes, an error message appears saying :
I/O Error: Connection closed without indication.
This happens in Mac OS 4.2.1 and 4.3.1.The directory contains 31 files, and 59 symbolic links.
At first I thought it was a server error, but I verified with Filezilla, and it opens reliably instantaneously. I actually had to switch to Filezilla because CyberDuck was not able to access my data.
All seems related to the way CyberDuck gets the directory listing. Hope you will be able to spot the problem and fix it.
Mitch
The text was updated successfully, but these errors were encountered:
I have a directory on my web site which contains files for download ranging in size from 50,000 K to 4 MB and I access it by ftp. I have been adding files and symbolic links pointing within that directory. For instance W-TEXT.zip would point to TEXT.zip.
All was OK until recently, when all the sudden CyberDuck was not able to open 'delivery'. When I double click on it, it says :
And the rotating symbol of activity shows it is working. After a couple minutes, an error message appears saying :
This happens in Mac OS 4.2.1 and 4.3.1.The directory contains 31 files, and 59 symbolic links.
At first I thought it was a server error, but I verified with Filezilla, and it opens reliably instantaneously. I actually had to switch to Filezilla because CyberDuck was not able to access my data.
All seems related to the way CyberDuck gets the directory listing. Hope you will be able to spot the problem and fix it.
Mitch
The text was updated successfully, but these errors were encountered: