Error: FTPError: 550 Remove directory operation failed. #220
Comments
|
I have fixed this issue in this fork, if you want to test this out. |
|
i guess action is using yours @Penguibird, but still same error msg... Run Penguibird/FTP-Deploy-Action@4.2.1🚀 Thanks for using ftp-deploy. Let's deploy some stuff!removing folder "just_engine/lib/temp/" -------------- 🔥🔥🔥 an error occurred 🔥🔥🔥 ------------------------------------ full error below ----------------------FTPError: 550 Directory not found |
|
i have the same issue ? |
|
I also have the same issue (failed to remove empty folders after removing all their contents). Also, it seems that in the case it aborts without writing the new (partial) sync state to the server, which seems to be dangerous. |
|
i have the same issue ? |
Me too, hope this will be fixed soon |
|
I also encountered this problem when I renamed a folder and committed the changes. The file structure was like this: When I gave the main_folder a new name, a new folder with the same contents but the new name was created on the server. After this the files inside the subfolders of the main_folder were deleted and then the subfolders themselves were also deleted. When it came time to delete the main_folder from the server, error 550 happened. I fixed this error by connecting to the server using FileZilla FTP Client, manually deleting that folder and also the |
|
hello @Trainax, sorry if it's a dumb question, but i don't get it: How do you manage to do a 'new complete sync'? I was re-running the action but i'm getting the same response. And also, what is this 'sync state json' you told in your answer? |
Inside the directory on the server where this action syncs the files to you can find a file called If you connect to the server using an FTP client and delete this file, when you run again this action all the files in the repo will be synced again to the server even if they have not been modified |
|
Since it doesn't fix yet, use version 4.0.0 instead of 4.1.0. |
|
It looks like there has been a commit which fixes this and marked as 4.2.0 beta, but no release as of yet. Does anyone know if it's possible to use this? |
|
Does this actually fix the issue?
…On Wed, Oct 20, 2021, 11:14 Gav Richards ***@***.***> wrote:
It looks like there has been a commit which fixes this
<ba86a1b>
and marked as 4.2.0 beta, but no release as of yet. Does anyone know if
it's possible to use this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#220 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALZ5QFJA6CFEGTFJBQ2ODILUH2I73ANCNFSM5CLHVNPA>
.
|
Thanks for this, downgrading to lower versions works. |
|
Still not OK in 4.2.0. See shot below. Created a testfile.txt in a testfolder and removed the folder afterwards:
@SamKirkland Are you able to replicate this? PS: The file gets removed, but the remaining empty folder doesn't. // T |
In version 4.0.0 files get removed, folder remains but doesn't throw a 550 error. So it's still an issue. |
Which version? |
Version 4.0.0 |
|
@ApplecakeYT Version 4.0.0 fails silently, see my reply above: #220 (comment) |
|
I really wish this was fixed, it's such a pain in the ass when you do a big deployment, and then near the end it fails because some directories were deleted, so you then have to redeploy the entire repo to get the "sync state" file up to date. |
I am aware, although thanks for pointing it out. I should have mentioned that it only hides the error rather than actually fixing it. |
|
I had a similar error today. One issue is that removal should happen in reverse order. In my case it tried to do this:
And because
What the action should do is remove in deep-first order:
|
|
Hello,
Hope that this can help :) |
|
After long searching, now in Jan/2022 I arrived at conclusion that unfortunatelly this issue still has no solution as should be, but I will follow a short routine which does the trick: |
|
Apparently it's an FTP user permission error. To test, use FileZilla (for example), login with the same login/password and try to create a folder through filezilla. Check for a permission error. |
|
I've pushed uses: SamKirkland/FTP-Deploy-Action@v4.3.0-betaPlease follow up with a comment letting me know if the issue has been resolved. Note: Once I deploy the actual |
|
@SamKirkland Fix works here. I performed the following:
👍🏻 |
|
@SamKirkland Yes, I can confirm too, removing directory works for @v4.3.0-beta 👏 |
Upgrade FTP-Deploy-Action version to fix the build error. See SamKirkland/FTP-Deploy-Action#220
Upgrade FTP-Deploy-Action to fix error when deploying book to FTP server. See SamKirkland/FTP-Deploy-Action#220
|
@SamKirkland Didn't have a chance to test this until now. Wanted to say thanks much. The latest update v4.3.0 works like a charm. |
|
I slove this using |
|
O solve this excluding the folder error like: I hope I've helped! |
|
For me the problem was that my cPanel hosting doesn't allow foreign FTP connections by default and I had to allow it manually. |
Same thing - helped me to just change version and error "Can't delete file or folder" was lost. Thank you! |
|
I just got this on 4.3.0 😞 If it helps: |
The issue still exists 😞Bug DescriptionMy result is similar for the followings: Here you wrote that you fixed the issue in the 4.3.0-beta version. But the latest version(4.3.4)still has the issue. My Action Configname: 🚀 Deploy Site to cPanel
on:
push:
branches:
- main
permissions:
contents: read
jobs:
FTP-Deploy-Action:
name: 🎉 Deploy
runs-on: ubuntu-latest
steps:
- name: 🚚 Get the latest code
uses: actions/checkout@v3
with:
fetch-depth: 2
- name: Use Node.js 16
uses: actions/setup-node@v3
with:
node-version: '16'
- name: Cache npm dependencies
uses: actions/cache@v3
id: cache-node-modules
with:
path: '**/node_modules'
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
- name: 🔨 Install Dependencies
if: steps.npm-cache.outputs.cache-hit != 'true'
run: |
npm install
npm prune
npm run build --if-present
git reset --hard
- name: 📂 Sync folders and files to the server
uses: SamKirkland/FTP-Deploy-Action@v4.3.4
with:
server: ${{ secrets.FTP_SERVER }}
username: ${{ secrets.FTP_USERNAME }}
password: ${{ secrets.FTP_PASSWORD }}My Action Log |
|
I had the same issue even though less than 6 months ago it was working perfectly. I tried everything and nothing worked. At the end the problem was with the permissions of the user I was using. After I gave the user all the permissions it worked perfectly. |
absolute yes. thanks! |
How can I gave a permission for the user?? |
|
Thanks for this. Please try to do it for the Laravel project. :) When I push my project, '.env' file replace automatically again and again. |
|
I found a solution to the problem that might help. This apparently happens because it exceeds the open and inactive connection timeout. Same error in a C# library: https://www.chilkatsoft.com/p/p_462.asp The solution I found was to increase the "timeout" to 2 minutes: timeout: 120000. |
and others
FTPError: 550 Remove directory operation failed.
at FTPContext._onControlSocketData (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.1.0/dist/index.js:3945:39)
at Socket. (/home/runner/work/_actions/SamKirkland/FTP-Deploy-Action/4.1.0/dist/index.js:3786: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: 550
}
Error: FTPError: 550 Remove directory operation failed.
The text was updated successfully, but these errors were encountered: