scp-action
scp-action copied to clipboard
appleboy
error copy file to dest: ***, error message: dial tcp *** i/o timeout
I have been using this actions in one of my projects. So far it works fine, but sometimes I get the following error:
tar all files into /tmp/979006019/KQmgptshHs.tar
scp file to server.
2021/03/19 12:52:01 error copy file to dest: ***, error message: dial tcp **.**.**.**:***: i/o timeout
drone-scp error: error copy file to dest: ***, error message: dial tcp **.**.**.**:***: i/o timeout
@Pumpk1ns check with your cloud provider if the ssh port (22) is released for everyone to access, after I make these releases my pipeline ran successfully
Same here, but with remove old .tar
tar all files into /tmp/861092316/wuXwBu8u8s.tar
scp file to server.
create folder .
untar file wuXwBu8u8s.tar
remove file wuXwBu8u8s.tar
drone-scp error: dial tcp ***.***.***.***:22: i/o timeout
drone-scp rollback: remove all target tmp file
remove file wuXwBu8u8s.tar
dial tcp ***.***.***.***:22: i/o timeout
So it's able to upload file but unable to delete .tar.
I switched to another scp action and everything was fine, until I started to make several consecutive requests - then it started to fail after a couple of tries. Perhaps the problem is that my remote server is hosted on the smallest DigitalOcean droplet and it cannot handle such "intentional" request rate. After reducing count of requests to one, everything started working flawlessly.
I received this issue when I was sending a file and listing the file name (with file extensions) in the target option, assuming it would land in the home directory of the user.
I changed it to ~/ and the issue went away.
Unfortunately, the same error.
UPD: when I had changed host and port without secrets - action was successful
Hey I am getting this same issue right now and tried all of your guys work arounds aside from @ZhillinS recommendation to reduce the count of requests. Would you be able to walk me through how to do that on my droplet? I have the same configuration (smallest droplet DO offers)
I am getting the same error. i want to deploy my artifact into a Azure window VM.
Is "appleboy/scp-action@master" only for Linux VM?
Can somebody help me here?
Can happen if your host has an ipv6 and your firewall only allow ipv4
Had the same issue.
My solution was to change the firewall rule(ufw) for my ssh port from LIMIT to ALLOW
In my case it was that I was connecting to the wrong port, changing from 722 to 22 solved the issue.
As of now, you can use version 0.1.3
appleboy/[email protected]
instead
appleboy/scp-action@master
It's working fine with me instead of master branch
As of now, you can use version 0.1.3
appleboy/[email protected]instead
appleboy/scp-action@masterIt's working fine with me instead of master branch
Thankyou bro!
I think I was able to find a way around it.
Firstly: The default timeout for ssh to remote host is 30 seconds, you can try increasing it to probably 120 seconds. you can do this by simply defining the timeout input as 120 as shown below:
for more info on the possible inputs you can edit or change check https://github.com/appleboy/scp-action/blob/master/action.yml
That should work, well, hopefully it worked well for me.
I noticed an issue though, even though everything worked fine, somehow the 'tar.gz' files still remained. I did a simple work around in my yaml file as shown below:
Please Note: I only did this after confirming that no other tar .gz files exist in my target directory.
I hope this helps.
As of now, you can use version 0.1.3
appleboy/[email protected]instead
appleboy/scp-action@masterIt's working fine with me instead of master branch
This is the solutions, a lot of thanks!
At the end I have got to work it fine in an aws instance
The solution is to fix the rules of ufw
#sudo ufw allow 22
In an aws instance the solution is to open port 22
#sudo ufw allow 22