I have been all over these forums, google, etc trying to figure this out. I have a ReadyNas Pro 6. Crashplan Pro has been installed via the instructions provided in this forum. That part went fine with no errors or issues reported.I have installed Crashplan Pro on a Win Server 2008 r2 machine. This machine is set up and backing up just fine.I have been unsuccessful at getting the win server desktop client to connect to the ReadyNas. I have made the changes to ui.properties. I am using PuTTY to set up the SSH Tunnel and can connect just fine. Even with all this set up, when I open the Crashplan desktop client on the win server, I get the local windows machine. Can't seem to get it to come up with the ReadyNas.Any assistance would be greatly appreciated. I am happy to post any needed info.Jason

You need to make an edit in crashplan/conf/ui.propertiesLine 3 needs to be changed from#servicePort=4243toservicePort=4200changing the port number AND removing the initial #Also - when you select your backup folders, you need to select the shares shown under "C", and ignore the top level list (which are actually links).

That has been updated. #Fri Dec 09 09:50:22 CST 2005#serviceHost=127.0.0.1servicePort=4200#pollerPeriod=1000 # 1 second#connectRetryDelay=10000# 10 seconds#connectRetryAttempts=3#showWelcome=true#font.small=#font.default=#font.title=#font.message.header=#font.message.body=#font.tab=In PuTTY, I am creating the tunnel using local port 4200 and mapping to localhost:4243Still connects to the local windows install.Jason

Odd. That is what I've done (following CrashPlan's instructions here: http://support.crashplan.com/doku.php/h ... ess_client) and it works fine. Under Destinations/computers I see the NAS first (labeled "this one") and my local machine second. I launch Putty first and login, then I launch the Crashplan desktop client. Did you try rebooting the PC?

Found a weird quirk. Luckily, I had made a backup copy of ui.properties before making any changes. I was using notepad to edit the file initially. I then went back to the backup file I created and opened it with wordpad, made the changes, and resaved as ui.properties.Now, when trying to connect the desktop engine, I am getting a message that says, "unable to connect to the backup engine, retry?" - this is positive movement. Now, it is either the firewall blocking it, or an issue with the readynas install of Crashplan.As my linux is not very good. Is there a quick check I can do to make sure the engine is running correctly on the ReadyNAS?

if you enter "ps -x" in the NAS command line you should see "/usr/bin/java -Dfile.encoding-UTF-8 -Dapp=CrashPlanSe" as one of the processes.If putty is connected to the NAS, and local port 4200 is still forwarded to localhost:4243, and you are logged in as root, then you should be able to reach the backup engine. The port forwarding is not persistent - it is convenient to save the session settings in putty, so you don't have to re-enter it.

Crashplan Headless | NETGEAR Communities

18 Replies

Replies have been turned off for this discussion

jasont1
Aspirant
Mar 21, 2012
I tried opening a case with Crashplan and they said it was an unsupported setup...which was expected. I may try an uninstall/reinstall to see if that works.
StephenB
Guru - Experienced User
Mar 22, 2012
A bit crazy for them to deny all support when you are following their instructions!

Anyway, there is an alternative method for connecting to the engine here: viewtopic.php?f=61&t=18139&p=348104#p327363
jasont1
Aspirant
Mar 22, 2012
Stephen, you're a freaking genius!

The alternate directions were the key to tip me off. I checked the my.service.xml file and found that the ServiceHost line was already set to the nas IP (instead of 127.0.0.1 or localhost). Due to this, when I was setting up the SSH tunnel using localhost:4243, crashplan didn't know how to handle that.

After changing the SSH tunnel to <NAS IP>:4243, I was able to connect without issue.

Must have done something in the initial setup to change that...not sure...either way, that did it!

Thank you for all the help, it was greatly appreciated!

Jason
StephenB
Guru - Experienced User
Mar 22, 2012
No problem, I am glad you are up and running.
jasont1
Aspirant
Mar 23, 2012
So close...
I can now get to a login prompt, but my username and password are not accepted. I worked with Crashplan support and got them to extend my trial for another 30 days. I can log onto the Crashplan website and two other crashplan windows installs. When I connect the Crashplan desktop agent to the readynas and try to log in with my crashplan credentials, I get an error that the entered information is not correct.

I'm now emailing back and forth with Crashplan support to try to figure it out.
StephenB
Guru - Experienced User
Mar 23, 2012
They should help with that...

Can you log in at their website? (clicking on "my account" at the top).
jasont1
Aspirant
Mar 23, 2012
My bad on this one. I am using Crashplan Pro on the windows side. The linux install I grabbed was for the consumer version. They have different logins. I found this info in the linux config files (OrgType = CONSUMER) and then verified with Crashplan support that this is the case.

I thought I downloaded both the windows and linux installs from the same location...guess not. Going to uninstall/reinstall over the weekend.
jasont1
Aspirant
Mar 26, 2012
Uninstalled CrashPlan from the ReadyNAS over the weekend and installed CrashPlanPRO. After this, the connection worked without an issue. I was even able to follow the tunnel directions using localhost instead of the ip of NAS.

Thanks again for all the help.
To anyone that happens to come into a similar issue, please make sure you are using the appropriate install version (Regular vs PRO vs PROe). Will save a LOT of headaches.

Forum Discussion

Crashplan Headless

18 Replies

Related Content

TIP: CrashPlan Pro 4.9 DOES Work With Headless ReadyNAS Over X

CrashPlan Alternatives

CrashPlan Performance

Crashplan JRE update needed

Crashplan for small business on headless

NETGEAR Academy

ProSupport for Business