CrashPlan updated to 4.3 and now my GUI will not connect.

My symptom was that the GUI only showed a free account status, with "sign up" next to Crashplan Central. The issue is the same - the gui was not connecting to the NAS service.

I applied sdouek's fix, but it wasn't enough. I also needed to edit C:\ProgramData\CrashPlan\ui_username.properties

It had servicePort=4243, but I needed servicePort=4200. The original ui_properties still exists in c:\Program Files (x86)\CrashPlan\conf\ui.properties so you can confirm the service port you need by looking there.

BTW, The upgrade to 4.3 happened yesterday it was applied automatically to both the NAS and the GUI. Cloud backups continued as usual, the only thing that was lost was the connection between the gui and the server.

I assume that people are installing Crashplan without the need to tunnel via ssh. You can do away with the tunneling by editing my.service.xml on the NAS to your NAS ip address and just put in your address in the ui.properties file located on your PC.

But either way works.

StephenB do you see any cons to the above fix ?

sdouek wrote:
I assume that people are installing Crashplan without the need to tunnel via ssh.

I've just left it at tunneling. The GUI is fine as far as it goes, but I like to look at the tail of various logs also, so I'm logging in with SSH anyway.

sdouek wrote:
StephenB do you see any cons to the above fix ?

No cons, and the files were just where you said they were. It just wasn't enough in my case because the upgrade also disrupted the tunnel. Your post actually made solving my problem much faster, since it pointed me to c:\ProgramData\Crashplan.

As a practical matter, Windows explorer can misbehave on files that start with . If that happens to you, you can use the windows command shell to rename files.

sdouek wrote:
EDIT: Configure your ui.properies file on you PC appropriately. i.e. sevice port should be 4200 if you are using ssh to tunnel or service host should be changed to your NAS ip adresss if you made the proper changes in the my.service.xml file on you nas.

Sorry, I missed an important detail...

c:\Program Files (x86)\CrashPlan\conf\ui.properties still had the correct service port. The 4.3 Crashplan GUI is apparently ignoring that port. So if you are using tunneling you need to edit C:\ProgramData\CrashPlan\ui_username.properties, and configure the same service port there.

I checked my C:\ProgramData\CrashPlan\ui_username.properties the port was set to 4243 and in c:\Program Files (x86)\CrashPlan\conf\ui.properties the port was set 4200 and I wsa able to connect via ssh tunneling.

my.service.xml on the NAS was set to my NAS ip address, I don't know if that is what you have or is it set to 127.0.0.1 or sometimes when you change the settings in CrashPlan GUI on the PC you have to end the process tree in task manager, it may make a difference ?


C:\ProgramData\CrashPlan\ui_username.properties, It had the following:

#Sat Jul 11 15:25:21 EDT 2015
expandedDestinations=1\:42
servicePort=4243
window=0,0,1920,1024

c:\Program Files (x86)\CrashPlan\conf\ui.properties
#Fri Dec 09 09:50:22 CST 2005
serviceHost=XXX.XXX.XXX.XXX
servicePort=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=

Shall I add this to the guide? I don't see the advantage of using a tunnel...

I didn't end it with taskmanager; I right-clicked on the icon in the notification tray, and selected exit.

c:\Program Files (x86)\CrashPlan\conf\ui.properties has servicePort=4200 and serviceHost commented out.
servicehost on the NAS (my.service.xml) is 127.0.0.1; serviceport is 4243

C:\ProgramData\CrashPlan\ui_username.properties now has servicePort set to 4200

tony359 wrote:
Shall I add this to the guide? I don't see the advantage of using a tunnel...

I believe the code42 guide does set up a tunnel (certainly it did at one point).

I'm running ssh anyway (since I tail history.log.0 and backup_files.log.0 first, and often that's all I do). So I use the tunnel method.

But I think the main reason sdouek posted is because he got a different result than I did with 4.3.0. My tunnel didn't work until I changed C:\ProgramData\CrashPlan\ui_username.properties. Sdouek's tunnel worked w/o making that change.

So many ways to skin a cat. I guess they both work.

Why would you want to skin a cat? ;)

I'll add the note on the bottom notes. Stephen, yes, Code42 mentions the tunnel but for the average user using SFTP is so much easier. That way you don't need to learn how to use Linux!