None of the available transfer modes work #229

posbank2 · 2021-10-12T05:20:47Z

on: push
name: Deploy website on push 1
jobs:
web-deploy:
name: 🎉 Deploy
runs-on: ubuntu-latest
steps:
- name: 🚚 Get latest code
uses: actions/checkout@v2

- name: 📂 Sync files
  uses: SamKirkland/FTP-Deploy-Action@4.1.0
  with:
    server:  myhostname 
    username: username 
    password: password 
    server-dir : www/

1 set up job ok
2.Get latest code ok
3. sync files error
📁 Create: admin
➕ Upload: admin/404.html
➕ Upload: admin/blank.html
➕ Upload: admin/buttons.html
➕ Upload: admin/cards.html
➕ Upload: admin/charts.html
📁 Create: admin/ckeditor
10867 uploading "admin/404.html"

Error: None of the available transfer modes work.
at Client.prepareTransfer (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.1.0/dist/index.js:3494:19)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: Error: None of the available transfer modes work.

All firewalls allow port 21.
The file transfer is interrupted.

Its file permissions are the same as all other files.
Could a lot of files be a problem?

I keep getting an error from a specific file.

The text was updated successfully, but these errors were encountered:

posbank2 · 2021-10-13T02:11:30Z

In dry-run mode, it works fine.

emyu01 · 2021-11-13T07:47:24Z

Having same issue

manuelescrig · 2021-12-07T09:44:18Z

Same issue for me.

bertugmete · 2022-02-21T16:17:25Z

