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
Trying to connect to a folder made read+write available to me by a friend in his web.de account, I have different reactions from CyberDuck 7.10.2 and from MountainDuck 4.7.2
I probably should say, that I have absolutely no problem in using the browser interface for logging in, uploading and downloading files and folders. (See screenshot «Safari interface → no problems.png»
In CyberDuck I get an error message when trying to connect to the web.de server. (See the two screenshots starting with «CyberDuck…»)
On the other hand, in MountainDuck I am led to believe that a the folder «Isaiah Berlin» in uploaded, but other users of the same common folder assure me that the sid folder is not there. (See the two screenshots starting with «MountainDuck…»)
Both for CyberDuck and for MountainDuck I use port 80
What do you think, might be the problem?
Thank you
Trying to connect to a folder made read+write available to me by a friend in his web.de account, I have different reactions from CyberDuck 7.10.2 and from MountainDuck 4.7.2
I probably should say, that I have absolutely no problem in using the browser interface for logging in, uploading and downloading files and folders. (See screenshot «Safari interface → no problems.png»
In CyberDuck I get an error message when trying to connect to the web.de server. (See the two screenshots starting with «CyberDuck…»)
On the other hand, in MountainDuck I am led to believe that a the folder «Isaiah Berlin» in uploaded, but other users of the same common folder assure me that the sid folder is not there. (See the two screenshots starting with «MountainDuck…»)
Both for CyberDuck and for MountainDuck I use port 80
What do you think, might be the problem?
Thank you
Attachments
CyberDuck 2021-09-24 fields.png
(158.1 KiB){Mountain+Cyber}Duck-screenshots.zip
(681.5 KiB)The text was updated successfully, but these errors were encountered: