FTP Authentication not working on my cloud?!

My Cloud OS 3 Personal & Network Attached Storage My Cloud
1

So, I’m not sure what changed, but randomly I can’t access the FTP shares anymore. I can ping the 21 port externally and internally, and I get an authentication prompt when I go to the FTP://IPadress:21, but no user can access, even the root UN and PW. I’ve tried to create a new user with NO password and it still isn’t working.

Now, I followed this WD guide to re-enable the FTP function:

http://support.wdc.com/KnowledgeBase/answer.aspx?ID=2680

it says “Private Shares have FTP disabled by default. In order to enable FTP for a specific Share, go to Shares, select the Share, and click on the toggle button for FTP to change it to On.” however, I’m not seeing the FTP function on the shares page on my private shares. I also have public shares enabled as well.

I’ve tried to disable and renable the FTP function.

Yes, I’ve tried to reboot the NAS.

I’m pretty sure it’s an authentication problem. Anything I should try?

Thanks,

2

Root is not enabled for FTP.

  1. Which exact device do you have?
  2. Firmware?
  3. FTP://IPadress:21 ← from which client? Windows Explorer?
  4. Were you trying to access locally or externally (with proper port forwarding, else you might end up trying to connect to the router’s FTP if it has one)?
  5. Any other mods done?

Try using the same account username/password you use to view the WD Dashboard, open the command prompt and test: ftp wdmycloud

You should be able to see the response code. Then check the log, tail -f /var/log/vsftpd.log;.

3
  1. I have the WDMyCloud 3TB
  2. WDMyCloud v04.04.03-113 : Core F/W
  3. From ANY client, windows, chrome, ftp client software, doesn’t matter, same result
  4. I’ve tried externally and internally, same problem on both.
  5. I’ve made a few mods via SSH, but nothing with FTP

Yes, Ive tried using the ADMIN account, and it doesn’t authenticate.

Here is the log:

WDMyCloud:~# tail -f /var/log/vsftpd.log;
Mon May 30 16:28:41 2016 [pid 2] CONNECT: Client “192.168.1.1”
Mon May 30 16:28:43 2016 [pid 1] [seanvree] OK LOGIN: Client “192.168.1.1”
Mon May 30 16:33:27 2016 [pid 2] CONNECT: Client “192.168.1.12”
Mon May 30 16:33:28 2016 [pid 1] [seanvree] OK LOGIN: Client “192.168.1.12”
Mon May 30 16:33:32 2016 [pid 2] CONNECT: Client “192.168.1.12”
Mon May 30 16:33:33 2016 [pid 1] [admin] OK LOGIN: Client “192.168.1.12”
Mon May 30 16:37:00 2016 [pid 2] CONNECT: Client “192.168.1.12”
Mon May 30 16:37:01 2016 [pid 1] [admin] OK LOGIN: Client “192.168.1.12”
Mon May 30 16:37:05 2016 [pid 2] CONNECT: Client “192.168.1.12”
Mon May 30 16:37:06 2016 [pid 1] [seanvree] OK LOGIN: Client “192.168.1.12”
Mon May 30 16:37:30 2016 [pid 2] CONNECT: Client “192.168.1.12”
Mon May 30 16:37:31 2016 [pid 1] [seanvree] OK LOGIN: Client “192.168.1.12”
Mon May 30 16:37:40 2016 [pid 2] CONNECT: Client “192.168.1.12”
Mon May 30 16:37:40 2016 [pid 1] [admin] OK LOGIN: Client “192.168.1.12”

SO, it says “OK”, but it just keeps re-prompting me for the UN and PW, no errors.

4

What mods (all of them) have you made via SSH?

5

Umm, there’s too many to remeber, but it was working for 3 months until now…

But the latest mods I made were the following:

Changed umask to 0000; in etc\profile

Also changed:
Edit nano /etc/exports
/nfs *(rw,all_squash,sync,no_subtree_check,insecure,crossmnt,anonuid=0,anongid=1000)

exportfs -a;.

“/NFS” is my root directory where I keep everything.

6

What happens if you undo the recent mods you made just prior to or the day of the FTP not working properly?

There is a good probability one of the mods you made broke FTP.

7

With all do respect, there’s no way these “mods” have anything to do with the FTP function.

also, It’s not really possible to “Undo” these actions either.

8

With all due respect… how do you know? Your device worked fine, you made some mod changes at some point, now FTP doesn’t work. If you’ve done a 4 second reset and a 40 second system restore (both may affect certain mods), ensured FTP is enabled through the Dashboard, and you’ve eliminated the possibility that it is the FTP client software or local network that is causing the issue, then it leaves the mods you’ve made to the My Cloud as the potential cause.

Because of the way the My Cloud firmware has been coded by WD it is possible that a mod one makes to something they think is unrelated to FTP may or could actually impact or affect FTP. Especially if any of those mods performed via SSH touches user or folder permissions.

9

JFYI vsftpd login root path is /nfs. I don’t really use NFS that much so not sure if changes you did affects the FTP on MyCloud. Try reverting see if it helps:

nano /etc/exports;

/nfs *(rw,all_squash,sync,no_subtree_check,insecure,crossmnt,anonuid=65534,anongid=1000)

exportfs -a;

Remove the umask in profile, exit the shell, relogin then, service vsftpd restart;

10

On my v4.x My Cloud both the anon root and local root are /nfs per the /etc/vsftpd.conf file.

anon_root=/nfs
local_root=/nfs
11

Yeah, to be honest, I go so frustrated, the NFS permissions are more important to me than the FTP function.

Plus, I just used my Windows Server as an FTP server with passthru authentication to the NAS using MKLINK. it’s actually a better way of doing it.

Whatever.