No problem. Glad it's working again. :)

Latest java 8 or java 9 ?

Any error in the logs ?

The documentation has been moved. 

You'll find everything here:

https://vaemendis.github.io/ubooquity-doc/

Your scenario allowed me to consistently reproduce the issue (and apparently it only affects books, not comics).

There is definitely something wrong with the display settings, but now I should be able to write a fix. Thanks for the help !

I'm glad your problem is solved !

Ubooquity should have no issue running with Java 1.8.162 though.

> Also see this in the log file: (So any conversion of PDF files to compliant PDF files I can run?)

20180402 12:26:30 [Scanner thread] ERROR com.ubooquity.data.feeder.a - Failed to insert /comics/101-200/bog - Nr_104 - Noegleroman.pdf

I will need the next 10 or 20 lines of logs after this one (more info about what went wrong).

> 20180402 12:23:15 [main] ERROR com.ubooquity.d.e - Provided keystore is not valid, HTTPS will NOT be activated

It means you have setup the path to a file that is not a valid JKS file in the settings. If your connection is already wrapped in HTTPS by your NAS, you don't need to set anything for this setting. (the only impact of this error is that Ubooquity serves pages using HTTP, if you see them in HTTPS, then your NAS did the wrapping).

> Another strange thing, I created a user Henrik and in the log I see:

java.io.FileNotFoundException: Henrik (No such file or directory)

Same as above, I need the surrounding log lines.

That should not be possible. Are you sure you have only one instance running ?

Not sure it's related but you need to use the "headless" option when running on a NAS.

You have two issues, right ?

• No logs written to file
• No logs displayed in the admin screen even when you manually simulate logs

If so I guess it has something to do with the working directory path (perhaps a bug).

Do you use the "workdir" option when launching Ubooquity ?

Thnaks for the accurate probelm description. But the only way I managed to reproduce your issue is by:

• Being in "folder" mode
• Doing a search that returns folders
• In another tab, switching to "flat" mode
• Clicking on a folder in the first tab

In the scenario I described you get an error because Ubooquity is not supposed to display folders in "flat" mode. (settings are stored in cookies, so when you change them in one tab, all others tabs are affected)

But I guess this scenario is not what you did. If you could describe an exact sequence of event that lead you to the issue, I could try to reproduce on my side.