remote-sync
remote-sync copied to clipboard
yongkangchen
Error: Unable to Exec
I'm receiving an error "Error: Unable to Exec" when trying to upload via SFTP.
remote-sync seems to connect and authenticate okay, then displays the Error: Unable to Exec message in red. The SFTP connection works fine in other clients like Transmit.
Strangely, I also have remote-sync working fine on the same host (WP-Engine) in another account. The settings are very similar.
Is there a way of getting a more detailed error message to try to understand what is going on? Or is this a known issue? DIdn't see reference to it. Thanks!
I have the same issue. Also using WP-Engine for hosting... using "port": 2222
If I try to use port 22 I get:
Error: Authentication failure. Available authentication methods: publickey
If I use port 2222 I get (note replace 123.123.123.123 with my WPEngine IP) :
[10:12:36 AM] Connecting: [email protected]:2222
[10:12:39 AM] Upload: /Users/chris/Sites/test.md to /test.md ...
Error: Unable to exec
To start the upload I right click on the file and choose "Upload file"
Using Atom v.1.0.0 on OSX Yosemite 10.10.3.
{
"transport": "scp",
"hostname": "123.123.123.123",
"port": 2222,
"username": "username",
"password": "mypassword",
"target": "/",
"ignore": [
".git/**"
]
}
@chrisjacob it seems that port 22 is the right port. And you should config keyfile path in .remote-sync.json according to your error msg.
So Error: Unable to exec means port wrong?
Was a fix implemented for this @yongkangchen? Or is it not a bug in the plugin?
I get this error as well although there are no extra error messages. The port is fine as other SFTP clients can connect and I've never used a key file on any of the servers we use.
Thanks
Same issue; WP-Engine, Using Port 2222; SFTP. Download works; upload leads to the error: "unable to exec"
Same exact issue with me on 2 WP Engine accounts that I own. When I plug these same settings into my FileZilla client, it works perfectly.
Same issue with WPEngine on port 2222
ScreenShot: https://www.dropbox.com/s/fwwiu89ymzgajv6/Screenshot%202016-04-14%2015.08.06.png?dl=0
Have the same issue on Windows platform using if I try to upload file.
"transport": "scp",
How can I resolve`issue?
Possible fix for this issue mscdex/ssh2#427
what does it mean? Should you release new fixed version? Should you wait until mscdex/ssh2 bug is fixed?
I have the same issue when trying to upload a file to Squarespace. Port 2030.
It authenticates correctly, but when it begins to upload I receive this error: "Error: Unable to exec"
On the flip side, I'm able to download files with no issues.
I just got off phone with WP Engine and they were not able to determine why this is failing on their end.
Does anyone have any other insight here? @patrickgilmour you mentioned that you had the remote-sync working on another WP Engine account - would you be able to provide the example settings (with username/password details removed) here so we could further diagnose?
I am setting up a support ticket with WP Engine about this and any further information would be helpful.
@derekcavaliero - Sorry! I haven 't used remote-sync for quite some time and don't have the settings file any more.
Should I close this, or leave it open for others?
I am having the same issue, but not seeing much by way of support by the authors. No problem: free and all of that.
Does anyone know of an Atom package like this that works?
@hellboy81 I actually switched from Atom to PHPStorm because of this very issue!
I think it's fairly evident that this won't be fixed by the plugin author any time soon. If you want to keep using Atom, but want remote FTP/SFTP syncing with WP Engine or port 2222, you might want to look into the new Prepros.
@v0wels I wish I knew how to close this.
It's been open since May '15. If it hasn't been fixed by then, you're right, it won't be now.
Please stop commenting on this.
