Your comments

I did some tests, the current pure Java libraries for 7zip management (namely Apache Commons Compress with XZ) are still too slow to be integrated.

Sorry.

By default (if you don't use the --host option) Ubooquity does not listen to a specific address (the one you see in the GUI is just the first one found, in reality Ubooquity listens to all of them).

So I guess your problem might come from somewhere else (firewall, port forwarding...).


As for the Linux scripting issue, I'll users more skilled than me answer you.

Still trying to figure out what might be happening...

Did you try to completely delete the database and rescan everything ?


To do that:

  1. stop Ubooquity
  2. delete (or move somewhere else) the ubooquity-4.h2.db file in your Ubooquity working directory
  3. restart Ubooquity

The ComicRack format is the only one that is commonly used for comics.

Using an external file would amount to create a format specific to Ubooquity. I prefer to stick to standards (or de facto standards) when they exist.


As for the options to choose which fields to display, it'll come "naturally" when Ubooquity starts using templates for all the pages generation.

Don't know if and when I'll do it though.


Why not just use :

https://fonts.googleapis.com/css?family=Oswald:400,700,300

in your font CSS file ?

(the fact that your are using a reverse proxy has no impact on this, fonts will be served using the URL you specified in your custom css file regardless)


The problem does not exist for fonts taken from the "fonts" folder of Ubooquity since they are referenced using relative paths (so they are automatically served through a "https" URL when a certificate is used).

I don't know exactly why you have this problem, but the symptoms you describe remind me of a HTTP Pipelining issue that some users (including me) have encountered when using Ubooquity with an iOS Browser.


I'am currently trying to replace the internal HTTP server used by Ubooquity (NanoHTTPD) with Jetty, a more robust alternative, to try to solve this issue. But there is still work to do (meaning I don't know yet when it'll be ready) and I have no idea if it will change something to your situation.