[Support] Linuxserver.io - Ubooquity


Recommended Posts

linuxserver_medium.png

 

Application Name: Ubooquity

Application Site: https://vaemendis.net/ubooquity/

Docker Hub: https://hub.docker.com/r/linuxserver/ubooquity/

Github: https://github.com/linuxserver/docker-ubooquity/

 

Please post any questions/issues relating to this docker you have in this thread.

 

If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Edited by linuxserver.io
Link to comment
  • 1 month later...
  • 2 months later...

After the latest Docker update available for this image, I can no longer login under either the admin page or as a regular user. I get a 502 Bad Gateway error as well as two different Java errors in the logs:

 

20170326 10:54:10 [pool-1-thread-6] ERROR com.ubooquity.Ubooquity - Uncaught exception on thread: pool-1-thread-6
java.lang.NoClassDefFoundError: Could not initialize class sun.security.ec.SunEC
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.8.0_121]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[na:1.8.0_121]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:1.8.0_121]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[na:1.8.0_121]
at java.lang.Class.newInstance(Class.java:442) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206) ~[na:1.8.0_121]
at java.security.AccessController.doPrivileged(Native Method) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187) ~[na:1.8.0_121]
at sun.security.jca.ProviderList.getProvider(ProviderList.java:233) ~[na:1.8.0_121]
at sun.security.jca.ProviderList$ServiceList.tryGet(ProviderList.java:434) ~[na:1.8.0_121]
at sun.security.jca.ProviderList$ServiceList.access$200(ProviderList.java:376) ~[na:1.8.0_121]
at sun.security.jca.ProviderList$ServiceList$1.hasNext(ProviderList.java:486) ~[na:1.8.0_121]
at javax.crypto.Mac.getInstance(Mac.java:174) ~[na:1.8.0_121]
at com.ubooquity.f.c.a(SourceFile:29) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.provider.webadmin.j.a(SourceFile:600) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.provider.webadmin.j.a(SourceFile:115) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.c.a(SourceFile:324) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.c.a(SourceFile:58) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.c$1.a(SourceFile:133) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.e.e.a(SourceFile:287) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.e.e$f.a(SourceFile:830) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.e.e$1$1.run(SourceFile:210) ~[Ubooquity.jar:1.10.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121]

 

20170326 10:48:20 [pool-1-thread-2] ERROR com.ubooquity.Ubooquity - Uncaught exception on thread: pool-1-thread-2
java.lang.InternalError: null
at sun.security.ec.SunEC.initialize(Native Method) ~[sunec.jar:1.8.0_121]
at sun.security.ec.SunEC.access$000(SunEC.java:49) ~[sunec.jar:1.8.0_121]
at sun.security.ec.SunEC$1.run(SunEC.java:61) ~[sunec.jar:1.8.0_121]
at sun.security.ec.SunEC$1.run(SunEC.java:58) ~[sunec.jar:1.8.0_121]
at java.security.AccessController.doPrivileged(Native Method) ~[na:1.8.0_121]
at sun.security.ec.SunEC.<clinit>(SunEC.java:58) ~[sunec.jar:1.8.0_121]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.8.0_121]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[na:1.8.0_121]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[na:1.8.0_121]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[na:1.8.0_121]
at java.lang.Class.newInstance(Class.java:442) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:221) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206) ~[na:1.8.0_121]
at java.security.AccessController.doPrivileged(Native Method) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206) ~[na:1.8.0_121]
at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187) ~[na:1.8.0_121]
at sun.security.jca.ProviderList.getProvider(ProviderList.java:233) ~[na:1.8.0_121]
at sun.security.jca.ProviderList$ServiceList.tryGet(ProviderList.java:434) ~[na:1.8.0_121]
at sun.security.jca.ProviderList$ServiceList.access$200(ProviderList.java:376) ~[na:1.8.0_121]
at sun.security.jca.ProviderList$ServiceList$1.hasNext(ProviderList.java:486) ~[na:1.8.0_121]
at javax.crypto.Mac.getInstance(Mac.java:174) ~[na:1.8.0_121]
at com.ubooquity.f.c.a(SourceFile:29) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.provider.webadmin.j.a(SourceFile:600) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.provider.webadmin.j.a(SourceFile:115) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.c.a(SourceFile:324) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.c.a(SourceFile:58) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.c$1.a(SourceFile:133) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.e.e.a(SourceFile:287) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.e.e$f.a(SourceFile:830) ~[Ubooquity.jar:1.10.1]
at com.ubooquity.e.e$1$1.run(SourceFile:210) ~[Ubooquity.jar:1.10.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121]

