Regibox Faq

More FAQ on the regify homepage.

Technical FAQ

I have problems, can I do some debugging?

Yes, please take a look at the regibox trouble shooting pages.

Is it possible to redirect the regibox root folder?

Yes, there is a chance to set this to another location. Follow this guide:

1. Stop regibox manager (right click on the ToolTray icon and close the program).
2. Move the whole regibox root folder to the new location (incl. all subfolders). Do not copy, please move the folder and files.
3. Edit the regibox.ini:
   1. The file is located in
      • Windows: %APPDATA%\regify\regibox\regibox.ini
      • Linux: ~/.regify/regibox/regibox.ini
      • Mac OSX: ~/.regify/regibox/regibox.ini
   2. Change the "boxRoot" entry to point to the new root. The path needs to end on backslash (Windows) or slash (Linux, OSX).
4. Re-start regibox manager.

There are a few limitations for the location of the new regibox root folder. Please respect.

• Do not point to a location which is not having full read/write/delete access permissions for the user.
• We do not recommend to use a network share as regibox may become slow and sync may be not reliable. If you do so, please activate network mode in regibox manager settings.
• regibox is only accepting one regibox root folder. You can not run multiple instances of regibox to get more root folders.
• We recommend to never point multiple regibox managers from several computers to the same network share!

Is it possible to run regibox as a Windows service?

There is a daemon/service version available as SDK (Software Development Kit). It's named regiboxd and is available for Linux and Windows (x64). It allows the unattended use of regibox including API for automated processing. This is not to be confused with a desktop version of regibox. It does not offer GUI. Please contact support(at)regify.com for getting access to this SDK.

If you like to run the regular regibox GUI version, there is no serviced option available. You may consider software like AlwaysUp, but we have no experience with it and can't support you on this. It may be needed to make sure that no second instance is ran at any time in the same user context. Eg for running regibox manager to handle the configuration, the service would have to become stopped previously. For sure, you may need to test this carefully before production!

If you are willing to auto-login a session on your Server, please note that if Windows starts to the Desktop directly, it normally also auto-starts the regibox Manager by default. At least, the setup already adds it to the users auto-start during installation. If this fails for you, you may want to run regibox manager by yourself on Server startup together with the comand-line switch -m for a minimized start.

By the way, you can find the possible command-line options by running regibox manager executable using -h (for help).

How to execute a silent regibox setup?

Simply call the setup with the /silent 2 switch (Windows only):

regibox-1.3.2-4433.exe /silent 2

How to create a logfile for the installation process?

You can call the regibox setup file with the /logfile switch (Windows only):

regibox-1.3.2-4433.exe /logfile

This will create a file "Logfile_[ProductName]_MSI.txt" in your system %TEMP% folder. You can also combine this with the /silentex switch, if you like to get more information about the silent installation.

regibox Manager to regiboxd migration

Sometimes we are asked about the best way of migration from regibox Manager to regiboxd. The way with the least effort is to stop regibox Manager and assign a regiboxd session to the existing database.

How to migrate

Please note that the path described here only works if you migrate within the same major versions of regibox Manager and regiboxd. The path is described for regibox Manager version 1.5.3 on Windows.

1. Stop regibox Manager (Tray icon, Exit).
2. Uninstall regibox Manager using System control or the uninstall option from Windows start menu.
   • Please note that this will not delete the configuration or any data inside of regibox root folder.
3. Determine regibox configuration folder:
   • Typically this is %APPDATA%\regify\regibox\.
   • Note the full path!
4. Rename config files. Use file explorer and go to the regibox configuration folder. In there:
   • Ensure there are no files with extension .sqlite-shm or .sqlite-wal! If you find such, another regibox manager or regiboxd is running on this folder! This is a source of massive errors. Please stop and uninstall any other regibox Managers and regiboxd services.
   • Rename regibox.ini to regiboxd.ini.
   • Rename regibox.sqlite to regiboxd.sqlite.
5. This is the best moment to make backups.
   • We suggest you to make a backup of the regibox root folder and the complete folder with regibox configuration.
6. Download and install regiboxd with standard configuration.
   • IMPORTANT: The installation tool adds the regibox tools to your PATH environment. So you can run the tools from any location in the command shell.
   • IMPORTANT: You can find the regiboxd documentation PDF in the installation folder (usually C:\Program Files\regiboxd).
7. Open a CMD prompt using Administrator permissions.
8. Type the following to register a new instance to the existing regibox Manager configuration:
   • The used path for -c is the one gathered above for regibox configuration folder.

   regiboxd -c "C:\Users\regify\AppData\Roaming\regify\regibox" -i "instance-1" -d "Migration instance of regiboxd"

9. Get a list of the services for validation using

   regiboxd -L

10. Verify the correct functionality using

    regiboxctl -c "C:\Users\regify\AppData\Roaming\regify\regibox" -J "{'op':'getBoxInfo'}" -p

11. You're finished

We strongly suggest you to verify synchronization now. Place some test file into one of the regiboxes and verify synchronization on the other members of this regibox.

Some useful calls

Turn on local copy for all files and folders of given regibox uid:

   regiboxctl -c "C:\Users\regify\AppData\Roaming\regify\regibox" -J "{'op':'localOnOff', 'uid':'srp79f915967u3doyd8o7orfikjyn5d8', 'filePart':,'isOn':1}"

Turn debugging on and off:

   regiboxctl -c "C:\Users\regify\AppData\Roaming\regify\regibox" -J "{'op':'diagnostics'}"

Stop and remove regiboxd service named "instance-1":

   regiboxd -u "instance-1"