Most internet providers will terminate the internet connection periodically, most likely during the night. During this period, the client may fail to connect to the server but after a few minutes, this should be fixed automatically.

The synchronisation is limited to 250 files at a time. The reason is to give other clients the possibility to also access the server. The remaining files will be synced during the next run.

Open the command line with administrator rights and enter the following command: “sfc /scannow”

Automatically, whenever there is a new message.

These buttons will filter your messages. Only messages with a severity high enough will be displayed.

What shall be synced? There is nothing… 🙂

Hidden files will not be synced.

It may happen, that the files “Desktop.ini” and “Folder.ico” appear in the root folder and will be restored on every start of the client. If this happens, setting the folder icon in the Windows Explorer failed. You can deactivate this in the client configuration by setting “SetClientFolderIcon” to “false”.

Max. 200 characters including path and file name.

Yes. You cannot use filenames beginning with the tilde sign “~” (these filenames are internally used for right management) and also the filenames “Folder.ico” and “Desktop.ini” are not allowed.

Sorry, also one limitation: “Rootfolder” is not allowed.

Download the Windows installer and simply run it.

Set the value for the client scan intervall to max. 15 minutes in case, you are using the relay service. The server has a time out and may terminate the connection in case you use longer intervalls.

Re-run the installer. It will detect your existing installation and propose to update it without changing your settings. You should close all apps before.

No. But you need full read/write access in the installation folder and the project root folders.

XML configuration files will be part of the backup (if included in the license). You can restore them from the ZIP archive.

Re-run the setup, choose your new license type and let the setup update your installation.

Use the password generator tool

For security reasons, no error messages are displayed.

Check, if the spelling of the project, user name and password is correct. Is the project really hosted on the server?

You need to manually delete unused clients from the server XML configuration file. Keep an eye on the numbering of the XML tags!

You can use any text editor, you like, but ensure, the files are UTF8 encoded.

The server is able to handle up to 255 parallel connections at a time. But most Windows licenses have restrictions. If you want to use a high number of parallel connections, you need to use a Windows server.

This port must be accessable from the internet. The clients will always first connect to this port and then forwarded to another port by the Windows API.

The Windows firewall should be configured automatically at the first run of the server application. If you are prompted to allow access for the server application, please grant it.

Either you need to configure the router or external firewall in such a way, that it forwards the server listen port to your server, or you use our DNS or relay service.

Go to the Android settins, navigate to battery optimisation and ensure, “just a simple cloud” is set to “not optimised”.

Check the global key.

You may find this warning printed from the “Start” script. This is due to the way, Raspian (the OS of the Raspberry Pi) is configured.
For more information have a look at https://pi3d.github.io/html/FAQ.html in chapter “GLX DRI2 not supported or failed to authenticate”.

What personal data is the Android app handling with?
The app only needs data to log in on your server:

• the name of the client (used for license management on the server)
• the name of the project (used for identifying the correct project on the server)
• your login credentials
• in case you use the relay service:
  • the unique identifier of your server
• in case you use a direct connection to your server:
  • the address and port number of your server

Theses data are saved encrypted in a configuration file located in the app folder on your Android smartphone. They are not shared with any other party.

During a log in on the server, the credentials are transmitted to the server as an AES encrypted data package.