Is anyone else experiencing this? Any idea how to fix this?

 

Thanks in advance! :)

Link to comment

I suppose it could be my LetsEncrypt container, but I didn't change any of the settings there, either. It worked perfectly fine, right up to my Docker update round yesterday evening. All my other containers are working just fine, so it has to be either the Ubooquity container or my LetsEncrypt container.

 

I reinstalled it completely and it worked fine, right up until I made a new user and required only authorized users be able to access my /comics path, could you check this out?

 

Edit: Yep, just checked again. Works fine without user authorization, stops working the moment I add it back.

 

Edit 2: Looks like I cant access the admin page from behind my LetsEncrypt container, either, but at least it works without having users. Not very secure, though. :(

 

Thanks!

Edited by grwn
Link to comment

I get the same here if I log out and try to hit the webpage again. Not sure why this happens.

 

You could try to install one of the previous versions and see if it's working by adding the tag at the end of the repository field in the container template.

Here is the list of tags you can try https://hub.docker.com/r/linuxserver/ubooquity/tags/

 

To use the 23 tag add :23 to the end like below.

 

linuxserver/ubooquity:23

 

Link to comment
  • 2 weeks later...

 

I have this up and running. Looks pretty nice (for comics). 

 

Anyone able to get "Comic Viewer" or "Challenger Viewer" working? I am just trying to use these viewers on my LAN (not WAN) and cannot seem to get in. I am not even seeing anything in the log indicating a client is trying to hit the Ubooquity server....

 

I can get in and view on my laptop but not on a reader in Android. Thanks!

 

FIX

 

The folks on the Ubooquity board sorted it for me. A usual, pilot error on my part. 
 
I should have been entering: http://192.168.1.115:2202/ubooquity/opds-comics/
 
I was missing the "ubooquity" bit. 
Edited by TexasDave
Link to comment
On 26.3.2017 at 10:04 PM, grwn said:

 

23.

 

Sorry for the delay. Haven't really had the time to check it until now.

 

The difference from tag 23 and 24 are openjdk8-jre-lib and base 8.121.13-r2 vs 8.121.13-r1.

So something broke ubooquity in the r2 version. I'll see if we can go back somehow. 

Link to comment
  • 2 months later...
On 3/26/2017 at 5:25 AM, grwn said:

I suppose it could be my LetsEncrypt container, but I didn't change any of the settings there, either. It worked perfectly fine, right up to my Docker update round yesterday evening. All my other containers are working just fine, so it has to be either the Ubooquity container or my LetsEncrypt container.

 

I reinstalled it completely and it worked fine, right up until I made a new user and required only authorized users be able to access my /comics path, could you check this out?

 

Edit: Yep, just checked again. Works fine without user authorization, stops working the moment I add it back.

 

Edit 2: Looks like I cant access the admin page from behind my LetsEncrypt container, either, but at least it works without having users. Not very secure, though. :(

 

Thanks!

 

How did you go about configuring this docker to work with LetsEncrypt? I'm using the LinuxServer LetsEncrypt docker container, and I have been having trouble getting it to work at all.

Link to comment
On 08/06/2017 at 4:52 AM, smashingtool said:

How did you go about configuring this docker to work with LetsEncrypt? I'm using the LinuxServer LetsEncrypt docker container, and I have been having trouble getting it to work at all.

 

	location /ubooquity {
		proxy_pass http://192.168.0.1:2202/ubooquity;
		include /config/nginx/proxy.conf;	
	}

And in the admin interface:

D906Tpd.png

Link to comment
21 hours ago, smashingtool said:

I found https://vaemendis.github.io/ubooquity-doc/pages/tutorials/lets-encrypt.html on the ubooquity website, but I am not really sure how to make that work with docker containers. Anyone have any insight on how to possibly pull this off?

 

Also, I see that Ubooquity now has a beta for version 2.0.2. Is there any way to set a flag to install this beta version?

 

For the first, check the post above and use our LetsEncrypt container and reverse proxy this container.

 

No, there's no flag to set the beta version.  Will get updated at stable.

Link to comment

Thank you CHBMB! I had it like this before:

 

    location / {
        proxy_pass https://192.168.1.130:2202/ubooquity;
        proxy_max_temp_file_size 2048m;
        include /config/nginx/proxy.conf;
    }

But that was not working. Now I can get to it. I didn't realize that the reverse proxy prefix needed to be part of the location, rather than simply as part of the server_name. 

Link to comment
  • 1 month later...

I notice that the docker has been updated Ubooquity version 2.1.  It looks like the update made some internal changes that made the existing databases inaccessible.  The databases are repopulating from the path set in the docker setup, rather than from the path set in the ubooquity admin area.  The admin page is also no longer accessible via the normal url method.

 

Is there a new method I should be using to access the admin page, and if not, how can I revert back to v 1.10?

 

Thanks!

Link to comment
12 hours ago, MisterWolfe said:

I notice that the docker has been updated Ubooquity version 2.1.  It looks like the update made some internal changes that made the existing databases inaccessible.  The databases are repopulating from the path set in the docker setup, rather than from the path set in the ubooquity admin area.  The admin page is also no longer accessible via the normal url method.

 

Is there a new method I should be using to access the admin page, and if not, how can I revert back to v 1.10?

 

Thanks!

I just added port 2203 and now it works. By the looks of it you have to have two ports mapped 2202 and 2203.

I noticed this in the sys log also:
Fix Common Problems: Error: Docker Application ubooquity, Container Port 2203 not found or changed on installed application

 

https://hub.docker.com/r/linuxserver/ubooquity/ tells you:
-p 2202 - the library port
-p 2203 - the admin port

 

Link to comment
4 hours ago, Hogwind said:

I just added port 2203 and now it works. By the looks of it you have to have two ports mapped 2202 and 2203.

I noticed this in the sys log also:
Fix Common Problems: Error: Docker Application ubooquity, Container Port 2203 not found or changed on installed application

 

https://hub.docker.com/r/linuxserver/ubooquity/ tells you:
-p 2202 - the library port
-p 2203 - the admin port

 

 

That did it, thanks!

 

 

Link to comment
  • 4 weeks later...

starting fresh, pointed to ebooks and comics folders but getting the following error and an orphaned docker.

I'm using Unraid 6.3.5

 
Warning: SimpleXMLElement::addChild(): unterminated entity reference EBooks/ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 211 Warning: SimpleXMLElement::addChild(): unterminated entity reference EBooks/comics/ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 211 Warning: SimpleXMLElement::addChild(): unterminated entity reference EBooks/ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 211 Warning: SimpleXMLElement::addChild(): unterminated entity reference EBooks/comics/ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 211
 
Docker output:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="ubooquity" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "MAXMEM"="512" -e "MAXMEM"="512" -e "PUID"="99" -e "PGID"="100" -e "PUID"="99" -e "PGID"="100" -p 2202:2202/tcp -p 2202:2202/tcp -p 2203:2203/tcp -v "":"/books":ro -v "":"/comics":ro -v "":"/books":ro -v "":"/comics":ro -v "/mnt/user/appdata/ubooquity":"/config":rw -v "/mnt/user/appdata/ubooquity":"/config":rw linuxserver/ubooquity

/usr/bin/docker: Error response from daemon: Invalid volume spec ":/books:ro": Invalid volume specification: ':/books:ro'.

 
Tried different folders, safe naming conventions, updating OS to 6.3.5 but no luck.
Had it working fine with old versions. 
Any ideas guys?
Edited by hayleraid
added OS version
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.