SlrG

Yes thats correct. The problem is that v5 does not know the Method tag but expects a Run tag. To solve it, I did it this way: <FILE Name="/tmp/&name;-script" Run="/bin/bash" Method="remove"> <INLINE> ARCHTYPE=$( /usr/bin/uname -m ) if [ "x86_64" == "$ARCHTYPE" ]; then # ============================================== # The 'remove' script # ============================================== ... ... Put your remove script here ... fi rm -f "/tmp/&name;-script" </INLINE> </FILE> That way it is extracted on v5 and executed, but as it checks the platform it is running on first, it will not do anything other than removing itself. The error will be gone. On v6 it will execute only when the remove method is called. The Run tag will be ignored if a Method tag is found. At least it worked that way the last time I tested.

See the answers to you other posts. Please don't crosspost.

It should be possible. The proftpd doku says this. So basically if you want to limit a single user, you should use the TransferRate command with user directive in your proftpd.conf file. #Download Limit 640 KB (5 Megabit) TransferRate RETR 640 user SlrG #Upload Limit 640 KB (5 Megabit) TransferRate STOR,STOU 640 user SlrG The limit will only apply to the given user. cheers, SlrG

No and yes. The only sophisticated gui for ProFTPd I found is gadmin-proftpd. That requires gtk support and that has a lot of dependencies on unraid and still requires another pc and x11 forwarding to access the gui. I experimented with that, but its not something that could be easily added to a plugin. Maybe with docker it will come a time that makes it possible. What the config editor gives you at the moment is a textbox, in which you can edit the proftpd.conf file. So you don't need to use an editor on the command line, but can edit it in the webbrowser window. Also it will check the file after you made changes and if there are errors, it'll report the error and the line so you can fix it before saving. If you still want the config editor, you need a webserver on your unraid. On v6 the easiest way is this plugin. The plugin requires you to set a webserver root path and port. Then you point the ProFTPd plugin to that path and port. The editor files will be copied to that path and the editor window will appear on the settings page. If you want to install ProFTP Administrator to this webserver that will work. But you will also need to install sql or maria db on your unraid, as ProFTPd Administrator uses a sql database to manage users. Again this whole setup is possible but a hassle to get it going. And in my opinion the gui has too few features to justify the work.

No problem. I'm glad you got it working.

Are you sure the path in the description of the second user is correct? /mnt/mnt/ seems wrong to me. Please try with only one /mnt/. Don't forget to restart ProFTPd after changing the description.

That is a somewhat short error description. I need more detail. What are the names of the ftpusers you created? What are the comments you saved with those users. Did you restart ProFTPd after creating the users?

The new version is online now. For installation instructions please refer to the first post. Please report here, if you encounter any problems.

Still a plugin for now. I did some extensive docker testing and while it is possible to create a docker with proftpd, the unraid based usermanagement, like it was possible with the old plugin/and will be with the new one, would not work. Also it is quite hard to get ftp where after the initial connect on transfer a whole range of ports is used, to work with docker. I really would have liked to go the docker route, but in the end I decided against it.

I finally had some free time and started working on a new v5/v6 version of the ProFTPd Plugin for unRAID. It's not finished yet, but it will be soon. So stay tuned if you are interested.

There already is a glftpd docker in the docker repository (look here). It is based on phusion/baseimage, like most other unRAID dockers are. So it should be easy to create an unraid template, shouldn't it?

On my system the S3Sleep plugin still doesn't display the sleep button in the array operations tab. dynamix.cfg exists, but instead of sleep="plugins/dynamix.s3.sleep/Sleep.php", sleep="1" is added by the plugin. Manually changing it works, but only until reboot. Then both lines will be present in the file: sleep="plugins/dynamix.s3.sleep/Sleep.php" sleep="1" Manually removing the sleep="1" will make it work again until reboot.

I would not recommend you to do that. There is a reason that newer beta versions exists. A lot of problems have been fixed on the way. What do you want to do with the ftpserver? Maybe the vsftp that already comes with stock unraid will be enough to help you until a new version of the plugin or an proftpd docker is released?

Well the thread title says this plugin is for version v5.0.5 and v6b6 only. So it is not compatible with the changes done to the plugin system in the newer betas. It won't run and cause problems for your system. Sorry. The only way would be to adapt it to the plugin system of the newest unraid version. If I have time, I'll have a look at it again. But at the moment I just don't have that time.

