Nice ! I didn't know this one. :)

Ubooquity needs writing authorization on the files located in its working directory.

Did you happen to launch Ubooquity manually the first time (allowing to create all its files with user A) then as a service (with user B, hence the rights problem) ?

Same answer as above: send me a link where I can download an example of mobi file for which Ubooquity does not correctly guess the cover, and I'll take a look to see if the extraction algorithm can be improved.

You can't recover it, but you can reset it: instructions in the FAQ.

This message, "Sorry, you are not authorized to access any file on this server", is what Ubooquity displays when it has nothing to show, meaning when no folder has been shared yet, or when the user you are logged in with doesn't have rights on any of the shared folder.

In other word, when you donwload and run Ubooquity with further configuration, you get this message.

I guess I should reword it to be more explicit.

So the fix for your problem is simply to configure Ubooquity again (The documentation has been updated, should you need any help).

"Address already in use" means that another application uses one of the ports Ubooquity uses (2202 for the library, 2203 for the admin page).

You have to use other ports (see here for command line options).

By the way, according to your logs, you are using Java 8 (which is a good thing, since Ubooquity does not work with Java 7).

Thanks for the nice words. :)

You have to run it in a directory with writing rights ("cd" into the one you chose before typing the java command).

I'm asking because Ubooquity keeps user settings in files it creates when running.

If it can't create the files, settings will be lost when Ubooquity is stopped.

You can check if the settings files are properly created (and modified) when you run Ubooquity. Easiest one to check: preferences.json

Two points that are new to Ubooquity 2.0.X (just in case it could help):

• there are two different ports: one for the library (2202), one for the admin page (2203)
• by default, the admin page can not be reached from an external machine, you have to explicitely allow remote administration (either on the desktop UI if your run Ubooquity by clicking on the jar, or using the --remoteadmin command line argument)