FTP-Deploy-Action icon indicating copy to clipboard operation
FTP-Deploy-Action copied to clipboard

Error: None of the available transfer strategies work.

Open sherz12r opened this issue 1 year ago • 10 comments

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/[email protected] - name: d uses: SamKirkland/[email protected] 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 avatar Jun 25 '24 14:06 sherz12r

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

Trainax avatar Jun 27 '24 09:06 Trainax

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

sherz12r avatar Jun 27 '24 10:06 sherz12r

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)

Trainax avatar Jun 27 '24 10:06 Trainax

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

sherz12r avatar Jun 27 '24 12:06 sherz12r

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 avatar Jun 30 '24 15:06 espenjohannessen

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!

espenjohannessen avatar Jun 30 '24 16:06 espenjohannessen

Does anyone get a solution?

RayhanulSumon avatar Jul 07 '24 10:07 RayhanulSumon

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.

Oscar-T24 avatar Aug 03 '24 16:08 Oscar-T24

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

kompasstech avatar Sep 17 '24 10:09 kompasstech

Facing same issue!

mhimon avatar Sep 19 '24 08:09 mhimon