It seems that the admin page is not very secured: once the admin is logged in, the page .../admin stays open for an infinite amount of time until a user clicks on "log administrator out"

• Even after a full night without activity, [and in fact, without even any connection to the page] in the morning, I can still access the admin page without beeing requested to put in the password
• one the admin is logged in, there is no IP check. I've moved from home (local network) to office (external network), and ubooquity doesn't detect there has been a change and doesn't request to put in the password

This is worrisome because it means that once an admin is logged-in, anybody can access the admin page; and I mean anybody: it's not even limiting access to registered users, anybody trying that page will gain access to the admin page

This is a bit strange because it seems to me [although I haven't really tested that] that the main pages for consulting the library does not suffer from this security breach

I suggest to improve

• add an "inactivity timer" in the admin page, set to 5 minutes by default [you may add this parameter in the admin settings];
• detect the IP address of the client connection so that whenever it's a new IP, ubooquity requests a new login.
• add something at the bottom of the page displaying the number of clients connected to the admin page => this could help detect intrusion

Here is an issue I've found that I don't understand

When I set the number of items per page to 20 and read the comics from internet, everything is going fine: browsing is fast, and I don't see any problems

But, when I set the number of items to 24, then every time I load a new page some icons takes a long time to load (more thant 0sec), and I see 4 warnings in the logs

20161114 14:07:50 [pool-1-thread-20]  WARN com.ubooquity.e.e - Interrupted while sending response (perhaps the client stopped the download) - java.net.SocketException - Broken pipe
20161114 14:07:50 [pool-1-thread-13]  WARN com.ubooquity.e.e - Interrupted while sending response (perhaps theclient stopped the download) - java.net.SocketException - Broken pipe
20161114 14:07:50 [pool-1-thread-15]  WARN com.ubooquity.e.e - Interrupted while sending response (perhaps the client stopped the download) - java.net.SocketException - Broken pipe
20161114 14:39:59 [pool-1-thread-15]  WARN com.ubooquity.e.e - Interrupted while sending response (perhaps the client stopped the download) - java.net.SocketException - Broken pipe

I don't understand this issue nor do I know where to search for a cause; I don't believe it's a performance issue on my Synology NAS: a difference of 4 items on a page doesn't seem enough to create a problem, and I have a fast connection to internet, so I don't believe the problem is there either...

If I set the number of items to 26, I see that 6 items take a very long time to load... but I dont see any warning in the logs

If I set the number of items to 21, I see that 1 item take a very long time to load... but I don't see any warning in the logs either

What could be the cause of this ? why is 20 a magic number ?

Hi Tom,

I'm using a custom theme (the dark theme made by Hidea). I've added all the necessary faviocn .png images to the custom theme folder (with the same filenames used by your default Ubooquity theme) but Ubooquity or the browser isn't using them, it just loads the default Ubooquity favicon images

I've tried on the following browsers:

Chrome desktop, mobile (ios & android)

Safari mobile

Microsoft Edge

Any ideas what's going on?

I'm running Ubooquity on a Mac mini. Generally it works fine but periodically it will crash requiring me to go and restart it. I'm trying to set up a cron job to check on it every so often and restart if need be but am running into a problem.

If I double-click Ubooquity.jar from the OS X GUI it launches fine. If I try to start it via Terminal though, I get this:

Computer:Ubooquity user$ java -jar Ubooquity.jar -webadmin
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/ubooquity/Launcher : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

Any ideas?

Since you plan to add a read status to comics, I believe this would be fairly easy to implement

I'm assuming you are going to have a table keeping track of the reading status of each comics for each user.

You could add in the same table, a column keeping track of comic's rating by user. This way we could have new benefits:

1: when opening the comics, provide ratings in the details window(and if the user has not put any rating, ubooquity could compute an average for all users)

2: folder (or any grouping), could display an average of the ratings for all comics within the folder/group below the image (again: display average for the connected user or the average over all users if no user ratings are available)

3: (in a future) a new sorting criteria for comics

I seem to have a problem with scanning ebooks after setting up a new instance of Ubooquity. Libraries that work fine don't anymore, and I'm not quite sure how to debug this. The only difference to my setup is that I'm using LXC instead of docker now, as far as I know.

On the initial scan, the scanner thread works fine initially, but than hangs at always the same book. If I delete that book, it will work for a few more, but than hangs on another one again. Restarting doesn't help, it'll hang on the same book again.

This is the log message where it hangs:

[Scanner thread] INFO com.ubooquity.fileformat.epub.b - Reading metadata of epub file:

Since all my books worked before, I guess its something with my setup, but I have no idea how to figure out why Ubooquity can't read the metadata of certain books. I've enabled the --debug option, but that doesn't seem to give me more output. I've also tried to send a signal ( kill -9 1149

) to the java process to get a stack trace, but nothing happened.

Any ideas what I can do to figure out what's wrong?

A month ago I made some changes to the comic cover width and height but found it too large in the cover preview panel. So I reverted back to the measurements as shown in this screenshot. However, it appears to have no effect. Any idea how I can stop this cover overlapping?

edit: So while writing this I've checked again and it appears to be correcting the cover size in some cases but there are still large chunks of covers overlapping.

I am running Ubooquity 1.9.1 on Ubuntu 14.04 LTS with my files located on a FreeNAS box. When I start a scan, Ubooquity logs a warning and inserts a path that doesn't exist. I have nearly 1TB of files in the Comics folder but Ubooquity only finds one comic in a folder that doesn't exist. Is there a cache file that needs to be deleted somewhere? I have cleared the comics data several times without any change. Thanks for any help in this matter.

20161102 01:33:18 [Scanner thread] WARN com.ubooquity.data.database.b - Could not find id of root path /home/bob/smb:/10.0.0.18/stuff/Comics (ignore this warning if you just added a new root directory)
20161102 01:33:18 [Scanner thread] INFO com.ubooquity.data.database.b - Inserting/updating comic entry in database : /home/bob/smb:/10.0.0.18/stuff/Comics
20161102 01:33:18 [Scanner thread] INFO com.ubooquity.data.database.b - Inserting/updating comic entry in database : /home/bob/smb:/10.0.0.18/stuff/Comics/Unknown
20161102 01:33:18 [Scanner thread] INFO com.ubooquity.data.database.b - Inserting/updating comic entry in database : /home/bob/smb:/10.0.0.18/stuff/Comics/Unknown/Daredevil #158 (2)
20161102 01:33:18 [Scanner thread] INFO com.ubooquity.b.c - Reading metadata of comic file: /home/bob/smb:/10.0.0.18/stuff/Comics/Unknown/Daredevil #158 (2)/Daredevil #158 - Unknown.cbr
20161102 01:33:18 [pool-1-thread-17] INFO com.ubooquity.c - Internal server started. Listening on port 2202

When Ubooquity hits files that it can't open (in a directory it can read), it creates a 'non-thumbnail' (with just the ubooquity logo). Once the permissions on such a file are fixed and read access granted, Ubooquity doesn't re-create that thumbnail, and it doesn't update the metadata in that file.

I think it would probably be best if Ubooquity would just ignore such files, and only put it in it's database once it can actually read the files. Or maybe display a special thumbnail with an error message.

When searching for a comic, or when accessing it through the "latest comic" section, and when we click on the comic and have 2 menus: download and read.

It would be nice to add a button to "Go to the collection" (or the folder containing the comic depending on how the navigation is done in ubooquity). This button would avoid navigating through each page when we remember a title or when we want to see the rest of the collection

Better yet: in the informations, we have the collection and the number of the issue. If you could make an hyperlink with the collection to navigate directly to its folder that would be awsome