# Release: 2.1.0.2 (Beta) 2024-11-29

**URL:** https://forum.duplicati.com/t/release-2-1-0-2-beta-2024-11-29/19577
**Category:** Releases
**Created:** [November 29, 2024, 1:23pm UTC](https://forum.duplicati.com/t/release-2-1-0-2-beta-2024-11-29/19577 "2024-11-29T13:23:59Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![kenkendk](https://forum.duplicati.com/user_avatar/forum.duplicati.com/kenkendk/32/5305_2.png) [@kenkendk](https://forum.duplicati.com/u/kenkendk)
#### Post date: [December 4, 2024, 7:35am UTC](https://forum.duplicati.com/t/release-2-1-0-2-beta-2024-11-29/19577/13 "2024-12-04T07:35:07Z")

</div>

> [@Sami\_Lehtinen](#):
>
> I did check the server side logs this morning when it was quiet, and it might be slightly more confusing than I thought.

I am trying to piece together exactly how this was working before.  
I _think_ the [previous FTP client was using Explicit TLS](https://learn.microsoft.com/en-us/dotnet/api/system.net.ftpwebrequest.enablessl?view=net-9.0), but the [new client is using “Auto”](https://github.com/robinrodricks/FluentFTP/wiki/FTP-Connection#important-ftp-server-settings).  
This would explain why it tries to send the username before enabling TLS.

If my assumption is correct, it should be possible to fix it by:

- Remove the `--use-ssl` flag
- Add `--ftp-encryption-mode=Explicit`

The reason why the `--use-ssl` flag must be removed, is that it will otherwise overwrite the `--ftp-encryption-mode` flag with `Auto`.

Is it possible for you to test this change? If I can get confirmation that this is working, it is a [one-line code change](https://github.com/duplicati/duplicati/pull/5736) to get the new FTP client to behave the same as before.

---

_[View the full topic](https://forum.duplicati.com/t/release-2-1-0-2-beta-2024-11-29/19577)._