Hello,

Ubooquity does indeed display the ComicRack metadata when they are found in the comic file.

To check if this metadata file is present, open one of your comics with an archive tool (Winzip, 7zip, Bandizip...) and look for a file named ComicInfo.xml.

If the file exists, the metadata should be displayed in Ubooquity. If you don't see them, there might be a bug and I'd be interested in getting the comic file to see what went wrong.

If the file does not exist, Ubooquity can't display metadata.

More details about metadata in ComicRack

(ComicRack can only write CBZ and CB7 files. So if you added metadata to CBR files using ComicRack, it'll stay in the ComicRack internal database)

What configuration lines do you have in the server section (of nginx) above "location" ? (especially the values for "listen" and "server_name")

I'm playing with nginx and haven't managed to reproduced the problem on my side yet.

But I have never really used it for more than a few tests, so I'm really far from being an nginx expert.

a black and white text only page with "Please identify yourself" in the upper left hand corner along with user ID and password boxes and a login button

Seems like the browser cannot find the CSS and images used by the login page. Did you try to clear the cache of your browser ?

If you get a proper login page after the cache clearing, please let me know so that I can focus on the remaining parts of the problem.

As for the main issue, it would be interesting to determine if your problem comes from the HTTPS or the reverse proxy feature.

Did you (or could you) try the following setups:

• No HTTPS, with reverse proxy through nginx (i.e. accessing Ubooquity via http://mydomain.net/ubooquity/ )
• HTTPS without reverse proxy, still through nginx (i.e. accessing Ubooquity via https://mydomain.net/)

Knowing which one works and which one doesn't would help delimiting the problem.

I have never used Docker, so I won"t be able to help much unfortunately.

What I can confirm is that the "permission denied" and the "NullPointerException" you get are coming from problems with the file system as seen by Ubooquity (the second one happens when Ubooquity tries to list the content of a scanned directory but encounters an I/O error).

It's as if Ubooquity suddenly lost the rights to access files in the middle of a scan.

I'm afraid this is a pure Docker issue.

Hello,

The script on the download page is just a manual start/stop script for command line usage, it won't start Ubooquity automatically with your system.

Do do that you'll need to either run it as a daemon, or use a cron job.

Both solution are described in this thread above. :)

Hello,

Unfortunately all the menu text is written directly into the code.

I know it's not a good practice, but I figured this was an application with almost no text (mostly icons, in the user interface anyway).

Désolé. :/

Thanks for your feedback !

This means a lot of people are probably using symlinks without being aware of it.

It would explain all the problems mentioned in this thread.

I was looking in the wrong direction, now I "just" have to add symlink support.

Thanks again !

I knew about the existence of the CBT format, but I never ever saw one CBT file in over 15 years of reading electronic comics. So I'm be curious to know where this format is actually used.

Usage apart, CBT is indeed technically the best format for storing comics pages (see next message) (CB7 is a nonsense, CBR should not be used anymore, CBZ is acceptable if used without compression).

So I'll add support in one of the next Ubooquity versions.

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.