Did you already define a user/users with ftp access? (See the README.txt on how to do that). Restart the plugin afterwards. Then you will have to decide if you want to connect from your local network or from the outside. Please always check if logging in works from the local network, before trying to get it working from the outside. Also be aware, that direct outside login is potentially dangerous. In both cases log in to a ftp service is done via a ftp client software (e.g. FileZilla). You give that the name of your server or your servers ip and the port you have set for the ftp service (default is 21). It will then connect and ask for the name and the password of an user you created for ftp access. It should then login to the homedir you defined for that user. If you want to access your ftp service from the outside you have to check if you get a fixed ip from your provider, or if not, get yourself some dynamic dns service, that provides you with a fixed name you can use to access your router. In the router you then setup a vpn and once you have the vpn tunnel running you can connect like you were in your local lan. Another (less secure) way is to forward a port from your router to port 21 on your unraid server. On the router don't use port 21 but a different higher one. Depending on your router the forwarding of additional ports for passive ftp will be necessary. You can than connect from the outside with the client software using the dynamic dns name and the higher port you defined. Please excuse the lengthy explanation, but your question leaves much room for interpretation in what you really want to do. Also if what I'm writing sounds way to complicated for your taste, it might be better to not use ftp or start with a deeper research on how to use it and its security implications.

I'm happy you got it working.

You propably need to masquerade the unraid servers address with the one you get from noip. (See here: http://www.proftpd.org/docs/howto/NAT.html) You have to add a rule MasqueradeAddress ftp.mydomain.com # using a DNS name PassivePorts 60000 65535 # These ports should be safe... replace the ftp.mydomain.com with your noip dns name. Also you'll have to define and forward the passive ports in your router.

Thank you for the syslog. As far as I can see, the plugin installs correctly. Your user setup seems to be fine too. Reading your log and your error message above, the user logs in quite fine. So the non-ASCII chars message is propably not the problem. I just noticed I have that too in my connect message. (Normally it scrolls by so fast I've never seen it before and as everything worked, I've had no reason to look for it.) What seems to be the real problem is this: The connection times out, because something goes wrong with the ip address the server replies with. What FTP client are you using? Can you try to connect in the shell of your server? Enter "ftp yourservername" then enter the username and password and once connected enter "dir"? Does it work then?

Okay, then at least it should work normally. Do you get any syslog messages when logging in? Please post the full syslog, after booting your server and logging in and out of the ftp. Also please describe the directory structure a little, do the directory names have special chars in them? How did you create them? Remote from some other system? What OS are you using there? Please post a screenshot of the restricted ftp users details. Do you have other plugins running? Which ones? regards SlrG

What version of unraid do you use? If you are on v6b I would recommend to not use the plugin for now.

@maspiter: I think the device nodes might change on reboot so the excluded drive outside the array could become one of the array drives suddenly. It propably would be better to let the user define outside drives by their drive id.

Before we start troubleshooting this, I think you should upgrade your server to beta 10a ASAP! Beta 7 and 8 have a DATA CORRUPTION ISSUE and could damage your data! Once you have done that and checked your data, please post a full syslog when booting your system with the plugin enabled. This should give me a first idea what is going wrong. Also the newest betas introduce a new plugin framework and the plugin is not yet adapted to support this. I'll have a look at this in the future, but it'll take some time, as I'm rather busy in real life at the moment.

I did not test it on other betas, so I can't say for sure, but in theory it should work without problems. Just give it a try and report your findings. If you have trouble, we can try to solve them together.

I added a modified version, which should work on v6b6. Please give it a try and report problems. For sql support maria db should be supported. The plugin is still in old unraid plugin design structure.

I'm still on V5. Over the next week I will give V6 a go again. If the s3sleep problem I had on the last try is gone and it works for me, I'll look into the plugin. But I'm not really sure how the best future would be. There are several options. 1) Try to get the plugin to work with V6 as it is now. It might be meaningless work, as changes in the next beta might break it again. 2) Wait for the V6 plugin system to be finished and convert the plugin to use that. 3) Drop the plugin route and create a docker container (There might be already something available? Did you look into that?) 4) Let people use a vm where it is much easier to install proftpd including graphical management tools like gadmin-proftpd. For all ways there are pros and cons. What do you think?