Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

FTPError: 553 Can't open that file: No such file or directory

See original GitHub issue

Bug Description I’m getting error 553 when updating the repository.

In the first synchronization the action worked perfectly, but when updating any file the second action returns the error.

My Action Config

on: 
  push: 
    branches:
      - main
name: 🚀 Deploy website on push
jobs:
  web-deploy:
    name: 🎉 Deploy
    runs-on: ubuntu-latest
    steps:
    - name: 🚚 Get latest code
      uses: actions/checkout@v2
      
    - name: 🚚 Install Composer Dependencies SITE
      working-directory: ./
      run: composer install --prefer-dist
    
    - name: 🚚 Install Composer Dependencies ADM
      working-directory: ./public/adm
      run: composer install --prefer-dist
            
    - name: 📂 Sync files
      uses: SamKirkland/FTP-Deploy-Action@4.2.0
      with:
        server: ${{ secrets.ftp_host}}
        username: ${{ secrets.ftp_user }}
        password: ${{ secrets.ftp_password }}
        exclude: |
          .git/**
          .git**
          .git*/**
          **/.git*
          **/.git*/**
          **/node_modules/**
          fileToExclude.txt

My Action Log

   Making changes to 2346 files/folders to sync server state
Uploading: 0 B -- Deleting: 16.2 MB -- Replacing: 434 kB
----------------------------------------------------------------
replacing "app/Config/App.php"
replacing "app/Config/Constants.php"
replacing "app/Views/client/templates/mdb/components/navbar.html"
replacing "app/Views/client/templates/mdb/components/post.html"
replacing "public/adm/composer.lock"
replacing "public/adm/vendor/autoload.php"

----------------------------------------------------------------
--------------  🔥🔥🔥 an error occurred  🔥🔥🔥  --------------
----------------------------------------------------------------

----------------------------------------------------------------
----------------------  full error below  ----------------------
----------------------------------------------------------------

FTPError: 553 Can't open that file: No such file or directory
    at FTPContext._onControlSocketData (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.2.0/dist/index.js:4744:39)
    at Socket.<anonymous> (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.2.0/dist/index.js:4585:44)
    at Socket.emit (events.js:210:5)
    at addChunk (_stream_readable.js:309:12)
    at readableAddChunk (_stream_readable.js:286:13)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:182:23) {
  name: 'FTPError',
  code: 553
}
Error: FTPError: 553 Can't open that file: No such file or directory

Issue Analytics

State:
Created 2 years ago
Comments:13

Top GitHub Comments

10reactions

mikedelgaudiocommented, Feb 8, 2022

Same issue, my not-so-ideal solution was to delete the .ftp-deploy-sync-state.json off the FTP server. The downside is uploading everything fresh again.

1reaction

marcos-queirozcommented, Mar 3, 2022

Se o push para o ftp que você fez anteriormente envolveu a remoção de arquivos/caminhos, parece que o próximo push para o ftp que você executar gerará esse erro. O Git parece exigir que os placeholders mantenham a estrutura de pastas, uma vez que esses placeholders desaparecem, assim como suas pastas pai, desde que sejam o único item nela. O script não sabe como lidar com esse comportamento, pois retém as informações completas do caminho que o git remove automaticamente.

that seems to be the problem.

If you remove a directory on the host or file this error occurs.

I deleted the entire directory and the new puhs worked fine.