Recent Posts

Pages: [1] 2 3 ... 10
Dear castaglia,

I am so sorry for late response because of long holiday in Japan.

ProFTPD Version is 1.3.4b.

Also, I attached the log file.

Could you please investigate the cause and resolution?
If you have any other requests or want more information, please feel free to ask me.

Best Regards,
Support / Re: Drobo5n and ProFTPD
« Last post by michael purdy on August 17, 2017, 09:37:12 pm »

So I contacted Drobo Support and they solved my issue. The fix is simple. I'm just going to copy paste their instructions:

Thank you for contacting Drobo Technical Support. My name is Sean and I will be assisting you with your issue.

You can get to the DroboApps share manually with the following steps.

In Windows Explorer, select Map Network Drive

Choose a drive letter, then for the server put in the following information.

\\<Ip address or name of the Drobo>\DroboApps

Click Connect and will most likely be prompted for a login, if not you should be connected and see the files needed.

I look forward to hearing from you.

Password-based authentication and publickey-based authentication are *independently* supported in mod_sftp in older versions; requiring *both together at the same time* does require ProFTPD 1.3.6.

I try to auth using public key and password.
The config from
Syntax: SFTPAuthMethods meth1 ...
Default: publickey password
Context: server config, <VirtualHost>, <Global>
Module: mod_sftp
Compatibility: 1.3.2rc2 and later

The SFTPAuthMethods directive configures the list of available authentication methods presented to connecting clients. The list of currently supported methods is:


In general, there is no need to use this directive unless only one specific authentication method must be used. Should it be needed, the list of authentication methods to use is provided as a space-delimited list, e.g.:

  # Offer publickey and keyboard-interactive authentication only
  SFTPAuthMethods publickey keyboard-interactive

The hostbased authentication method is only offered to clients if the SFTPAuthorizedHostKeys directive is configured.

The publickey authentication method is only offered to clients if the SFTPAuthorizedUserKeys directive is configured.

The keyboard-interactive authentication method is only offered to clients if the mod_sftp_pam module is present.

As of proftpd-1.3.6rc2 and later, you can use the SFTPAuthMethods directive to configure chains of methods. An authentication chain is a list of authentication methods, all of which must succeed in order for login to succeed. For example, using:

  # Require both publickey and password authentication
  SFTPAuthMethods publickey+password

Note that order of the methods in a chain is important. In the above example, the publickey authentication must succeed first, before password authentication will be offered. If you want require both publickey and password authentication, but that they can be used in any order, you can configure multiple chains:

  # Require both publickey and password authentication, in any order
  SFTPAuthMethods publickey+password password+publickey

As long as any one chain is completed, login will succeed.

You can even require that multiple different keys be used (e.g. a RSA and a DSA public key, or multiple different RSA/DSA keys) using:

  # Require different keys for publickey authentication
  SFTPAuthMethods publickey+publickey
was used.
When I enter " SFTPAuthMethods password+publickey" in the sftp.conf I receive the following error message while restarting proftpd:
Code: [Select]
Aug 17 09:39:10 ftp proftpd[2648]: Starting ftp server: proftpd2017-08-17 09:39:10,933 ftp proftpd[2654]: fatal: SFTPAuthMethods: unsupported authentication method: password+publickey on line'If the "+" gets deleted from the conf everything works fine again but users will be able to logon using the pub key only.
The docs say that the password+key auth will work starting from 1.3.2rc2.
My proftpd Version is 1.3.5 (stable).
Are there any other changes needed than told in the mentioned doc?

Best regards

==> I see version 1.3.6 is needed ......
Support / Drobo5n and ProFTPD
« Last post by michael purdy on August 16, 2017, 07:43:07 pm »
I need to edit my proFTPD.conf file so the server gives its external IP address using the MasqueradeAddress command

I'm using Windows 10. How do I gain access to the proFTPD.conf file so that I can edit it? The drobo says its located in:


Support / Re: MaxClientsPerHost ignored
« Last post by castaglia on August 12, 2017, 09:29:57 pm »
The MaxClientsPerHost limit is enforced _when the client sends the PASS command_.  Is it possible that these connections, from the IP address, which exceed that MaxClientsPerHost limit, have not sent USER/PASS commands, but instead are just idling there, taking up connection slows?  What does `ftpwho -v` show for these connections?

Instead of MaxClientsPerHost, you might consider using MaxConnectionsPerHost; see:
Support / Re: MaxClientsPerHost ignored
« Last post by dordal on August 10, 2017, 09:55:05 pm »
MaxClientsPerHost and MaxClientsPerUser are declared inside <Global>, but outside any <VirtualHost> directive.

The 74 connections are to a virtual host, yes.

Does that give you any clues? The really odd thing is that MaxClientsPerUser works; its just MaxClientsPerHost that doesn't.
Support / Re: MaxClientsPerHost ignored
« Last post by castaglia on August 10, 2017, 03:36:00 am »
Is your MaxClientsPerHost directive declared outside of any <Global> or <VirtualHost> sections?  Are these 74 connections to a <VirtualHost> section?
Support / MaxClientsPerHost ignored
« Last post by dordal on August 09, 2017, 06:13:11 pm »
We have a problem with MaxClientsPerHost. MaxClientsPerHost and MaxClientsPerUser both set to 40:

MaxClientsPerHost               40
MaxClientsPerUser               40

Proftpd is not quite the latest, but close:

root@proton:~ # proftpd -v
ProFTPD Version 1.3.5

MaxClientsPerUser is working fine, but MaxClientsPerHost is being ignored. For example, we have 74 connections from the IP

root@proton:~ # ps -ajx | grep proftpd | grep 65\.200\.133\.4 | wc -l

I think the stats for who's connected are kept in the scoreboard file, right?

-rw-r--r--   1 root    wheel    386432 Aug  9 11:10 proftpd.scoreboard
-rw-r-----   1 root    wheel         0 Aug  9 06:20 proftpd.scoreboard.lck

The only thing odd I see is that there's a scoreboard lock file that hasn't been touched since proftpd restarted at 06:20, but I think that's normal? What else is there to check?

mod_tls / Re: Letsencrypt configuration
« Last post by danjde on August 09, 2017, 12:15:57 pm »
castaglia:[...]these ProFTPD forums are not the best place for that.

Found the issues:

1) must assign passive ports to proftpd:

# Specify the ftp-data port range to be used
PassivePorts                    70000 75000

2) must open the same ports on shorewall:

ACCEPT  net     fw      tcp     -      70000:75000

et voilą
Pages: [1] 2 3 ... 10
sighted planning