Ftp over tls is not enabled users cannot securely log in как исправить

Thanks for the reply, I enabled FTP over TLS it gave me an error soon as I tried to click the ok button.

After enabling it, you need to create or import a certificate and private key pair. Generating the cert with FileZilla Server will put both cert and key into the same file, so the path to «Private key file» and «Certificate file» is the same. For importing a certificate (e. g. from a CA) it must be in PEM format.

N00b guide:
1. Press «Generate new certificate…» button.
2. Pick a key size (the higher the better, 2048 or above recommended).
3. Fill in the information. For a self-created cert it doesn’t need to be authentic, just don’t have blank entries there (I had problems in the past with such certificates).
4. Pick a path to a location where you want the certificate/key saved. Use a path where you’ve got write access or there will be an error.
6. Press Generate.
7. Wait.
8. The paths should have been filled in for you. Password is blank.
9. Press OK to save the settings.

I followed your link to that page and read down to the «Malicious routers, firewalls and data sabotage» part I dont see how this applies to the error I am receiving can you narrow it down, give me a hint, I haven’t the slightest clue the answer could probably beat me over the head and I still would not realize its the answer, I need the ‘for dummies’ help lol.

You need to do what the «Configuring server for Passive mode» chapter tells you.

— Defining a port range for Passive data connections in the Passive settings for FZ Server. The listening port(s) alone don’t work.
— Open that port range in all firewalls you might have. Hopefully it’s just one. The range is TCP only.
— Forward that port range in your router, along with the listening ports.

Test the server using our https://ftptest.net Enrichment Cen… err, testing facility. Plain FTP is testing without TLS, and Explicit with TLS. There are often differences, with the bad routers you read about in the guide.

FileZilla Forums

Welcome to the official discussion forums for FileZilla

Error: Server refused FTP over TLS

Error: Server refused FTP over TLS

#1 Post by oliflorence » 2015-11-25 22:48

Hello,
I have installed Filezilla server on a computer at home to FTP some files to it. I had this before but had to reset windows.
i have the router with port mapping and getting all ok on canyouseeme.org.

When trying to transfer files i am getting an error. When opening Filezilla I am getting «You appear to be behind a NAT router. Please configure the passive mode settings and forward a range of ports in your router. Warning: FTP over TLS is not enabled, users cannot securely log in.».
I have the correct IP for the machine on the router and here is the result i am getting from ftptest.net:

Status: Resolving address of xx.xx.xx.xx
Status: Connecting to xx.xx.xx.xx
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message.
Reply: 220-FileZilla Server 0.9.53 beta
Reply: 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
Reply: 220 Please visit https://filezilla-project.org/
Command: CLNT https://ftptest.net on behalf of xx.xx.xx.xx
Reply: 200 Don’t care
Command: AUTH TLS
Reply: 502 Explicit TLS authentication not allowed
Warning: Server refused AUTH TLS, trying deprecated AUTH SSL fallback.
Command: AUTH SSL
Reply: 502 Explicit TLS authentication not allowed
Error: Server refused FTP over TLS

Is there a setting i have wrong on FileZilla?

Источник

FileZilla Forums

Welcome to the official discussion forums for FileZilla

Can someone define this error?

Can someone define this error?

#1 Post by Rustyftp » 2015-11-19 19:55

I am getting the following error
Warning: FTP over TLS is not enabled, users cannot securely log in.

I searched this site and the web in general for this exact error and everything I read seems different before I spend hours reading I would like to find out how this error applies to my installation so I can refine my search to be more specific.

I also get this error above the other error I am not sure if they are related to each other?
You appear to be behind a NAT router. Please configure the passive mode settings and forward a range of ports in your router.

I have forwarded the port 21 in the router so am not sure why its still giving the error, tried to connect to the FTP and it does not connect it just times out.

Thanks in advance.

Re: Can someone define this error?

#2 Post by botg » 2015-11-19 23:02

You can enable FTP over TLS in the settings dialog.

As for the NAT warning, please study the Network Configuration guide.

Re: Can someone define this error?

#3 Post by Rustyftp » 2015-11-20 01:32

botg wrote: You can enable FTP over TLS in the settings dialog.

As for the NAT warning, please study the Network Configuration guide.

