rclone / rclone/rclone

Rclone doesn't close FTP connection when copy is completed

Open
#9,215 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
59.8k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

The associated forum post URL from https://forum.rclone.org
What is the problem you are having with rclone?

Rclone seems to not close the connection when is serving FTP, my client keeps the transfer window open for a few seconds after the transfer is completed and then says: CloseFile NO FD_CLOSE Response from Server

What is your rclone version (output from rclone version)

1.73.1

Which OS you are using and how many bits (e.g. Windows 7, 64 bit)

Windows 10, 64 bits

Which cloud storage system are you using? (e.g. Google Drive)

WebDAV

The command you were trying to run (e.g. rclone copy /tmp remote:tmp)

rclone serve ftp cardinal:

A log from the command with the -vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)

2026/02/25 14:51:31 DEBUG : rclone: Version "v1.71.1" starting with parameters ["rclone" "serve" "ftp" "cardinal:" "-vv"]
2026/02/25 14:51:31 DEBUG : Creating backend with remote "cardinal:"
2026/02/25 14:51:31 DEBUG : Using config file from "C:\Users\Neto\AppData\Roaming\rclone\rclone.conf"
2026/02/25 14:51:31 DEBUG : found headers:
2026/02/25 14:51:31 INFO : webdav root '': poll-interval is not supported by this remote
2026/02/25 14:51:31 NOTICE: webdav root '': --vfs-cache-mode writes or full is recommended for this remote as it can't stream
2026/02/25 14:51:31 NOTICE: webdav root '': Serving FTP on localhost:2121
2026/02/25 14:51:31 INFO : : Rclone FTP Server listening on 2121

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue through the rclone serve ftp entry point using the WebDAV remote and the client behavior described in the report. Trace the FTP transfer completion and connection-close path; done means the server closes the connection promptly after copying without the client's FD_CLOSE error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.