So, when I installed the plugin, I had to modify the run.conf twice -- once for the update from 3.5.x to 3.6.x and again from 3.6.x to 3.7.
The several things I really had to do to get this fixed was:
1. Made /etc/rc.local (set perms to 755 so crashplan autostarts) to:
cpuset -l 0 /usr/local/share/crashplan/bin/CrashPlanEngine start
2. Start up the Crashplan Engine by
/etc/rc.local
and let it update... and crash...
3. Editted /usr/pbi/crashplan-amd64/share/crashplan/bin/run.conf per:
https://forums.freenas.org/index.php?threads/crashplan-plugin-wont-start.24243/#post-149005
4. Do step #2 again
5. Do step #3 again
6. Edit /usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml and change 127.0.0.1 to 0.0.0.0 *
7. On your desktop, edit the C:\Program Files\CrashPlan\conf\ui.properties to uncomment serviceHost of the crashplan jail and uncomment servicePort.
8. Add Storage to your jail so you can backup stuff
* -- Major Potential Security Hazard -- you are letting the whole network in your CrashPlan server.... they can do very mean things to you; so be very careful here!