ProFTPD Plugin for unRAID v6.8.x


SlrG

Recommended Posts

@jeffreywhunter

Sorry for the delayed answer, I was on vacation. The first error is because the config file for proftpd is stored on your flash drive for persistence. When the unRAID server is running, it is symlinked to the config folder in your RAM but it inherits the user and access rights from the flash. As the flash uses the old MS-DOS filesystem fat32, there are no user and access rights stored and thus the error is thrown. It is a possible security risk, that anybody who has access to your flash is able to edit the config files, but that if somebody has physical access to your server there are a lot more effective ways to harm you or your data. So it can be ignored. Sadly there is no way to disable the error.

 

For the second one, please check your ProFTPd.conf. The default logging section looks like this:

# Control Logging - comment and uncomment as needed
# If logging Directory is world writeable the server won't start!
# If no SystemLog is defined proftpd will log to servers syslog.
#SystemLog               NONE
#SystemLog               /boot/config/plugins/ProFTPd/slog
TransferLog             NONE
#TransferLog             /boot/config/plugins/ProFTPd/xferlog
WtmpLog                 NONE

Please note the TransferLog NONE line and the # before the TransferLog /boot/config... line.

The TransferLog NONE should solve your error. It won't log Transfers, but normally this is not necessary.

If you want to log Transfers, it should be enough to create an empty xferlog file on the flash or

different path. This should  persist and will not require a go file entry.

 

@killeriq

Please read the first post and the readme. This should answer your questions. You need to configure

an user to allow FTP access by editing the comments of this user in unRAIDs user management.

Link to comment
9 minutes ago, SlrG said:

@jeffreywhunter

For the second one, please check your ProFTPd.conf. The default logging section looks like this:


# Control Logging - comment and uncomment as needed
# If logging Directory is world writeable the server won't start!
# If no SystemLog is defined proftpd will log to servers syslog.
#SystemLog               NONE
#SystemLog               /boot/config/plugins/ProFTPd/slog
TransferLog             NONE
#TransferLog             /boot/config/plugins/ProFTPd/xferlog
WtmpLog                 NONE

Please note the TransferLog NONE line and the # before the TransferLog /boot/config... line.

The TransferLog NONE should solve your error. It won't log Transfers, but normally this is not necessary.

If you want to log Transfers, it should be enough to create an empty xferlog file on the flash or

different path. This should  persist and will not require a go file entry.

 

 

@SlrG

Hey thanks for the reply, hope you had a restful vacation.  Yep, I had already looked through and verified this section.  See the attached screenshot.  You can see from the telnet session the /flash.../xferlog directory exists on the flash and its propagating to the /boot.../xferlog directory.  But I'm still getting that error.

 

Screenshot

Link to comment
  • 3 weeks later...

Hi,

 

I'm using UNRAID 6.3.5 with proFTP plugin verison 1.3a...

 

Trying top login with sFTP from a remote location with an ssh key. The logging doesn't work (it seems to freeze), and I see this in the UNRAID log at the time of the login.. Any ideas?

 

Thank you!

Reuben

 

Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - -----BEGIN STACK TRACE-----
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [0] /lib64/libcrypto.so.1(RSA_generate_key_ex+0x17) [0x2adb76929817]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [1] /lib64/libcrypto.so.1(RSA_generate_key_ex+0x17) [0x2adb76929817]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [2] proftpd: (authenticating) - (connecting): IDLE() [0x4d5c10]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [3] proftpd: (authenticating) - (connecting): IDLE(sftp_kex_handle+0x250) [0x4d60e0]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [4] proftpd: (authenticating) - (connecting): IDLE(sftp_ssh2_packet_handle+0x2c4) [0x4cdc44]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [5] proftpd: (authenticating) - (connecting): IDLE() [0x4c9572]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [6] proftpd: (authenticating) - (connecting): IDLE() [0x41e74e]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [7] proftpd: (authenticating) - (connecting): IDLE() [0x41efb4]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [8] proftpd: (authenticating) - (connecting): IDLE(main+0x56b) [0x41d1ab]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [9] /lib64/libc.so.6(__libc_start_main+0xf0) [0x2adb76ea8350]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - [10] proftpd: (authenticating) - (connecting): IDLE(_start+0x2a) [0x41d70a]
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - -----END STACK TRACE-----
Aug 30 18:46:00 UNRAID-NAS proftpd[30043]: 127.0.0.1 (192.168.2.100[192.168.2.100]) - ProFTPD terminating (signal 11)

 