I followed your link to that page and read down to the «Malicious routers, firewalls and data sabotage» part I dont see how this applies to the error I am receiving can you narrow it down, give me a hint, I haven’t the slightest clue the answer could probably beat me over the head and I still would not realize its the answer, I need the ‘for dummies’ help lol.

Re: Can someone define this error?

#4 Post by boco » 2015-11-20 07:16

After enabling it, you need to create or import a certificate and private key pair. Generating the cert with FileZilla Server will put both cert and key into the same file, so the path to «Private key file» and «Certificate file» is the same. For importing a certificate (e. g. from a CA) it must be in PEM format.

N00b guide:
1. Press «Generate new certificate. » button.
2. Pick a key size (the higher the better, 2048 or above recommended).
3. Fill in the information. For a self-created cert it doesn’t need to be authentic, just don’t have blank entries there (I had problems in the past with such certificates).
4. Pick a path to a location where you want the certificate/key saved. Use a path where you’ve got write access or there will be an error.
6. Press Generate.
7. Wait.
8. The paths should have been filled in for you. Password is blank.
9. Press OK to save the settings.

You need to do what the «Configuring server for Passive mode» chapter tells you.

— Defining a port range for Passive data connections in the Passive settings for FZ Server. The listening port(s) alone don’t work.
— Open that port range in all firewalls you might have. Hopefully it’s just one. The range is TCP only.
— Forward that port range in your router, along with the listening ports.

Источник

FileZilla Forums

Welcome to the official discussion forums for FileZilla

Setting up an ftp server->Error: Server refused FTP over TLS

Setting up an ftp server->Error: Server refused FTP over TLS

#1 Post by Trugoras » 2016-05-11 07:32

Hey Guys i’m trying to set-up an server and gone through the network configuration page but still not working. Obviously i’m doing something wrong but i can’t figure out what. I have added filezilla to firewall exception (later just turn the firewall off) i have forwarded ports in my NAT router to my computer and i believe the options in filezilla are correct. I’ll attach some files to show the settings btw, hope you guys can help.

Test log
Status: Resolving address of GreenMachine
Status: Connecting to 213.133.34.52
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message.
Reply: 220 Microsoft FTP Service
Command: CLNT https://ftptest.net on behalf of 2001:982:91d4:1:5959:68d7:5d6:5549
Reply: 500 ‘CLNT https://ftptest.net on behalf of 2001:982:91d4:1:5959:68d7:5d6:5549’: command not understood.
Command: AUTH TLS
Reply: 534 Local policy on server does not allow TLS secure connections.
Warning: Server refused AUTH TLS, trying deprecated AUTH SSL fallback.
Command: AUTH SSL
Reply: 534 Local policy on server does not allow TLS secure connections.
Error: Server refused FTP over TLS

Re: Setting up an ftp server->Error: Server refused FTP over TLS

#2 Post by boco » 2016-05-11 12:50

Re: Setting up an ftp server->Error: Server refused FTP over TLS

#3 Post by Trugoras » 2016-05-11 13:42

Hmm i havn’t seen that text just shows me:
FileZilla Server 0.9.57 beta
Copyright 2001-2016 by Tim Kosse (tim.kosse@filezilla-project.org)
https://filezilla-project.org/
Connecting to server localhost:14147.
Connected, waiting for authentication
Logged on

Could be the features my World wide web feature is on while its off on your picture. About the Microsoft server, i never used it to my knowledge and have no idea why it is on my pc.

Re: Setting up an ftp server->Error: Server refused FTP over TLS

#4 Post by boco » 2016-05-11 15:46

How did you determine your public IP address? Is the address/IP used with the tester really yours? There’s clearly an MS FTP server answering the call.

Alternatively, you could be behind an IPv6 transition technique like DS-Lite. In that case you do not have a public IPv4 address and thus cannot run servers with public access over IPv4. The server answering would then be the gateway server of the ISP.

Re: Setting up an ftp server->Error: Server refused FTP over TLS

#5 Post by Trugoras » 2016-05-11 16:07

These quick reponses are awesome man, thanks! About the external ip adress i thought the settings in passive mode would do that for me, but maybe i miss understand, after getting my external ip from http://www.whatismypublicip.com/ it work, but i don’t know if this is a static ip adress or a dynamic (which is random right?). Should i use this site instead of the default one?

