Hello,

Thanks for the new version. I have a question.

What is the difference between folder categories? Are they just for sorting books, or is there something else? Are they related to the format (pdf, cbz, epub...)? And what does it change to check "Folder is a Calibre library"?

Is there any plans to incorporate a DJVU reader to Ubooquity?

Unless I am doing something wrong I cannot read these files with the program?

Thanks 

Ian

Hi Tom,

as I have seen that you are in the middle of v3, I would first of all say a big thank you for the great work :)

I would like to add some feature requests here:

- Media Analysis: Identification of faulty files, wrong cbr/cbz archives, epubs etc.

- Duplicate Files: Identification of duplicates inside the library

is something like this planned?

I saw that there is a new beta coming out (yay!) and I was just wondering if there is any way to sync progress like I can do with some apps and Kavita? Would love to get all my epubs and comics under a single program, so was just curious.

Thanks!

So I've got my server up and running on my Mac and I'm trying to add a folder that's on my NAS where all of my media resides. 

When I navigate to the "Volumes' folder it shows me my local and attached drives. Does anyone know the path to mapped network drives on a Mac?

Thanks in advance!

I use Ubooquity for my massive RPG PDF collections simply because its the best option for the very weird file structure I have organized over the years. I'd simply love to be able to set a default action when clicking a book, so that instead of the popup asking if I want to download or read pops up, it just automatically does whichever option I set as default. I often like to copy/paste or highlight things in these PDFs so a way to skip those extra clicks would be a massive QOL improvement.

I would like to be able to translate some words or phrases into different languages.

For example, translate the login page or the book information popup

Running into problems with Ubooquity following moving to a new machine. I just migrated my setup to a new mac mini, my sense was that everything is supposed to be contained in the java, but now something seems to not be working correctly.

In Chunky, I can browse the OPDS, but I get "the network connection was lost" if I try to download anything, and missing pages and half pages when I stream. An example of the errors I see are attached below.

I suspect it may have something to do with my reverse proxy configuration, though it hasn't changed since migrating the machine; nginx maps the port associated with ubooquity to /print/ on my server, but when I pass the URL with the port i.e. 192.168.x.y:zzzz/print/ it works fine.

Any ideas?

20230529 22:45:14 [qtp224100622-58] ERROR com.ubooquity.c.a - Could not serve stream with URI: /print/opds-comics/comicreader/591829
org.eclipse.jetty.io.EofException: null
    at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:292) ~[jetty-io-9.4.0.v20161208.jar.2217617090236472972.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:429) ~[jetty-io-9.4.0.v20161208.jar.2217617090236472972.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:322) ~[jetty-io-9.4.0.v20161208.jar.2217617090236472972.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.io.AbstractEndPoint.write(AbstractEndPoint.java:372) ~[jetty-io-9.4.0.v20161208.jar.2217617090236472972.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpConnection$SendCallback.process(HttpConnection.java:747) ~[jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:241) ~[jetty-util-9.4.0.v20161208.jar.2399535752484912560.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.util.IteratingCallback.iterate(IteratingCallback.java:224) ~[jetty-util-9.4.0.v20161208.jar.2399535752484912560.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:518) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:677) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:728) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:234) ~[jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:218) ~[jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:509) ~[jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2147) ~[commons-io-2.5.jar.3281126444996151313.tmp:2.5]
    at org.apache.commons.io.IOUtils.copy(IOUtils.java:2102) ~[commons-io-2.5.jar.3281126444996151313.tmp:2.5]
    at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:2123) ~[commons-io-2.5.jar.3281126444996151313.tmp:2.5]
    at org.apache.commons.io.IOUtils.copy(IOUtils.java:2078) ~[commons-io-2.5.jar.3281126444996151313.tmp:2.5]
    at com.ubooquity.d.d.a(SourceFile:96) ~[Ubooquity.jar:2.1.2]
    at com.ubooquity.c.a.a(SourceFile:374) [Ubooquity.jar:2.1.2]
    at com.ubooquity.provider.page.a.a(SourceFile:138) [Ubooquity.jar:2.1.2]
    at com.ubooquity.provider.page.a.a(SourceFile:78) [Ubooquity.jar:2.1.2]
    at com.ubooquity.provider.opds.c.a(SourceFile:152) [Ubooquity.jar:2.1.2]
    at com.ubooquity.d.c.a(SourceFile:142) [Ubooquity.jar:2.1.2]
    at com.ubooquity.d.b.handle(SourceFile:54) [Ubooquity.jar:2.1.2]
    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:190) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1228) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:170) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1130) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:118) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.Server.handle(Server.java:564) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:318) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [jetty-server-9.4.0.v20161208.jar.5058115764834022332.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279) [jetty-io-9.4.0.v20161208.jar.2217617090236472972.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:112) [jetty-io-9.4.0.v20161208.jar.2217617090236472972.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124) [jetty-io-9.4.0.v20161208.jar.2217617090236472972.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:672) [jetty-util-9.4.0.v20161208.jar.2399535752484912560.tmp:9.4.0.v20161208]
    at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:590) [jetty-util-9.4.0.v20161208.jar.2399535752484912560.tmp:9.4.0.v20161208]
    at java.lang.Thread.run(Thread.java:750) [na:1.8.0_371]
