Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About JaY_III

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

693 profile views
  1. @SlrG All is well with the latest plugin update. Thank you again.
  2. This is the error I get without the script I posted. Mar 10 08:05:35 unRAID proftpd[9325]: ([]) - notice: unable to use DefaultRoot '~/' [resolved to '/tmp/FTP/']: No such file or directory Mar 10 08:05:35 unRAID proftpd[9325]: ([]) - chroot to '~/' failed for user 'JaY_III': No such file or directory Mar 10 08:05:35 unRAID proftpd[9325]: ([]) - error: unable to set DefaultRoot directory
  3. For anyone looking to get this working with unRAID 6.8.x it is actually fairly simple. First I would like to talk about why this plugin no longer works with 6.8.x as it is currently implemented. Due to the tightening of security in 6.8.x we are no longer able to execute from the flash drive. mountscript.sh no longer is executing and as such the FTP will not have the folder structure require to allow logins and this can be seen in the system log. So we are left with a few options to fix this mountscript not executing. We can manually create the file structure required as defined in the mountscript. However this does not survive a reboot, so other than testing, its not a viable option. The go file, you might be able to use it, but that is not the intention of the go file. You may cause further issues so best to leave that alone. crontab could work, with limitations. You need to implement crontab in a hacky way in order for your scripts to survive a reboot. The easy fix for 6.8.x is to use "CA User Scripts" Install this plugin add new script edit script copy the mountscript.sh into your new script. (#comments can be copied without issues) set to run at "At first array start only" apply either run the script now and your FTP will now work or reboot and test it. That's it, ProFTPD now works in 6.8.x
  4. Love: Docker Engine and KVM Would love to see: TRIM support on the array
  5. Thank you for this correction. I sort of forgot I was in a tunnel while setting up the software.
  6. If anyone is having troubles getting this working, here is what I did to set it all up using OpenVPN From the CA app, click the install button, it will bring up the settings we need to tweak to get this to work Step 1: Port Setup -> Remove : Host Port 3: Container Port: 8080 -> Set : Key 8: <to a free port number you wish to run this container on> Container Variable: WEBUI_PORT" -> Click : "Add another Path, Port, Variable, Label or Device" Set it up as follows Config Type: Port Name: Host Port 3 (or leave blank) Host Port: <same as key 8 port> Connection type : TCP Description: Container Port: <same as key 8 port> ->Edit : WebUI http://[IP]:[PORT:8080]/ (if you don't see this option ensure the advanced view toggle on the top right is enabled) change the port number to <same as key 8 port> Step 2: Download Dir -> Edit: Host Path 2: < location you would like to store your downloads > Container Path: /data Step 3a: VPN Key 1: Yes Container Variable: VPN_ENABLED Key 2: <username goes here> Container Variable: VPN_USER Key 3: <password goes here> Container Variable: VPN_PASS Key 4: Custom Container Variable: VPN_PROV Key 8: <set in step 1> Container Variable: WEBUI_PORT Key 9: (LAN specific, common network is <>) Container Variable: LAN_NETWORK Key 10: (defaults may work for you) <,,> Container Variable: NAME_SERVERS * Set VPN to "no" if you do not wish to setup the VPN at this time Click "APPLY" The docker will now download and unpack however if you have your VPN key 1 set to "Yes" the web interface will fail to load at this time as we do not have our certs setup yet. Step 3b: VPN cert Once the container has unpacked Go to your /appdata location the default install director is /binhex-qbittorrentvpn inside that directory you will see another directory called /openvpn -> Copy your < vpn.ovpn > file here. This is provided by your VPN provider Restart the container Step 4: Web interface config ->Click on the container icon WebUI *Providing you set the webui port in step 1 correctly L: admin P: adminadmin ->Click gear Icon (options) Down Load Tab Ensure the following is set as follows: Default Save Path: /data/ your downloads will be saved to the location set in step 2 I also like to set the following: <checked> Keep incomplete torrents in: /data/incomplete/ <checked> Copy .torrent files to: /data/incomplete/torrent <checked> Copy .torrent files for finished downloads to: /data/incomplete/torrent/done <checked> Create sub-folder for torrents with multiple files <checked> Delete .torrent files afterwards <checked> Append .!qB extension to incomplete files Automatically add torrents from: Monitored Folder | Override Save Location /data/incomplete/torrent/monitor/ | Default Save Location Connection Tab Port used for incoming connections: < as per your firewall/router settings > Web UI Authentication Username: <web UI username> Password: <web UI pass> <checked> Bypass authentication for clients on localhost <checked> Bypass authentication for clients in whitelisted IP subnets : <same as key9 durring setup> *only do this step if you don't want to worry about passwords for LAN (local) users -> Click Save Your Done! Now test everything out. If all goes well you will have a working VPN'd Torrent Client Linux Mint downloaded at my full network speed. Hopefully this helps anyone looking to set this up
  7. mountscript.sh is stored in the plugin directory on your flash drive. Might be a little easier for you do this with notepad++ in windows than with nano or vi over SSH You can enabled sharing of your flash drive by login into unRAID -> Main ->Boot Device ->Flash ->SMB Security Settings Setup the security appropriately for your needs. You can then access it in windows \\unraid-name-or-ip\flash\config\plugins\ProFTPd
  8. Just an FYI Samsung is ending B-Die production https://www.anandtech.com/show/14327/samsung-to-end-b-die-ddr4-memory
  9. You would be best to look for support in the plugin thread. Have a look at my post here: I have gone over how to setup shares and read write access and I believe that post answers your question.
  10. Plugin works perfectly now on 6.7.0 FTP comes right back up on a system reboot. Thank you again @SlrG
  11. We have a problem with the update of the plugin you did yesterday. If you were still using the non beta plugin that does not work with 6.7.0, the update to the 23 May 2019 build will not work. The beta version works great however. Updating the beta to the 23 May 2019 Build works. I have noticed this: When updating the beta ProFTPd-SlrG-Dependency-1.7_x64.tar.gz rolls down to ProFTPd-SlrG-Dependency-1.5_x64.tar.gz From my working state, uninstalling the plugin then installing the from here: https://github.com/SlrG/unRAID/raw/master/Plugins/ProFTPd.plg. Will not work The only way I can get the 23 May 2019 build to work is from 1st installing Beta http://sdevel.de/ProFTPd.plg Then update the plugin However the plugin will not survive a reboot and no longer works Rolling back the update to beta plugin does not work until the system is rebooted We are then back to using ProFTPd-SlrG-Dependency-1.7_x64.tar.gz And all is well again At this time I am required to stay on the 2018.02.05.1 beta build to keep the FTP running.
  12. I wrote a quick blurb before on how I setup shares for FTP users that you may want to check out: Default permissions are deny to the best of my knowledge, so you may have incorrectly set permissions. When you say you have given yourself full root access, are you referring to full Read / Write permissions and not the root of the file system correct?
  13. I also seem to have had some issues with adoption issues. This seems to have fixed it for me. ssh into the AP run this command set-inform http://ip-of-controller:8080/inform I my case I did this set-inform As per my system IP The port being what "Port used for device and controller communication" is set too in my case as 8080 is already in use by another container No other changes were made to the controller What I am not sure is why I had to redo this
  14. On RC5 ftp will not start Removed plugin (reboot) and reinstalled (reboot) and can not get it to start Rolled back to 6.6.7 and FTP starts without issues Upgrade back to RC5 and the FTP will not start I tried the file listed above (ProFTPd-SlrG-Dependency-1.6_x64.tar.gz) and edited ProFTPd.plg and the plugin does not even appear on the server upon reboot unRaid is not spitting out any errors the only thing the unRAID log file shows is Mar 10 01:24:05 unRAID emhttpd: req (3): cmd=%2Fplugins%2FProFTPd%2Fscripts%2Frc.ProFTPd&arg1=buttonstart&runCmd=Start&csrf_token=**************** Mar 10 01:24:05 unRAID emhttpd: cmd: /usr/local/emhttp/plugins/ProFTPd/scripts/rc.ProFTPd buttonstart Mar 10 01:24:08 unRAID sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/SlrG-Common/usr/local/sbin/proftpd -c /etc/proftpd.conf Says ok when starting jails Says ok when starting ProftpD Screen refreshes and status: stopped So its trying to start it, but not other info of what is going on is being shown as far as I can see For what its worth my mount script does run, so we know it gets that far at least
  15. you have me stumped then as I have no issues using either NIC If I turn my bond off, I can assign an IP to eth0 or eth1 and can access my system from either NIC, as i have both wired into my switch.