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 upload files to a remote HD where I have an allocated storage space. Cyberduck tells me: Authentifiaction as…, Upload of…, Authentifiacation as…, upload of…, and this is repeated until I read "failed connexion".
Using Filezilla, I have a similar "perpetual retry" with a supplementary message that tells me that the allocated disk space is full. This warning message is received from the remote FTP server because it is written in German and the remote HD is in Germany.
The text was updated successfully, but these errors were encountered:
I am not sufficiently "OSX fluent" to follow these intructions!
In the meantime, the owner of the remote HD has extended my working space, and I am again allowed to upload. Consequently, I cannot reproduce the "error" . I confess that the "problem" was not clearly stated in my description. I saw successive and repetitive "reactions of Cyberduck" without any explanation ("disk full" or "allocated storage space full"). Only Filezilla told me what happened, and I have thus contatcted the person in charge of the remote HD.
I beleive that you should detect this "allocated storage space full" and just send a warning to the user of Cyberduck as Filezilla does. You cannot do more!!!
If I can/should give more details, please tell me how… I am 70 years old, i.e., of the time of Fortran coding…
I upload files to a remote HD where I have an allocated storage space. Cyberduck tells me: Authentifiaction as…, Upload of…, Authentifiacation as…, upload of…, and this is repeated until I read "failed connexion".
Using Filezilla, I have a similar "perpetual retry" with a supplementary message that tells me that the allocated disk space is full. This warning message is received from the remote FTP server because it is written in German and the remote HD is in Germany.
The text was updated successfully, but these errors were encountered: