Enable SSH on LinkStation Stock Firmware

Enabling SSH on the LinkStation is simpler than you might think and opens up a world of functionality (and nerdyness) that you never had before – All this with no firmware flashing which ultimately means no data loss and no risk of bricking your box.

My motivation to enable SSH came about when my older LinkStation (a 500GB HS-DHGL) was doing a Disk Backup to my newer one (a 2TB LS-WXL) and it just seemed to be taking forever. It turned out the backup had hung part way through and the only official way to fix this problem as listed on Buffalo’s support website was to reset the box back to factory settings – That’s a bit ridiculous in my opinion but there is a work around, see this post here for more information on how to unstick a backup.

The activation process is done by a program called ACP Commander which is a command line tool that can be a little confusing to work at times with its lack of user friendly interface (if you search for this online you’ll see what I mean) however by chance I came across a reworked version that has a decent interface and is fairly easy to use.

Enabling SSH

The following guide will assume that you are on the same network as your LinkStation and are able to access it freely as you normally would day-to-day,Β  also if you want to keep your warranty with Buffalo do not continue!

  • Download ACP Commander GUI for Windows (.EXE file)
  • Run your newly downloaded file and you should see a screen similar to the one below:
  • Select your LinkStation IP address from where it says Select LinkStation, then enter your password where it says Admin password and press Enable SSH
  • After a couple of seconds you will be shown a SSH enabled OK! message as seen below:
  • The next step is to set your root password for SSH, click Set root PW, type in a password and then press OK and you will see another message like the one below:
  • Now head to your favourite SSH software and connect to your box! If all is well you will see something similar to this:
  • That’s all you need to do to enable SSH!


  • This method is proven to work on both Windows and Mac for the following models/firmware: LS-WXL/v1.68, HS-DHGL/v2.11, LS-QVL/v1.64
  • Common out of the box commands include: top – process viewer, vi – text editor, cp – copy files, mv – move files
  • Mine and my friends newer LinkStations had HTOP installed – Epic!
  • Enabling SSH will no doubt void your warranty with Buffalo but who needs that anyway?!
  • I didn’t create the program recommended and take no credit for it
  • Finally, if you could let me know if you encounter any problems or can confirm if this works for other models I’d be grateful
  • Thanks to Callum for confirming this works on the LS-QVL and Michael for confirming this works on the TS-X/R5 with version 1.66 firmware

Search terms:

  • enable ssh on buffalo linkstation ls10d654
  • buffalo linkstation ssh
  • buffalo linkstation 220 smb2 diabled
  • ls -al ~/ ssh
  • linkstation putty connection refused
  • buffalo nas ssh
  • enabling smb2 on buffalo linkstation
  • https://nerdkey co uk/guides/enable-ssh-linkstation-stock-firmware/
  • ssh to linkstation
  • add ssh to ls210d

