NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Tutorial to install CrashPlan (updated August 2016)
Hello everyone, As I have reinstall CrashPlan on my ReadyNas today. I thought I will share with everyone my updated notes. Feel free to comment to improve this step-by-step. Maybe a clever person...
jclaracq wrote:
Bogus,
I just checked again. I can connect to the CrashPlan of the NAS from the GUI of the client only if the ui.info port is set to 4243 !! Thus for me it works like that:
My ReadyNAS /var/lib/crashplan/ui.info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
You need to leave the ports at 4243 because you aren't tunneling through putty. I always start with putty myself, so I can access the crashplan logs, etc directly from linux - and then launch the client if there's something there I want to see or change. So 4200 works for me,
Also, I don't think you need to change the IP address on the NAS - 127.0.0.1 (localhost) should work too, and is easier to manage overall (fewer things to touch later if the IP address changes). Your method does require setting the NAS IP address on the client (and mine requires leaving it alone).
jclaracq - if you want edits to the main post, then let me know what they are - I can apply them for you.
Also, you might consider listing both the putty and direct configuration options in the main post, so both are documented.
StephenB wrote:
jclaracq wrote:Bogus,
I just checked again. I can connect to the CrashPlan of the NAS from the GUI of the client only if the ui.info port is set to 4243 !! Thus for me it works like that:
My ReadyNAS /var/lib/crashplan/ui.info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
You need to leave the ports at 4243 because you aren't tunneling through putty. I always start with putty myself, so I can access the crashplan logs, etc directly from linux - and then launch the client if there's something there I want to see or change. So 4200 works for me,
Also, I don't think you need to change the IP address on the NAS - 127.0.0.1 (localhost) should work too, and is easier to manage overall (fewer things to touch later if the IP address changes). Your method does require setting the NAS IP address on the client (and mine requires leaving it alone).
jclaracq - if you want edits to the main post, then let me know what they are - I can apply them for you.
Also, you might consider listing both the putty and direct configuration options in the main post, so both are documented.
Sorry my bad.
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.123
That is what I have too.
Regarding "the IP address on the NAS - 127.0.0.1 (localhost) should work too"
I doubt it (but don't know for sure), because it might only listen to itself (hence localhost). Chaning it to 0.0.0.0 makes more sense, in particular when using DHCP as the IP address of the ReadyNAS might change.
Stephen can you also attach files to my or the 1st post? These .so files are required for ARM.
Bogus wrote:
Regarding "the IP address on the NAS - 127.0.0.1 (localhost) should work too"
I doubt it (but don't know for sure), because it might only listen to itself (hence localhost). Chaning it to 0.0.0.0 makes more sense, in particular when using DHCP as the IP address of the ReadyNAS might change.
Perhaps just try both and report back?
Bogus wrote:
Stephen can you also attach files to my or the 1st post? These .so files are required for ARM.
I can, but I am thinking it would be better if you and jclaracq would collaborate on revisions to the first post, and I can apply those.
Then I can add an "EDIT" note, so people will know they won't have to scroll through the thread.
Seems the latest CP release (4.8) has royally broken things - they now require Java 8 and the service will crash upon attempted to start with Java 7 still loaded. I was able to get the Oracle JDK 8 embedded installed on my RN204 but am still having issues with the service properly starting - it complains about authorization or something along those lines. I also had to replace libjtux.so with an ARM-compiled version because it was bombing on that too since the upgrade presumably overwrote it. It's irritatating that CP still refuses to support ARM platforms - there seems to be a good number of users backing up data from their ARM-based NASes (not just ReadyNAS but Synology and QNAP and probably more), and I'd say this is a pretty strong use case for a service like this.
Which firmware are you running?
Do you see this problem on 6.6.0?
In 6.6.0 we have upgraded the core OS from Debian 7 to Debian 8.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