PS: don’t know if neccesary but made hid ip

Re: Setting up an ftp server->Error: Server refused FTP over TLS

#6 Post by boco » 2016-05-11 16:54

Yes the Retrieve option will work also and spare the manual changing. The real problem is: How will you know what your new server address is, from far away? The answer is: Dynamic DNS providers! One example is No-IP.com, it will give you an URL that always points to your up-to-date IP if you follow the setup procedure. Since you’re a believer in the almighty AVM Fritz!Box*, I can tell they include a Dynamic DNS section where you simply select the provider and your login data. The router will then keep the URL current.

*That was a joke. They have their issues, too, but are a lot better than the no-name China crap.

Re: Setting up an ftp server->Error: Server refused FTP over TLS

#7 Post by Trugoras » 2016-05-11 18:27

Re: Setting up an ftp server->Error: Server refused FTP over TLS

#8 Post by boco » 2016-05-11 19:42

1. Two possibilities: Either use the «Retrieve» option your arrow pointed to, or you can enter the No-IP URL into the «Use the following IP» field (minus the http:// protocol identifier).

2. I’m an AVM user, too. If you want to be completely free from distributor firmware, search the web for «DD-WRT» (Explanation) and buy a recent model that’s supported by them.

Источник

FileZilla Forums

Welcome to the official discussion forums for FileZilla

the FTP over TLS problem

the FTP over TLS problem

#1 Post by cusance » 2015-07-29 14:39

the latest version of Filezilla uses FTP over TLS as default.
for me this causes a problem as commands are rejected by my own server. (Cocktail Media Server X10) So, on my OWN network ‘this’ side of the firewall.
I found the following about the specification for FTP over TLS:

«The FTP protocol specification dictates that it is up to the client to specify session attributes like the protection level. The server cannot require that the client use TLS, but it can refuse to accept any command from the client until it sends an AUTH TLS FTP command to upgrade the control channel to TLS protection. See the FTPOptions, specifically the RequireSSL option, to make the server refuse any FTP command until a TLS session is established.»

My question is, does Filezilla send this ‘AUTH TLS FTP’ command ?

In the meantime i have gone back to an older version of FileZilla. Any thoughts anyone?

Re: the FTP over TLS problem

#2 Post by botg » 2015-07-29 15:33

Re: the FTP over TLS problem

#3 Post by botg » 2015-07-29 15:38

Re: the FTP over TLS problem

#4 Post by cusance » 2015-07-29 18:43

my X10 media server is on my own private network inside the firewall and does not have an external IP address. In any case, the only firewalls here are latest windows 7 and latest HUB 5 BT. But in this case the firewall is a red herring i think. I purely connect on my own home network between the computer and the media server. Firewall doesnt come into it. However the previous Filezilla version works fine which is a clue I think, but the latest version doesnt. the command to display the folders isnt recognised but initial connection to the server is made OK.
it just doesnt work, as many other folks have commented. All filezilla needs is code that makes it function like previous versions if for some reason no correct response is received from the server. clearly this is not the case at the moment, as it would otherwise work. I have gone back one version in filezilla and all works fine again.
I might be wrong but I really think this is a Filezilla coding issue. Here is a listing:

Status: Connecting to 192.168.1.69:21.
Status: Connection established, waiting for welcome message.
Status: Insecure server, it does not support FTP over TLS.
Status: Connected
Status: Retrieving directory listing.
Command: PWD
Response: 257 «/» is current directory.
Command: TYPE I
Response: 200 Type set to I.
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,69,153,8)
Command: MLSD
Response: 500 ‘MLSD’: command not understood.
Error: Failed to retrieve directory listing

I see no sign that it has defaulted back to normal FTP
I can see that the server has correctly reported that it does not support FTP over TLS
from that point onwards I would expect Filezilla code to be as in previous versions as that would make sense.
but i dont think it is.
Here the listing from the previous version:

Status: Connecting to 192.168.1.69:21.
Status: Connection established, waiting for welcome message.
Status: Insecure server, it does not support FTP over TLS.
Status: Server does not support non-ASCII characters.
Status: Connected
Status: Retrieving directory listing.
Status: Directory listing of «/» successful