41 Replies to “Enable SSH on LinkStation Stock Firmware”

  1. It didn’t work in my case (LS-WXL, firmware 1.71) The output in ACP shows OK for ssh and the root password, but trying it out with Putty and MobaXterm results in a sudden end of the connection. It’s a pitty for I also donnot care about the warrenty and just want access the drives easily

    1. It did work (and continues to work) on my LS-WVL (which is very similar to LS-WXL; the only difference is a stronger processor and larger memory) with firmware 1.71. SSH client is Putty release 0.62)
      Note the following general detail: you can edit the admin user on the linkstation and rename it if you so wish. The acp application uses the name admin, so if you changed the name, you need to change it back to the stock “admin”.

    1. Hey Ben,
      No problem at all! Well that sounds worthy of a post of its own, never been brave enough to even try that yet!


  2. hello i am trying to enable ssh on my LinkStation LS220DE Version 1.65-0.12 but it gives me
    Please note, That the current support for the change of the IP is currently very rudimentary.
    The IP Has Been Set to the given, fixed IP, DNS and gateway However have not Been in September Use the WebGUI to make appropriate settings.

    you know how I can fix
    thank you

  3. Ok I rooted my TS-X/R5 box w/FW1.66 and got SSH to work….I can root in now…

    Now what do I do?

    I want the lastest and greatest Debian or Gentoo to run on the box.

    But Buffalo….well….they “Buffalo’d” vi. And it can’t edit anything.
    /etc/apt/sources.list points to their private server and a custom flavor of armel for its “main”

    So all “root” is good for is to spin my wheels going nowhere…..

    I know it can’t be like that…..but the System is “Buffalo’d” and I got to get another firmware on here….and herd out the buffalo…

    Anyone on here can help?

    Nas-central.org is well…nearly defunct….And I don’t really know if anyone (other than me) still haunts the site looking for Terastation stuff….

    I’ve got to get this box to work right….

  4. Thanks you, I confirm this app work on LinkStation LS-WVL firmware 1.71, if this app not detect your LinkStation try: disable firewall on local pc, install NAS Navigator tools, reboot PC… if still not working, try on another pc.

  5. ACP seems to work, but I get connection refused when SSH’ing. Enabled AFP in the Buffalo GUI but no difference, set up a port forwarding rule just in case it was a router problem, still no good πŸ™

    Connecting from a MacBook (MacOS Sierra) using terminal πŸ™

    Strange, because it worked on my previous Buffalo NAS.

  6. This method works on the LS-CHL2.0TL model running the latest stock firmware v1.71. Although the change won’t survive a system reboot using only the above method. In order to make the change survive a system reboot you will also need to modify the rcS shell script located in the /etc/init.d directory:

    Basically, find this line in the script:

    And change it to this:
    start-stop-daemon –background –start –exec /usr/local/sbin/sshd

  7. I am getting the following error messages when I run the java on my Mac (running OSX 10.12.5):

    Exception in thread “main” java.lang.NoClassDefFoundError: acp_commander/jar
    Caused by: java.lang.ClassNotFoundException: acp_commander.jar
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

    Any ideas, am I missing a command line?
    I have tried

    java acp_commander.jar -t

  8. Hi All,

    Acp commander is working fine, I enabled the ssh and set the password for root.
    whenever i trying to access my terastation via putty its giving Network error: Connection refuse.

    request all to assist me.

    Thanks all.


  9. This may be a stupid question since scp makes use of ssh to do it’s thing. But since this puts ssh in place, does that mean I can assume that I’ll also be able to scp my Plex library to it?

  10. Excellent tool and saved me a great amount of time. It worked on my Buffalo LS-WVL with v1.73 Firmware. I was able to successfully grow my partition from Stock 2TB HD to 3TB HD rebuild after a HD failure.

  11. Works like a charm on my LS-WXL. I had to set the root password and I am logging in with root, even if I have a different admin user.

    cat /proc/mdstat is giving me finally the status of teh RAID scan. I takes ages for a 1 TB RAID 1. Any idea why?


  12. ACP Commander is not finding my drives (LS-CHCLA9 and LS-XL138). What port number should I be using? The photo in the original message is too fuzzy to read.

  13. Works great on LS-WXL (v1.73) (Thank you!) but on LS220D (v1.67) on same network I get OK response to Enable SSH and to Set Root PW but PuTTY gets Connection Refused (no prompt for login). Any ideas?

  14. LS220D firmware 1.68 didn’t work. I tried updating hte firmware to 1.70, but same result.
    When trying to SSH, I get
    ssh: connect to host xxx.xxx.xxx.xxx port 22: Connection refused

    Anybody has an idea?


  15. LS441 on latest 1.85.0 – also no go..
    ACP finds connects and says SSH good to go as well as set Root both come back good..
    SSH is refused on connection… bummer…

  16. figured I’d update…
    used this link to manually run the commands – theirs suggests rebooting at the end as its updating the /init.d/ and setting up the service…
    removed https to avoid link issues – but good info.


    just fyi after setting that up my LS441D now has SSH…
    thx and heads up for some of the units!

Leave a Reply