From an earlier post:

Hello,

 

Not sure if this is a bug in the ProFTPd Plugin for UNRAID or what. Trying to sFTP to a ProFTPd plugin instance using Mobaxterm and I'm seeing this is the logs. Any ideas?

 

Aug 8 08:24:33 UNRAID-NAS kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Aug 8 08:24:33 UNRAID-NAS emhttp: nothing to sync
Aug 8 08:24:34 UNRAID-NAS kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Aug 8 08:24:34 UNRAID-NAS kernel: Ebtables v2.0 registered
Aug 8 08:24:34 UNRAID-NAS kernel: virbr0: port 1(virbr0-nic) entered blocking state
Aug 8 08:24:34 UNRAID-NAS kernel: virbr0: port 1(virbr0-nic) entered disabled state
Aug 8 08:24:34 UNRAID-NAS kernel: device virbr0-nic entered promiscuous mode
Aug 8 08:24:34 UNRAID-NAS avahi-daemon[8480]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Aug 8 08:24:34 UNRAID-NAS avahi-daemon[8480]: New relevant interface virbr0.IPv4 for mDNS.
Aug 8 08:24:34 UNRAID-NAS avahi-daemon[8480]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Aug 8 08:24:34 UNRAID-NAS kernel: virbr0: port 1(virbr0-nic) entered blocking state
Aug 8 08:24:34 UNRAID-NAS kernel: virbr0: port 1(virbr0-nic) entered listening state
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: started, version 2.76 cachesize 150
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
Aug 8 08:24:34 UNRAID-NAS dnsmasq-dhcp[9747]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Aug 8 08:24:34 UNRAID-NAS dnsmasq-dhcp[9747]: DHCP, sockets bound exclusively to interface virbr0
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: reading /etc/resolv.conf
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: using nameserver 167.206.251.75#53
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: using nameserver 167.206.251.11#53
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: using nameserver 167.206.251.74#53
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: read /etc/hosts - 2 addresses
Aug 8 08:24:34 UNRAID-NAS dnsmasq[9747]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Aug 8 08:24:34 UNRAID-NAS dnsmasq-dhcp[9747]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Aug 8 08:24:34 UNRAID-NAS kernel: virbr0: port 1(virbr0-nic) entered disabled state
Aug 8 08:24:35 UNRAID-NAS avahi-daemon[8480]: Service "UNRAID-NAS-AFP" (/services/afp.service) successfully established.
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - -----BEGIN STACK TRACE-----
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [0] /lib64/libcrypto.so.1(RSA_generate_key_ex+0x17) [0x2aaf0f4d5817]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [1] /lib64/libcrypto.so.1(RSA_generate_key_ex+0x17) [0x2aaf0f4d5817]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [2] proftpd: (authenticating) - (connecting): IDLE() [0x4d5c10]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [3] proftpd: (authenticating) - (connecting): IDLE(sftp_kex_handle+0x250) [0x4d60e0]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [4] proftpd: (authenticating) - (connecting): IDLE(sftp_ssh2_packet_handle+0x2c4) [0x4cdc44]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [5] proftpd: (authenticating) - (connecting): IDLE() [0x4c9572]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [6] proftpd: (authenticating) - (connecting): IDLE() [0x41e74e]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [7] proftpd: (authenticating) - (connecting): IDLE() [0x41efb4]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [8] proftpd: (authenticating) - (connecting): IDLE(main+0x56b) [0x41d1ab]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [9] /lib64/libc.so.6(__libc_start_main+0xf0) [0x2aaf0fa54350]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - [10] proftpd: (authenticating) - (connecting): IDLE(_start+0x2a) [0x41d70a]
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - -----END STACK TRACE-----
Aug 8 08:24:37 UNRAID-NAS proftpd[9866]: 127.0.0.1 (143.55.61.60[143.55.61.60]) - ProFTPD terminating (signal 11)

Edited by Ruby-Rube
correct
Link to comment

@Ruby-Rube

Sadly I can't tell from the errors what the problem could be. Maybe it would help to up the logging level to a high debug by adding

SyslogLevel DEBUG
DebugLevel 10

to you ProFTPd.conf, as described here. Let's see what the error messages look like, if you try it with that enabled.

Edited by SlrG
Link to comment

Thank you, here is the error after enable the DEBUG logging in ./boot/config/plugins/ProFTPd/proftpd.conf.


Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - mod_delay/0.7: no DelayOnEvent rules configured with "DelayTable none" in effect, disabling module
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - connected - local : 192.168.2.251:2222
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - connected - remote : 143.x.x.x:60671
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - SSH2 session opened.
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - dispatching LOG_CMD command 'KEXINIT' to mod_log
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - -----BEGIN STACK TRACE-----
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [0] /lib64/libcrypto.so.1(RSA_generate_key_ex+0x17) [0x2b701c7d5817]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [1] /lib64/libcrypto.so.1(RSA_generate_key_ex+0x17) [0x2b701c7d5817]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [2] proftpd: (authenticating) - (connecting): IDLE() [0x4d5c10]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [3] proftpd: (authenticating) - (connecting): IDLE(sftp_kex_handle+0x250) [0x4d60e0]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [4] proftpd: (authenticating) - (connecting): IDLE(sftp_ssh2_packet_handle+0x2c4) [0x4cdc44]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [5] proftpd: (authenticating) - (connecting): IDLE() [0x4c9572]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [6] proftpd: (authenticating) - (connecting): IDLE() [0x41e74e]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [7] proftpd: (authenticating) - (connecting): IDLE() [0x41efb4]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [8] proftpd: (authenticating) - (connecting): IDLE(main+0x56b) [0x41d1ab]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [9] /lib64/libc.so.6(__libc_start_main+0xf0) [0x2b701cd54350]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - [10] proftpd: (authenticating) - (connecting): IDLE(_start+0x2a) [0x41d70a]
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - -----END STACK TRACE-----
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - ProFTPD terminating (signal 11)
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - mod_sftp/1.0.0: scrubbing 2 passphrases from memory
Aug 31 09:33:07 UNRAID-NAS proftpd[26684]: 127.0.0.1 (143.x.x.x[143.x.x.x]) - SSH2 session closed.

 

Link to comment

@Ruby-Rube

Sadly this is way over my head. I don't know what is going wrong and what is causing your error. If it is my selfcompiled version of proftpd used for the plugin, or if it is unraid or something else entirely. I guess you will have to contact the proftpd devs using their forum or mailing list and ask them, if they can tell from the log what is going wrong. Sorry. :(

Link to comment
On ‎2‎/‎21‎/‎2013 at 0:28 AM, SlrG said:

With my supplied proftpd.conf it goes to the syslog. If you want to change that you can do by editing /etc/proftpd.conf in shell.

 

This is the section of the conf file:

# Control Logging - comment and uncomment as needed

# If logging Directory is world writeable the server won't start!

# If no SystemLog is defined proftpd will log to servers syslog.

#SystemLog              NONE         

#SystemLog              /boot/config/plugins/proftpd/slog

TransferLog            NONE

#TransferLog            /boot/config/plugins/proftpd/xferlog

WtmpLog                NONE

 

Uncomment the SystemLog line with path and supply a path where you want the logfile saved. Do the same with TransferLog. For WtmpLog you change the NONE to a path.

 

For more advanced logging features have a look here.

SlrG

Hi SirG-

 

Am trying to log connections and transfers.  I edited the proftpd.conf file located in /flash/config/plugins/proftpd and tried to point it to a share, however it failed.  i then tried to uncomment your commented path (above), restarted the plugin and it still does not log the transfer.  any ideas what i am doing wrong?  here is what i have in the file:

 

# Control Logging - comment and uncomment as needed
# If logging Directory is world writeable the server won't start!
# If no SystemLog is defined proftpd will log to servers syslog.
#SystemLog               NONE
#SystemLog               /boot/config/plugins/ProFTPd/slog
#TransferLog             NONE
TransferLog             /boot/config/plugins/ProFTPd/xferlog
#TransferLog             /media/xfer/xferlog
WtmpLog                 NONE

 

 

 

Link to comment

Has anyone tried this on 6.4rc8q?  It's my first time using the plugin, but i followed the instructions. Created a new user with 'ftpuser /mnt/user/Backup' without quotes, restarted it. I can't connect. FileZilla says "Received unexpected end-of-file from SFTP server". I tried with console based sftp in linux and it also refuses to connect. I've restarted the server. Didn't help.

Link to comment

@althoralthor

Checking the logfile shows that proftpd refuses to create the xferlog file in a directory, that is world writable for security reasons.

Sep  9 15:53:33 lafiel proftpd[23554]: 127.0.0.1 (192.168.178.69[192.168.178.69]) - opening TransferLog '/boot/config/plugins/ProFTPd/xferlog'
Sep  9 15:53:33 lafiel proftpd[23554]: 127.0.0.1 (192.168.178.69[192.168.178.69]) - error: /boot/config/plugins/ProFTPd is a world-writable directory
Sep  9 15:53:33 lafiel proftpd[23554]: 127.0.0.1 (192.168.178.69[192.168.178.69]) - unable to open TransferLog '/boot/config/plugins/ProFTPd/xferlog': No such file or directory

As the unRAID stick has the FAT filesystem, you can't change the security permissions on it. So you need to create a directory on your array or cache drive. There you can use the chmod command to change the permission to set the directory to something only the owner and group can access. Then proftpd will create the transfer log file in there and log transfers.

Link to comment

@Kewjoe

Setting up SFTP access requires changes in the proftpd.conf file too. By default the plugin only supports basic ftp access and only that gets tested. Also it is not tested on versions above 6.3.5.

 

For security reasons I always recommend to use a VPN to access you home network and not expose unRAID to the internet. Doing it that way it doesn't matter, that basic FTP is unencrypted.

Link to comment
2 minutes ago, SlrG said:

@Kewjoe

Setting up SFTP access requires changes in the proftpd.conf file too. By default the plugin only supports basic ftp access and only that gets tested. Also it is not tested on versions above 6.3.5.

 

For security reasons I always recommend to use a VPN to access you home network and not expose unRAID to the internet. Doing it that way it doesn't matter, that basic FTP is unencrypted.

 

Got it, missed that part. No worries, this is internal. Main server to backup server using duplicati backup. I guess I can just use FTP in that case :)

Link to comment
19 minutes ago, SlrG said:

@althoralthor

Checking the logfile shows that proftpd refuses to create the xferlog file in a directory, that is world writable for security reasons.


Sep  9 15:53:33 lafiel proftpd[23554]: 127.0.0.1 (192.168.178.69[192.168.178.69]) - opening TransferLog '/boot/config/plugins/ProFTPd/xferlog'
Sep  9 15:53:33 lafiel proftpd[23554]: 127.0.0.1 (192.168.178.69[192.168.178.69]) - error: /boot/config/plugins/ProFTPd is a world-writable directory
Sep  9 15:53:33 lafiel proftpd[23554]: 127.0.0.1 (192.168.178.69[192.168.178.69]) - unable to open TransferLog '/boot/config/plugins/ProFTPd/xferlog': No such file or directory

As the unRAID stick has the FAT filesystem, you can't change the security permissions on it. So you need to create a directory on your array or cache drive. There you can use the chmod command to change the permission to set the directory to something only the owner and group can access. Then proftpd will create the transfer log file in there and log transfers.

Thanks SirG...  so i had tried to use a directory on a share i created, and i think i am close.  but i have hit the wall on my linux kung fu.  tried googling and only confused myself even more.  so i just want to give everyone permissions.  here is the share path:  /mnt/user/media  and i have a dir called xfer.  can you help me with my chmod command?  i guess i am just not linux capable...

Thanks in advance!

Link to comment

@Kewjoe

If it is internal, using pure FTP would be the simplest solution, yes. :) If you are set on SFTP you can go back in the thread, there are some infos on how to get this running. But be aware, that it is not so easy and as an user reported above, he gets an error witch implicates a crash of proftpd. That one I can't resolve and had to tell him to ask the proftpd devs instead.

 

@althoralthor

Okay no problem. :) I did the following on the unRAID console:

mkdir /mnt/cache/Apps/proftpd
chown nobody:users /mnt/cache/Apps/proftpd
chmod 744 /mnt/cache/Apps/proftpd

The first command creates the directory /mnt/cache/Apps/proftpd where the transferlog file xferlog will be created.

The second command changes the user and group of that directory to nobody:users, which is the user and group of the default unraid user.

The last command changes the access rights to 744 which means owner can do everything (7), group can do reads only (4) and world can do reads only (4).

That solves the security problem proftpd hinders to use the log folder.

 

In the next step you change the proftpd.conf:

#TransferLog             NONE
TransferLog             /mnt/cache/Apps/proftpd/xferlog

So you comment the TransferLog NONE so it gets ignored and define the new TransferLog to be used. The xferlog is the name of the logfile, you can change it if you wish. The other is the path you prepared. Afterwards you restart proftpd and if a connection gets opened, the xferlog file in the folder will get created. It will be empty until a transfer is completed.

 

The file will be owned by the user root, as that is running the proftpd service, but it will be readable by others.

 

  • Like 1
Link to comment
4 hours ago, SlrG said:

@Kewjoe

If it is internal, using pure FTP would be the simplest solution, yes. :) If you are set on SFTP you can go back in the thread, there are some infos on how to get this running. But be aware, that it is not so easy and as an user reported above, he gets an error witch implicates a crash of proftpd. That one I can't resolve and had to tell him to ask the proftpd devs instead.

 

I'm good now. Just using standard FTP. Thanks for following up!

Link to comment
  • 1 month later...

I'm seeing the following errors in the syslog every time ProFTPd executes (I do backups every night via FTP).

 

HunterNAS proftpd[619]: 127.0.0.1 (192.168.29.11[192.168.29.11]) - error: /boot/config/plugins/ProFTPd is a world-writable directory
Oct 18 01:30:07 HunterNAS proftpd[619]: 127.0.0.1 (192.168.29.11[192.168.29.11]) - unable to open TransferLog '/boot/config/plugins/ProFTPd/xferlog': No such file or directory

I've looked at the plugins directory, and the xferlog file is there.  Not been written to since 8/23/17.  Other files in that directory have been written to, even today, so I know its being accessed.  What could be causing this?  Diags attached.

 

Thanks in advance!

hunternas-diagnostics-20171019-2227.zip

Link to comment
  • 3 weeks later...

Does the share have to be a disk? I'm getting the following error:

notice: unable to use DefaultRoot '~/' [resolved to '/mnt/user/testshare/testshare 01/']: No such file or directory
 - chroot to '~/' failed for user 'testftp': No such file or directory
 - error: unable to set DefaultRoot directory

Link to comment

@chillr88

No, any path on your shares should be okay. If you manually created it in the unRAID shell, you will need to check, that it has the correct permissions to be accessible for proftpd. Default is user nobody and group users. Maybe run the newperms script with your directory as parameter (e.g. newperms /mnt/user/testshare/testshare 01/) to set the unraid default permissions. Also make sure you restarted the proftpd service after setting the path for the user.

Edited by SlrG
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.