Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot create archive - returns "Connection failed" dialog box that reads "Request failed." #11034

cyberduck opened this issue Apr 23, 2020 · 2 comments


Copy link

@cyberduck cyberduck commented Apr 23, 2020

cdf6f90 created the issue

First off, I can't give you a transcript from View → Toggle Log Drawer because that option doesn't exist in my version of Cyberduck. In fact, according to the log drawer was discontinued in 2006. More than fourteen years ago.

But I can tell you what my issue is!

What I'm trying to do:

  • Create an archive of a file on the server.

What happens:

  • It returns a "Connection failed" dialog box that reads "Request failed."
  • It shows a spinning wheel of death next to the command on the bottom line.

Before you ask:

  • Yes I'm logged in SFTP / SSH.
  • Yes my server has a zip executable, at /usr/bin/zip

What I think might be the problem: Take a look at the command that Cyberduck sends to my server:
"cd /; zip -qr / wp-login.php"

I'm just an amateur when it comes to this kind of stuff, but I did notice that the command does not escape the period between "" ... could that be the issue?

Or is it something else? What's going on?


Copy link
Collaborator Author

@cyberduck cyberduck commented May 22, 2020

@dkocher commented

I cannot reproduce the problem. Can you execute the command manually in a SSH terminal session or using Go → Send Command… to see if it works there.


@cyberduck cyberduck closed this May 22, 2020
Copy link
Collaborator Author

@cyberduck cyberduck commented May 22, 2020

cdf6f90 commented

Thanks for looking into this, I was just about to come back and close this ticket myself.

Turns out the issue was my web hosting service. They wouldn't let me SSH into the server, and told me there was no way to archive files using their file manager. Which was crazy because I have a WordPress plugin that backs up my website, and I could see right there in its logs that it found a zip executable in /usr/bin/zip and was using it just fine. The tech support folks with the hosting service said I had to write a .sh script and run it with a cron job to zip or unzip anything, but it didn't work. So I spent half an hour scheduling cron jobs and never got that avenue to function.

In the end I deployed my own VPS and canceled my account with the hosting service. Now I'm my own server admin!

Cyberduck works perfectly now — it archives / unarchives functionally. But of course now I can just SSH into the server to archive anything I want from the command line.

I'm never using shared hosting again.

Long story short: if any other Cyberduck users run into this issue it's probably a problem with their hosting service.


@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants