Community Developer
  • Content Count

  • Joined

  • Last visited

Community Reputation

28 Good

About SlrG

  • Rank


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @offroadguy56 By the look of your log I doubt you are connecting to the proftpd service. The errors are thrown by unraids sshd service, so I guess you are trying to connect using SFTP which is an entirely different beast using SSH to connect to your server and then using the SFTP protocol to transfer data. (Even called SFTP it is not the same protocol as FTP.) If you want to use this, you have to: remove the ftpuser comment from your user (With this comment given, the user is blocked from logging in and getting a normal shell and will only be allowed to use ftp - this
  2. @cinereus In your last post you mentioned, that and that the path repo suggested to use cpg and mvg as the command names.
  3. @KUMAR @kricker Thank you very much for noticing the problem and providing a solution. I had removed the configuration directive on my system (so the problem did not hit me), but forgot to remove it from the default config file provided with the plugin. 😢 I released a new version which fixes that and also removes the directive from existing configs (if found).
  4. @thymon My recommendation is to never connect your unRAID server directly to the internet. Always use a vpn (openvpn, wireguard) to connect to your home network from other sites and then you can directly access any device as if you were in the same network. In some cases this is not possible however. Then never use the ftp default port 21 facing the internet! Define port forwarding rules on your router/firewall, which will forward outside traffic from a private port between 49152 and 65535 to your internal port 21 on the unRAID server. This will stop the most crawlers from aut
  5. @Autchirion A future update probably will. It will not be the next one however. That will bring the current proftpd version and fix some underlying ownership and permission problems (not noticeable to the user). Sadly my time to work on this plugin is extremely limited. 😢 The only workaround at the moment is to switch to light mode, change the settings and return to dark mode. I know this sucks, but as it is not often necessary to change the config of the plugin it's not a critical problem.
  6. @Meller As Squid noticed, I have deprecated the glftpd docker. The last change I did on it, was 6 years ago. I sadly don't have much time to develop things any longer and have to pick carefully which projects I support. Being that old, it probably contains a lot of bugs and or security problems. Also I didn't want users looking for ftp in CA to install it and then be disappointed that it is that old and unsupported. The dockerfile and scripts are still on my github however, if someone wishes to pick it up and work on it, feel free to do so!
  7. @soder Sorry for the late reply. I hope you have not lost any data. I have a bit of trouble to understand, what you really want to do. If you want your ftp user to access your media share, you could indeed setup the user to be jailed into that directory. Or don't jail the user at all and give him access to the whole server like the default unraid ftp does. A third possibility is to mount your media share into the folder used for the ftp jail directory. Of course a proper rights management is key here, or the user will have the chance to delete all your media files
  8. @DovahDovolom Are these three files all the same file for testing purposes, or are there differences? Above I asked you to change the order of the files you try to transfer. If the "third" file always stops, please try to transfer that as the first file and the other ones later. Does it work then or does it still fail? Is it possible to copy the file to another location in a shell without using proftpd without problems? To enable debug logging see here.
  9. @DovahDovolom Are there any error messages in the syslog when the transfer stops for the third file? What happens if you try to transfer only the third file? What happens if you transfer the files one by one? What happens if you run a linux vm or another machine, with proftpd installed and copy the files using that?
  10. @all Released a new version and renamed the commands from gcp and gmv to cpg and mvg. If you have shell aliases please update them accordingly! @bubbaQ If you still have those large testfiles and the freetime, could you give the new version a spin? I don't expect problems, but sometimes tests on one (my) system don't match others. Thank you very much!
  11. @SkinnySkelly I'm glad you got it working. Default location for config files is /etc/. So the "correct" way would be to edit /etc/proftpd. conf. This is a symlink to the file you mentioned on the flash however, so it doesn't really matter.
  12. @Obscuritas The error message indicates permission problems. What are the linux user and permissions for the folder where you want to upload the file? Default unRAID user and permissions are user:nobody group: users and u-x,go-rwx,go+u,ugo+X. You can achieve this by running the newperms script for that directory e. g. newperms /mnt/user/targetdir.
  13. @Gee1 Another idea is to create a virtual host with an IP address instead of a FQDN (see here). If this doesn't work, I'm sadly out of ideas, sorry. Maybe you could try to ask on the ProFTPd forum?
  14. Hmm... It was enabled by default in previous versions. It must have changed somewhere along the way. Thank you for the bug report. I'll try to fix it in a future version. It can take a while however as I have little to no time.
  15. @Retrogamer137 This is the support thread, but I'm not reading it regularly and depend on the notifications mostly. Sometimes they sadly fail. I got no info on your first post, but for the second one it worked. To answer your questions, stopping and restarting the array will stop and restart the plugin, too. So is it really crashing or are you "killing" it manually? Under normal circumstances however, the plugin should start automatically, when the array is started again. So if you have to manually restart it, something is indeed going wrong. (A bit of explanation: