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

Error: None of the available transfer strategies work. #469

Open
sherz12r opened this issue Jun 25, 2024 · 10 comments
Open

Error: None of the available transfer strategies work. #469

sherz12r opened this issue Jun 25, 2024 · 10 comments

Comments

@sherz12r
Copy link

sherz12r commented Jun 25, 2024

name: Deploy Project on push
on:
push:
branches:
- master
jobs:
web-deploy:
name: Deploy
runs-on: ubuntu-latest
steps:
- name: Get the latest code
uses: actions/checkout@v2.3.2
- name: d
uses: SamKirkland/FTP-Deploy-Action@4.0.0
with:
server: ${{ secrets.SERVER }}
username: ${{ secrets.USER_NAME }}
password: ${{ secrets.SERVER_PASS }}
server-dir: ${{ secrets.SERVER_PATH }}/

    uploading "_temp/index.html"

Error: None of the available transfer strategies work.
at Client.prepareTransfer (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.0.0/dist/index.js:3308:19)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Client._uploadFromStream (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.0.0/dist/index.js:2997:13)
at async Client._uploadLocalFile (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.0.0/dist/index.js:2983:20)
Error: None of the available transfer strategies work.
at Client.prepareTransfer (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.0.0/dist/index.js:3308:19)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Client._uploadFromStream (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.0.0/dist/index.js:2997:13)
at async Client._uploadLocalFile (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.0.0/dist/index.js:2983:20)

Time spent hashing: 5.2 seconds
Time spent connecting to server: 213 milliseconds
Time spent deploying: 16 minutes 37.1 seconds (179 kB/second)

@sherz12r sherz12r changed the title not deploying in subfolder Error: None of the available transfer strategies work. Jun 27, 2024
@Trainax
Copy link
Contributor

Trainax commented Jun 27, 2024

Try updating actions/checkout to v4 and SamKirkland/FTP-Deploy-Action to v4.3.5 and then try running the action again

@sherz12r
Copy link
Author

thanks for replying updated then i have follwoing
Error: None of the available transfer strategies work. Last error response was 'Error: Timeout when trying to open data connection to ***:60185'.
at Client.prepareTransfer (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/v4.3.5/dist/index.js:4811:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Client._uploadFromStream (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/v4.3.5/dist/index.js:4496:13)
at async Client._uploadLocalFile (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/v4.3.5/dist/index.js:4482:20)
Error: Error: None of the available transfer strategies work. Last error response was 'Error: Timeout when trying to open data connection to ***:601

@Trainax
Copy link
Contributor

Trainax commented Jun 27, 2024

Try checking if your server needs a special port for FTP. From your original comment I assume you are using FTP on port 21 (default values), maybe your host uses a different port for FTP or only accepts FTPS connections (which need to be set in the action YML file)

@sherz12r
Copy link
Author

sherz12r commented Jun 27, 2024

i saw this is updating files but not complete please see image it giving error after uploading many folders
gitCapture
also i have 21 port active and i am accessing my account using filezilla with port 21 also

@espenjohannessen
Copy link

I'm having the same issue! Any ideas how to solve this? FTP transfers works fine through other FTP clients, but I'm getting the same errer as above when running the GitHub action!

@espenjohannessen
Copy link

Just as I posted this I realized that the issue was related to passive FTP mode and adding the passive ports (49152-65534) to the server firewall solved the issue!

@RayhanulSumon
Copy link

Does anyone get a solution?

@Oscar-T24
Copy link

I get the same error. Perhaps FTP-Deploy-Action assumes your server is running in passive mode ? This is obviously not the case on my server and I don't understand why Github action is using "high" ports like 601 while I expect a specific port. Additionaly my router has not forwarded these ports to my server hence why I get timeouts.

Any help will be greatly appreciated.

@kompasstech
Copy link

Check your Firewall, Creating Problems in Almalinux. Same Time-out error. Once disable the Firewall it Works

@mhimon
Copy link

mhimon commented Sep 19, 2024

Facing same issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants