SlrG

Community Developer
  • Posts

    564
  • Joined

  • Last visited

Everything posted by SlrG

  1. @master00 Not within the scope of this plugin. If you setup a vm and install gadmin-proftpd as gui this will come with gprostats as statistics generator. Also there might be other ftp servers more capable but not necessarily free. @kricker The easiest way would be to restore a backup, if you have. Otherwise as there is no recycle bin you can only search and try some linux ways to restore your data. First make sure nothing is written to your array anymore or you will risk the deleted data being overwritten! I had successes using testdisk and photorec on standalone machines, but never had to try on an unraid machine yet. (see this article for other tools: https://www.journaldev.com/36900/top-best-linux-data-recovery-tools) Make sure however, you mount another disk outside of your array as target for all write operations or again you will risk the deleted data being overwritten. Also you will probably need to know on which exact disk the data you want to recover was and then let the tools work on that disk. I hope this ideas are useful, but I fear the chance to recover the data is very slim. 😟
  2. @SvbZ3r0 Yes, sadly the last change by me to solve the problems with quotes and double quotes in filenames is not perfect either and shows the shown symptoms under certain conditions. In all my test there was never data lost, but from time to time these "cosmetic" problems show up. If I have the time, I'll have a look at it again and will try to solve it. Sadly my times is very limited, so please don't expect fast results.
  3. @Berto90vi In unraids user creation screen open your user "x" and put "ftpuser /mnt/user/Download" (without the double quotes) into the Description field. Then apply and restart the proftpd plugin. This will jail the user x into the given directory. It will still have read and write access, however. If you want to restrict that, you will need to configure limits in your proftpd.conf.
  4. Hi, While I really like Font Awesome as an icon provider, I would prefer for it to be switched to a more open source alternative, like Fork Awesome. Or maybe it would be an even better idea to create an own unraid icon font based on Fork Awesome. Developers could then create their own icon for their plugin and it could be added by merging their pull request on the new unraid fonts repository. Please let me know your opinions. Background Story: I'm the developer of the ProFTPD plugin and obviously I would like to use an icon of the official logo for the plugin. In March 2019 I requested the logo to be incorporated in font awesome. But as it was classified as a "brand icon" it would cost 3.000$ to get it included. Even the non brand 300$ would be to much for me. As it is now 2021 I doubt it will be included free sometime in the future. Getting it included into fork awesome was much easier. cheers, SlrG
  5. @Flemming See here for the difference between active and passive ftp. For both types normally data ports >1024 are randomly opened. You can restrict the used ports using the PassivePorts directive.
  6. @Flemming Are there any error messages in the syslog when trying to connect?
  7. @Flemming The "Plugin file missing" under Information indicates a failed uninstallation. On why this happened, I have no idea. To get back to a clean state I would the recommend the manual removal and reinstallation described by @kricker. If you have the time to experiment, what happens if you click "update plugin"?
  8. @offroadguy56 Ah I see. I had only tested with root and as that worked I falsely assumed it would work with other users, too. Further testing shows that it would be possible to enable ssh for other users, but it is a complicated multi step process and it would also be reset each boot, so it would require scripting to restore its state and so all in all it is probably too much hassle. The synology in a vm idea sounds very cool. A quick search shows they seem to support FTPS and SFTP and access management for the users. Though such a solution will obviously not be endorsed by Synology without buying their hardware. If you want to continue with the ssh idea, there is the "openssh-server" docker in unraids community applications. If I understand it correctly, this will enable ssh for one user per container and this user will only be able to access what you mount into the container. So you should be able to configure a secure backup access for your friends. Looking at ftp again, that you can use it now is thanks to unraids internal ftp server, as you already noted. The drawback is, that it is unencrypted ftp and always gives access to the complete server. I wrote the proftpd plugin and use it myself for my home network only. Basically it provides unencrypted FTP (like the stock ftp service) but with the added benefit of being able to jail the users into home directories they cant leave and so only have access to what I want them to. While it is possible to open this up to the internet it is in no way recommended because of the default unencrypted connections. Proftpd can be configured to use FTPS or SFTP, but it is sadly complicated and while there are some tips in this thread how to do it, there are cases where it doesn't work and I sadly don't have the time to fully support other users in how to set it up.
  9. @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 is a security precaution by the plugin.) restart the proftpd service so the user is removed from the jail make sure, you can login with this user using ssh, and get a normal shell setup your ftp client to connect using SFTP Now it should work in theory. Using this connection type you don't need the proftpd plugin and can remove it.
  10. @cinereus In your last post you mentioned, that and that the path repo suggested to use cpg and mvg as the command names.
  11. @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).
  12. @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 automatically recognizing and attacking your ftp server. Be aware however, that by default FTP is an unencrypted and unsecure protocol. You can try to enable encryption (search this thread on how to do this - its no easy process however) or find other means to securely backup your wordpress.
  13. @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.
  14. @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!
  15. @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 or more. So I would only recommend it, if you are the only one using this ftp user. The third possibility and mounting read only is probably the safest way to handle this, if you want other users besides yourself to access the files. Where you create the FTP base folder is mostly a matter of taste. If you create it on the cache only, writing to it, but not to the mounted media files inside will be faster, as if you put it on the array directly. In most cases the speed will be about the same however, as through the mount, the array will be accessed anyway. Also please don't just create folders in the root of the cache directory from the shell. Always use unraids share management to do this. Set the FTP share to cache only and don't change this later on, as it will result in the situation you described. This is however an unraid "problem" and how it handles things between cache drive and the array and not related to the plugin itself. The only solutions to not run into it, would be to jail into the media share folder itself (be aware of the risk described above) or mount some drive outside the array and place the FTP folder on that.
  16. @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.
  17. @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?
  18. @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!
  19. @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.
  20. @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.
  21. @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?
  22. 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.
  23. @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: In stopped array mode, only the flash and no user or disk shares are accessible. No shares means, no sources available to read or write and so it wouldn't make sense to keep the plugin running.) As there are no shares available when stopped, it makes me wonder if your symlink will really work, if you start and stop the array manually? If you have still trouble, I'll need your diagnostics file, to try and find the reason.
  24. @Gee1: It did not try, but maybe this is what you want: http://www.proftpd.org/docs/directives/linked/config_ref_DefaultAddress.html
  25. @Gee1 Maybe you could try to "mount --bind /mnt/user0/Filme /mnt/cache/FTP/Gee/Filme" instead. Does it move the files faster then? The drawback will be, that your FTP users will not be able to access the new files until the mover has moved them from the cache to the array. Or you could try to place the homedir of the user on the array and not on the cache: "mount --bind /mnt/user/Filme /mnt/FTP/Gee/Filme". Also you could try to setup the user without jailing them into a home directory, then you won't need the bind mound. To limit what the user can access use directory and limit directives instead.