FTP-Deploy-Action
FTP-Deploy-Action copied to clipboard
SamKirkland
None of the available transfter mode swork
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/[email protected]
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.
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.
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
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
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.
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)
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.
Anybody found solutions for [None of the available transfer modes work]. SamKirkland/[email protected]
just downgrade to version 4.6.6 , it works https://www.npmjs.com/package/basic-ftp/v/4.6.6
@awaidus can you post your config?
Looking at your log it appears you're still on a old version (4.3.0)
@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
one more thing it is also not recognizing " .ftp-deploy-sync-state.json " whereas this file is already there.
@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 Can you switch back to the latest version
4.3.4and try excluding files that start with.see readme for how. You also need to change yourstate-nameto 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.editorconfigand the script cannot see the.ftp-deploy-sync-state.jsonfile
Thank @SamKirkland for your muck quicker and needed answer. I have changed my config.
would it be worked ? is config is correct ?
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.
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.
@awaidus did the upload work? After the first upload it should be MUCH faster (only changes will be uploaded going forward)
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.