Now this makes total sense to me.
Why, if a server reports that it does not support FTP over TLS
would one then use the MLSD command??
Maybe someone can explain. By the way, dont get confused by the ‘insecure server’ line.
This server has NO connection outside the firewall and outside my home network.
it can not be reached from outside.

Источник

Устранение ошибки «Could not load TLS libraries» в программе FileZilla

При передаче данных по FTP-протоколу случаются различного рода ошибки, которые обрывают связь, или вообще не позволяют подключиться. Одной из самых частых ошибок при использовании программы FileZilla является ошибка «Could not load TLS libraries». Попробуем разобраться в причинах этой проблемы, и в существующих путях её решения.

Причины ошибки

Для начала разберемся, в чем причина ошибки «Could not load TLS libraries» в программе FileZilla? Дословный перевод на русский язык данной ошибки звучит как «Не удалось загрузить библиотеки TLS».

TLS – это протокол криптографической защиты, более продвинутого уровня, чем SSL. Он обеспечивает безопасность передачи данных, в том числе при использовании соединения FTP.

Причин ошибки может быть множество, начиная от неправильной установки программы FileZilla, и заканчивая конфликтом с другим софтом, установленным на компьютере, либо настройками операционной системы. Довольно часто проблема возникает из-за отсутствия важного обновления Windows. Точную причину сбоя может указать лишь специалист, после непосредственного изучения конкретной проблемы. Тем не менее, попробовать устранить данную ошибку может и обычный пользователь со средним уровнем знаний. Хотя для устранения проблемы, желательно знать её причину, но не обязательно.

Решение проблем с TLS на стороне клиента

Если вы пользуетесь клиентской версией программы FileZilla, и у вас появляется ошибка, связанная с библиотеками TLS, то попробуйте, прежде всего, проверить все ли обновления установлены на компьютере. Важное значение для Windows 7 имеет наличие обновления KB2533623. Также следует установить компонент OpenSSL 1.0.2g.

Если данная процедура не помогла, следует деинсталлировать FTP-клиент, а после установить заново. Конечно, деинсталляцию можно проводить и при помощи обычных инструментов Windows для удаления программ, расположенных в панели управления. Но лучше проводить деинсталляцию с помощью специализированных приложений, которые удаляют программу полностью без остатка, например Uninstall Tool.

Если после переустановки проблема с TLS не исчезла, то следует подумать, а настолько ли важно для вас шифрование данных? Если данный вопрос принципиальный, то нужно обратиться к специалисту. В случае, если отсутствие повышенного уровня защиты для вас некритично, то для возобновления возможности передачи данных по FTP-протоколу следует вообще отказаться от использования TLS.

Что бы отключить TLS, заходим в Менеджер сайтов.

Выделяем нужное нам подключение, а затем в поле «Шифрование» вместо пункта с использованием TLS, выбираем пункт «Использовать обычный FTP».

Очень важно осознавать все риски, связанные с решением отказаться от использования шифрования TLS. Впрочем, в некоторых случаях они могут быть вполне оправданными, особенно если передаваемые данные не представляют большой ценности.

Исправление ошибки со стороны сервера

В случае, если при использовании программы FileZilla Server возникает ошибка «Could not load TLS libraries», то для начала можно попробовать, как и предыдущем случае, установить на компьютер компонент OpenSSL 1.0.2g, а также проверить обновления Windows. В случае отсутствия какого-то обновления, нужно подтянуть его.

Если после перезагрузки системы ошибка не исчезает, то пробуем переустановить программу FileZilla Server. Удаление, как и в прошлый раз, лучше выполнять с помощью специализированных программ.

Если не один из указанных вариантов не помог, то можно вернуть работоспособность программы путем отключения защиты по протоколу TLS.

Для этого переходим в настройки FileZilla Server.

Открываем вкладку «FTP over TLS setting».

Снимаем флажок с позиции «Enable FTP over TLS support», и жмем на кнопку «OK».

Таким образом, мы отключили шифрование по протоколу TLS со стороны сервера. Но, нужно также брать во внимание тот факт, что это действие связано с определенными рисками.

Мы выяснили основные способы устранения ошибки «Could not load TLS libraries» как на стороне клиента, так и сервера. Нужно отметить, что прежде чем прибегать к радикальному методу с полным отключением шифрования TLS, следует попробовать другие варианты решения проблемы.

Источник