Same issue :(

emyu01 · 2022-02-21T17:46:52Z

Downgrading to v4.0.0 solved the issue for me

GaelCodes · 2022-02-21T21:19:39Z

I had the same issue, make sure ports for data channel are open.
You need to open port for command channel, but also for the range of ports that you specified to your ftp server to use when passive mode is requested.

It works for me.

kingyue737 · 2022-03-02T09:07:18Z

Same issue for me.

kingyue737 · 2022-03-02T09:38:04Z

Here is my error log:

Trying to find optimal transfer mode...
> EPSV
< 229 Entering Extended Passive Mode (|||40003|).

Transfer mode failed: "Can't open data connection in passive mode: connect ECONNREFUSED 101.37.28.143:40003", will try next.
> PASV
< 227 Entering Passive Mode(127,0,0,1,156,75).

Transfer mode failed: "Can't open data connection in passive mode: connect ECONNREFUSED 127.0.0.1:40011", will try next.

Here is the log of filezilla which can successfully transfer file with ftp server. May be the issue is related to server address?

Command:	PASV
Trace:	CFtpControlSocket::OnReceive()
Response:	227 Entering Passive Mode(127,0,0,1,156,81).
Trace:	CFtpRawTransferOpData::ParseResponse() in state 2
Status:	Server sent passive reply with unroutable address. Using server address instead.
Trace:	  Reply: 127.0.0.1, peer: 101.37.28.143

kingyue737 · 2022-03-03T09:16:57Z

I've located the issue! The problem is that 127.0.0.1 is not considered as private address:

https://github.com/patrickjuchli/basic-ftp/blob/e1acee0215bf8e39c490a470e98cdaa0898460b3/src/netUtils.ts#L55

patrickjuchli · 2022-07-17T06:26:06Z

@SamKirkland, this should be fixed with basic-ftp 5.0.0.

SamKirkland · 2022-07-22T17:15:24Z

@patrickjuchli you rock! ♥️🚀
I'll upgrade asap

mhasanmeet · 2022-07-23T18:35:22Z

Error: None of the available transfer modes work.
    at Client.prepareTransfer (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.3.0/dist/index.js:4323:19)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error: Error: None of the available transfer modes work.

This issue happens. Can you please solve the issue? Thank you so much for your contributing time, sir.

KimpShreyan · 2022-09-29T08:28:43Z

This error shows up latest version please help

Error: None of the available transfer modes work. at Client.prepareTransfer (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.3.2/dist/index.js:4803:19) at processTicksAndRejections (internal/process/task_queues.js:97:5)

harry2712 · 2022-11-11T07:37:19Z

i also get the same
Error: None of the available transfer modes work.

ibilalfaizz · 2022-12-23T07:18:41Z

Tried the latest as well as the 4.3.1v, but the issue is still there for me.
p.s: it occurs in the last 1% of the files.

DEV-BDM · 2023-01-16T08:27:39Z

Anybody found solutions for [None of the available transfer modes work]. SamKirkland/FTP-Deploy-Action@4.3.3

inventorDrizzt · 2023-01-29T15:34:55Z

just downgrade to version 4.6.6 , it works
https://www.npmjs.com/package/basic-ftp/v/4.6.6

SamKirkland · 2023-03-16T15:58:57Z

Had a bug on my side. This should be fixed in v4.3.4

awaidus · 2023-03-31T19:38:47Z

Same error:

SamKirkland · 2023-03-31T19:41:48Z

@awaidus can you post your config?

Looking at your log it appears you're still on a old version (4.3.0)

awaidus · 2023-03-31T19:43:37Z

@awaidus can you post your config?

Looking at your log it appears you're still on a old version (4.3.0)

I previously tried with 4.3.4 but still not working so I tried again with some older version as it was working fine before. but now none of any working

awaidus · 2023-03-31T19:45:35Z

one more thing it is also not recognizing " .ftp-deploy-sync-state.json " whereas this file is already there.

SamKirkland · 2023-03-31T19:47:46Z

@awaidus Can you switch back to the latest version 4.3.4 and try excluding files that start with . see readme for how. You also need to change your state-name to a file that does NOT start with . see readme for how.

What I suspect is happening: Your FTP account does not have access to special files (files that start with .) - which is why the upload fails on .editorconfig and the script cannot see the .ftp-deploy-sync-state.json file

awaidus · 2023-03-31T19:55:19Z

@awaidus Can you switch back to the latest version 4.3.4 and try excluding files that start with . see readme for how. You also need to change your state-name to a file that does NOT start with . see readme for how.

What I suspect is happening: Your FTP account does not have access to special files (files that start with .) - which is why the upload fails on .editorconfig and the script cannot see the .ftp-deploy-sync-state.json file

Thank @SamKirkland for your muck quicker and needed answer. I have changed my config.

would it be worked ? is config is correct ?

SamKirkland · 2023-03-31T19:59:48Z

state-name is relative. So no need to re-specify /public_html/laravel-app/

state-name: ftp-deploy-sync-state.json

If you make that change it should work - assuming the problem is limited FTP access.

If you want to test your config out you can add

dry-run: true

dry-run will output paths/files that WOULD be uploaded. But doesn't attempt to make the uploads. So its useful for testing what files would be excluded.

awaidus · 2023-03-31T20:19:35Z

dry-run: true

Thank you again. with your help I can manage to exclude all files staring from " . " and test the upload using dry-run. it works. but still it could not recognize ftp-deploy-sync-state.json. Well let's see what happened after upload completed as it takes a while.

SamKirkland · 2023-03-31T20:20:51Z

@awaidus state-name only works after the initial sync.

SamKirkland · 2023-03-31T22:01:24Z

@awaidus did the upload work?
After the first upload it should be MUCH faster (only changes will be uploaded going forward)

Atahar-Hossain · 2023-08-20T19:24:31Z

after completing this commit i got success message. But when i am going to cpanel there have all folders without file. That means all folders uploaded to cpanel but folders are empty. Secondly files are not uploading which are with (.) like, package.json.

theJohnCode · 2023-09-09T02:02:31Z

This is still a problem in version 4.3.4

Sharifur · 2023-10-21T14:34:50Z

same problem in version 4.3.4

presidonaycs · 2023-10-28T03:37:53Z

Same Issue with version 4.3.4 I have tried all the solutions above @SamKirkland please help

presidonaycs · 2023-10-28T04:06:16Z

The Error I get

Error: None of the available transfer modes work.
at Client.prepareTransfer (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/v4.3.0/dist/index.js:4323:19)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Client._uploadFromStream (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/v4.3.0/dist/index.js:4011:13)
at async Client._uploadLocalFile (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/v4.3.0/dist/index.js:3997:20)
Error: Error: None of the available transfer modes work.
##[debug]Node Action run completed with exit code 1
##[debug]Finishing: 📂 Sync files

presidonaycs · 2023-10-28T04:07:10Z

It works fine with dry-run, but nothing shows up on the server, not even the empty folders

Sharifur · 2023-10-28T04:08:46Z

I have solved my problem by downgrade to version 4.1.0

presidonaycs · 2023-10-28T04:44:45Z

@Sharifur I have tried that as well, I have also tried 4.0.0, 4.3.0, non worked

Sharifur · 2023-10-28T05:28:12Z

@Sharifur I have tried that as well, I have also tried 4.0.0, 4.3.0, non worked

Did you try to change your FTP host url to IP address?
example: ftp.yourftp.com to 123.123.123.123

presidonaycs · 2023-10-28T16:50:25Z

This is my current configuration

presidonaycs · 2023-10-28T16:51:05Z

@Sharifur I just tried that, still didn't work

SamKirkland mentioned this issue Aug 22, 2022

version 4.3.1 #313

Merged

SamKirkland closed this as completed in #313 Aug 22, 2022

SamKirkland changed the title ~~None of the available transfter mode swork~~ None of the available transfer modes work Aug 22, 2022

None of the available transfer modes work #229

None of the available transfer modes work #229

Comments

posbank2 commented Oct 12, 2021

posbank2 commented Oct 13, 2021

emyu01 commented Nov 13, 2021

manuelescrig commented Dec 7, 2021

bertugmete commented Feb 21, 2022

emyu01 commented Feb 21, 2022

GaelCodes commented Feb 21, 2022

kingyue737 commented Mar 2, 2022

kingyue737 commented Mar 2, 2022 • edited

kingyue737 commented Mar 3, 2022

patrickjuchli commented Jul 17, 2022

SamKirkland commented Jul 22, 2022

mhasanmeet commented Jul 23, 2022

KimpShreyan commented Sep 29, 2022 • edited

harry2712 commented Nov 11, 2022

ibilalfaizz commented Dec 23, 2022 • edited

DEV-BDM commented Jan 16, 2023

inventorDrizzt commented Jan 29, 2023 • edited

SamKirkland commented Mar 16, 2023

awaidus commented Mar 31, 2023 • edited

SamKirkland commented Mar 31, 2023

awaidus commented Mar 31, 2023

awaidus commented Mar 31, 2023

SamKirkland commented Mar 31, 2023

awaidus commented Mar 31, 2023

SamKirkland commented Mar 31, 2023

awaidus commented Mar 31, 2023

SamKirkland commented Mar 31, 2023

SamKirkland commented Mar 31, 2023

Atahar-Hossain commented Aug 20, 2023

theJohnCode commented Sep 9, 2023

Sharifur commented Oct 21, 2023

presidonaycs commented Oct 28, 2023

presidonaycs commented Oct 28, 2023

presidonaycs commented Oct 28, 2023

Sharifur commented Oct 28, 2023

presidonaycs commented Oct 28, 2023

Sharifur commented Oct 28, 2023

presidonaycs commented Oct 28, 2023

presidonaycs commented Oct 28, 2023

kingyue737 commented Mar 2, 2022 •

edited

KimpShreyan commented Sep 29, 2022 •

edited

ibilalfaizz commented Dec 23, 2022 •

edited

inventorDrizzt commented Jan 29, 2023 •

edited

awaidus commented Mar 31, 2023 •

edited