I don't know either who has developed the DLink addon.

But installing Ubooquity manually on a NAS should not be complicated provided you have some knowledge of the Linux command line. The only problem could come from specific features of the different brands of NAS.

There are already tutorials for Synology and Asustor NAS on the wiki.

Thanks for the detailed report.

I already know that Ubooquity has performance issues for some users and I'll try to understand and fix them.

Without these problems, I'd says that a few hundred megs of memory should be enough.

The problem is that you are running Ubooquity from the system32 directory, which is not writable as this is a system directory (Ubooquity needs to write some files in its working directory to work properly).

This should not happen with a proper Java installation. You file association for "jar" files has probably been altered one way or another. What I mean by that is that your problem is not specific to Ubooquity but will most likely happen with any jar file you try to run by double-clicking on it.

A few ideas to fix or work around the problem:

• Uninstall and reinstall Java
• Or create a shortcut to the jar file, edit the shortcut to specify the working directory (the "Start in" field) you want (the one where the files will be created), then double-click on the shortcut

By the way, Ubooquity.jar is the program itself, not the installer. Ubooquity does not need to be installed, it just works in the folder of your choice. But not in System32. ;)

I've never done it, by I guess you should try to run it as a service.

The log file is rolled and zipped when it reaches 1MB.

You can customize the logging policy.

Here is a tutorial to change log line format, but you can customize all logging parameters.

Depends on the problem the current size poses.

What's the size of your DB ? (for how many files ?)

I thought a bit more about it and found it hard to add meaningful debugging information as the security mechanism involves database queries and thus might depend on what is inside your database.

Would it possible for you to send me:

• your database file (ubooquity-4.h2.db in your working directory)
• your settings file (preferences.xml in your working directory)
• the password of a user for which you have the problem

Ideally on a small collection, so that the database is small enough to be sent by email.

And with a dummy password.

My address: tom at vaemendis dot net.

(putting everything in a zip file stored somewhere on the web will do too)

I'll post here the answer I sent you by email so that other users can build upon it if they have other ideas.

Installation directory (where you put Ubooquity.jar) and working directory are not necessarily the same. It depends on where you launch Ubooquity from.

Running any application in a system directory is not a good idea, your working directory should be a user directory you have created somewhere in your own files (not the OS files), and for which the user running Ubooquity has writing permission.

To do that you can either "cd" in your working directory before launching Ubooquity, or use the "-workdir" command line option: it allows you to specify where Ubooquity should create its own files (database, logs, preferences, cache, etc).

Ubooquity tries to unzip the file and fails.

As a workaround, it tries to guess the actual format by reading the first few bytes of the file (you'd be surprised by how many people confuse cbr and cbz when naming their files).

Turns out the file is a zip file, so it tries to unzip it (Useless, I agree. Usually in theses situations the actual format is different).

It fails again, of course.

As to why exactly, I don't know. The "magic number" is the only way Ubooquity has to guess the format.

Your files might be corrupted.

Unless you use the "--host" command line parameter ("-host" works too), Ubooquity listens to everything coming to your server on the specified port. There is no need to enable anything for remote connections, they are allowed by default.

I'm afraid your problem is somewhere else on the network.