Caused by: java.io.IOException: Broken pipe

I can't for the life of me figure out how to convert the cert that I got from Lets Encrypt / Certbot to something usable by Ubooquity.

A long time ago I gave up trying to use HTTPS with Ubooquity on Windows 10. I tried. I read lots of things, I tried lots of things, but I clearly did not understand what I was doing. Recently I heard a colleague mention how easy it was setting up his server's certs with Lets Encrypt and automating it with Certbot. So I tried it, and it was super easy. Just downloaded Cerbot, ran the Windows installer, and before you know it, I had a legit cert for my Win 10 box... but the files that Certbot grabs for you are PEM files. Ubooquity wants a java keystore...

So I did plenty of searching and reading. Lots of instructions for Linux - next to nothing for Windows. I did try some that I found, one was manually generating a keystore with the command line. Then somehow importing your PEM into the keystore...

None of the instructions I found worked. Clearly I'm missing something. Honestly, I don't know how certs work or have much experience with them. When I need to apply them at work, I download the cert from DigiCert and follow the application instructions and they work. But there aren't really instructions for this for Ubooquity (at least not any I could find).

Can someone help by documenting this?

I can get it started:

1. Open your web browser and go to

   https://certbot.eff.org/

2. You'll see a large "My HTTP website is running " and a drop-down menu " on " and another drop-down menu.

3. Use the two drop-downs. Select Other for the first one and Windows for the second.

4. It will take you an instructions page. There's a download link there to get the certbot installed. https://github.com/certbot/certbot/releases/latest/download/certbot-beta-installer-win_amd64_signed.exe
5. Install certbot by double-clicking the file after you download it. It will open an install wizard. Just accept the defaults and click your way through until it is finished.
6. Halt your Ubooquity service (open it from the toolbar and click the "Stop Server And Exit" button)
7. Halt any other web servers you might be running on your PC
8. (You may have to briefly disable your Windows firewall for the next step. I did not, but YMMV.)
9. Open a command prompt with admin privs (right click on it in the Start menu, select More, and select Run As Administrator)
10. In the command prompt type: certbot certonly --standalone
11. Note that there are two minus signs in that command.
12. Certbot will ask you what the domain name of your server is, type it in. (Example: www.myserver.net)
13. Certbot will grab a cert for you and save it in the default directories and even tell you what they are.
14. Copy & Paste the info from the command prompt into Notepad and save it. You'll need that info later.
15. Remember that certbot has scheduled a renewal of your cert just before it expires. So you shouldn't have to do anything more with certbot.

... and that's where I hit a brick wall. I don't know what to do with the PEM files that cerbot so kindly grabbed for me.

hello !

In the title

Thank