Jump to content

SlrG

Community Developer
  • Content Count

    517
  • Joined

  • Last visited

Community Reputation

21 Good

About SlrG

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. @danktankk Maybe I misunderstood. I thought you had a share /mnt/user/nextclound, where your nextcloud data is located. Now you want to upload to that folder but have it using the cache, as that is faster and having the mover moving the files in the night to the share. If you upload to /mnt/cache/nextcloud all files will be uploaded to the cache drive utilising its higher speed. In the night the mover will move the files to /mnt/user/nextcloud automatically. No need to move it yourself. The only problem is probably if you have subfolders in your share and want to upload your files to them. The mover will probably move the folders as well as the files so one would have to recreate them each time. I did not test this however.
  2. @danktankk Sorry for the late reply. See above for the reason. What @itimpi told you should work in theory. I don't know, why I isn't. Might be it works only for samba connections and not ftp. What you can try however is to write directly to /mnt/cache/yourfolder which should place the files on the cache and they will be copied to the array by the mover. So if you want to read them after they are moved, you will have to use /mnt/user/yourfolder again.
  3. @fatmaddin2000 Sorry for the late reply. Notifications did not work. It seems the naming of the file /etc/ssl/openssl.cfg has changed back to the default /etc/ssl/openssl.cnf. So the command is now: openssl req -new -x509 -config /etc/ssl/openssl.cnf -days 3650 -nodes -out /boot/config/plugins/proftpd/ssl/ftp.cert.pem -keyout /boot/config/plugins/proftpd/ssl/ftp.key.pem
  4. @Kristijan Sorry for the late reply. Somehow I got no notification of the latest posts even though I have notifications enabled for this thread. I can't replicate your problem, as I am not able to enter "" in the comments field, unraid asks me to "Please match the requested format.", so I don't really know, what was going wrong for you. You can check the contents of /etc/shadow, which is the file that contains your unRAID users. A stock shadow file should probably look like this: root::17990:0:99999:7::: bin::14824:0:99999:7::: daemon::14824:0:99999:7::: adm::14824:0:99999:7::: lp::14824:0:99999:7::: mail::14824:0:99999:7::: news::14824:0:99999:7::: uucp::14824:0:99999:7::: ftp::14824:0:99999:7::: smmsp::14824:0:99999:7::: mysql::14824:0:99999:7::: rpc::14824:0:99999:7::: sshd::14824:0:99999:7::: oprofile::14824:0:99999:7::: usbmux::14824:0:99999:7::: sddm::14824:0:99999:7::: pulse::14824:0:99999:7::: avahi:!:14980:0:99999:7::: avahi-autoipd:!:14980:0:99999:7::: messagebus:!:14980:0:99999:7::: pop::14824:0:99999:7::: haldaemon::14824:0:99999:7::: polkitd::14824:0:99999:7::: nobody::14824:0:99999:7::: tss:!:17825:::::: Though I am not sure, you will have the same "numbers". If the file looks alright, to you, a reboot will probably fix your problem.
  5. @jenga201 In theory this is of course possible. But It might be necessary to add a new dependency on the openldap package which is not default on unRAID. Sadly I don't have the time at the moment to check out possible negative side affects. The plugin is heavily integrated info the unRAID user management and intended to use only that. For a more ambitious setup it is better and far easier to setup a VM with a more flexible linux distro than unRAIDs Slackware. Within debian and ubuntu for example there are addon packages for proftpd with ldap that can be installed without compiling. Pointing to the shares on your unRAID for data storage should give you what you want without possible adverse effects.
  6. Its a bit hard for me to understand, as I am not a native English speaker. How are the upload folders created? Through the shell console or through the ftp client? As they are both user, group and world writeable, there should be no problems uploading to both of them in theory. Can you give me the full paths of both users DCIM folders on your array? What is the error message, when trying to upload to the nobody users DCIM? Which ftp client do you use? Please try with FileZilla if it works and only then try another client. I'm guessing from your description you are trying to upload not a file, but a folder with 10000+ files within it. I have never tried to upload such a large number of files. I can only recommend trying with a single or a few files first and expanding from that. Also please enable debug logging as described in the link above, to maybe get more information on what is going wrong.
  7. The functionality to edit the proftpd.conf file from the plugins settings page is sadly currently broken. You have to open a shell window and use nano (or any other editor of your choice) to edit /etc/proftpd.conf. If you have your log files on the flash, like your config file suggests, the server will propably run into problems and not start, as the file system of the flash doesn't support access rights and is therefore deemed insecure by proftpd. If you don't want to log into the syslog, I recommend to create a folder on the array to host the log files and set the correct access rights for that. (not world writeable) Make sure you can access the ftp by a normal client (e.g. FileZilla) first before trying more advanced stuff like trying to run some backup software. It might be necessary to enable Debug Logging, to maybe get more information on the problem. See here.
  8. Something like this would have been my guess. It's great you found the cause of the problem yourself. And no, I don't think you should worry. 😉
  9. @Nacrana Its in /etc/proftpd.conf. Just use nano in the shell prompt to edit it. The location given above is where the file will be stored to keep it on reboots. Editing it there is also possible.
  10. That's a bit crazy. But if it works. 🙈
  11. @kricker Can you connect using https://ftptest.net/? Set it to fallback to plain FTP before you run the test. What does it say?
  12. You can download older versions and their dependencies manually from my github account. Download the following into /boot/config/plugins: https://github.com/SlrG/unRAID/raw/87f31b9a223fd2f2b6b414207a2ab5204c1003f8/Plugins/ProFTPd.plg Create a new directory /boot/config/plugins/ProFTPd and download these into the new dir: https://github.com/SlrG/unRAID/raw/87f31b9a223fd2f2b6b414207a2ab5204c1003f8/AppSupport/ProFTPd/ProFTPd-SlrG-Control-1.5.tar.gz https://github.com/SlrG/unRAID/raw/87f31b9a223fd2f2b6b414207a2ab5204c1003f8/AppSupport/ProFTPd/ProFTPd-SlrG-Dependency-1.5_x64.tar.gz Afterwards a reboot of your server should install the older version of the plugin. The new version will show as update under Plugins and in the plugins settings afterwards however. Make sure you have no auto updates enabled and exclude the old version check of it from the "Fix Common Problems" plugin if you have that running. I didn't test it today, but I think that are the required steps. If it does not work, please report back.
  13. @LSL1337 While I certainly understand your frustration that this problem is not yet solved, things are not always as easy to fix, as a normal user might think. It probably won't help to discourage the author even further by being rude. If you know how to solve the problem, please provide a patch or pull request and the author will probably check and accept it. If you don't, please try to be kind, encouraging and understanding, that this plugin is developed in the free time of the author without monetary compensation (at least I think it is). @bonienl I don't have this problem myself, as I don't own NVME drives, so I don't really know, what I am talking about. But if the problem is recognizing if NVME drives are present and which ones they are, it might be a solution to let the user choose drives to be excluded from a list. What do you think?
  14. @wgstarks When trying just now, it works fine in the built in terminal when using .bash_profile.
  15. Copy the .bash_profile to your flash (/boot/config/) and add the following line to your go file: ln -sf /boot/config/.bash_profile /root/.bash_profile This will create a link overwriting the original file and pointing to the new one on the flash. Changing something in the original location will be put on the flash automatically and thus survive a reboot.