[Support] Linuxserver.io - Ubooquity


Recommended Posts

@saarg - thanks for your comment above. I had a really dumb mistake in my setup and I would not have noticed it without your help. Thanks!

 

I will correct my post above and I attach a version of my "ubooquity.subdomain.conf" file as it may be useful for others. I do not think one comes with the LetsEncrypt docker from the fine folks at LinuxServer? 

 

@CHBMB - hope you are well! Is there a conf file for Ubooquity with the Let's Encrypt docker? Last I looked there was not. It was easy enough to create my own (attached) but would be great to get someone who knows what they are doing to add this to the conf library? 

 

 

 

ubooquity.subdomain.conf

Edited by TexasDave
Link to comment
  • 4 weeks later...

I've edited my /nginx/site-confs/default file with:

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

and checked my ubooquity admin page to ensure the reverse proxy prefix is set to ubooquity as well as restarted letsencrypt.

 

I'm not currently getting any error from letsencrypt, but I can't access https://ubooquity.mydomain.me or https://mydomain.me/ubooquity

 

what step am I missing here?

 

edit: ...I just realized (as I was guessing around) that it's set to XXXX.duckdns.org/ubooquity/

is there a way to have it use my private domain? I'd much prefer to use ubooquity/mydomain.me or at the least mydomain.me/ubooquity 

 

edit2: it also goes through a security warning when you visit the first time that you have to override... any way to stop that? 

 

edit3: Okay, I've gotten a little further. I set up a file in the proxy-config folder titled ubooquity.subdomain.config (I basically just took another config file and changed it to match ubooquity info)

 

# make sure that your dns has a cname set for ubooquity

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name ubooquity.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2202/ubooquity/admin;
    }


}


This takes me to an odd looking log in page (basically the log in with no CSS) and no matter what I enter, it won't let me through. When I check the ubooquity logs, I get this error (depending on login info I try)

 

Quote

20190303 00:12:10 [qtp1213818572-22] INFO com.ubooquity.d.c - Password provided is wrong. Access denied. [login:leftovernick]

 

When I turn off "Protect shared content with user accounts" It takes me in to the main page with no CSS again and no comics or images (also the links don't go anywhere)

 

Basically it looks like all it's sending through is the HTML, but no CSS or back end.

Edited by leftovernick
Link to comment
  • 3 weeks later...
On 2/28/2019 at 9:52 PM, leftovernick said:

I've edited my /nginx/site-confs/default file with:


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

and checked my ubooquity admin page to ensure the reverse proxy prefix is set to ubooquity as well as restarted letsencrypt.

 

I'm not currently getting any error from letsencrypt, but I can't access https://ubooquity.mydomain.me or https://mydomain.me/ubooquity

 

what step am I missing here?

 

edit: ...I just realized (as I was guessing around) that it's set to XXXX.duckdns.org/ubooquity/

is there a way to have it use my private domain? I'd much prefer to use ubooquity/mydomain.me or at the least mydomain.me/ubooquity 

 

edit2: it also goes through a security warning when you visit the first time that you have to override... any way to stop that? 

 

edit3: Okay, I've gotten a little further. I set up a file in the proxy-config folder titled ubooquity.subdomain.config (I basically just took another config file and changed it to match ubooquity info)

 


# make sure that your dns has a cname set for ubooquity

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name ubooquity.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2202/ubooquity/admin;
    }


}


This takes me to an odd looking log in page (basically the log in with no CSS) and no matter what I enter, it won't let me through. When I check the ubooquity logs, I get this error (depending on login info I try)

 

 

When I turn off "Protect shared content with user accounts" It takes me in to the main page with no CSS again and no comics or images (also the links don't go anywhere)

 

Basically it looks like all it's sending through is the HTML, but no CSS or back end.

I've reached the point where the same thing is happening to me. I'm having no luck fixing it. Have you resolved this?

Link to comment
On 3/1/2019 at 4:52 AM, leftovernick said:

I've edited my /nginx/site-confs/default file with:


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

and checked my ubooquity admin page to ensure the reverse proxy prefix is set to ubooquity as well as restarted letsencrypt.

 

I'm not currently getting any error from letsencrypt, but I can't access https://ubooquity.mydomain.me or https://mydomain.me/ubooquity

 

what step am I missing here?

 

edit: ...I just realized (as I was guessing around) that it's set to XXXX.duckdns.org/ubooquity/

is there a way to have it use my private domain? I'd much prefer to use ubooquity/mydomain.me or at the least mydomain.me/ubooquity 

 

edit2: it also goes through a security warning when you visit the first time that you have to override... any way to stop that? 

 

edit3: Okay, I've gotten a little further. I set up a file in the proxy-config folder titled ubooquity.subdomain.config (I basically just took another config file and changed it to match ubooquity info)

 


# make sure that your dns has a cname set for ubooquity

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name ubooquity.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2202/ubooquity/admin;
    }


}


This takes me to an odd looking log in page (basically the log in with no CSS) and no matter what I enter, it won't let me through. When I check the ubooquity logs, I get this error (depending on login info I try)

 

 

When I turn off "Protect shared content with user accounts" It takes me in to the main page with no CSS again and no comics or images (also the links don't go anywhere)

 

Basically it looks like all it's sending through is the HTML, but no CSS or back end.

I posted a working subfolder config in the letsencrypt thread.

Link to comment
1 hour ago, CHBMB said:

Did you look at the post immediately above your first one?  TexasDave had posted a config.

I didn’t see that one, I’ll try it out!

 

edit: Texasdave's config worked. Is there a way round having to the /ubooquity/admin after the url? (ie. https://ubooquity.XXX.me/ubooquity/admin)

 

not the biggest deal, but would be nice.

 

1 hour ago, saarg said:

Then figure out how to do that. 

No need to be rude... that is what I’m doing..

Edited by leftovernick
Link to comment
On 3/22/2019 at 11:46 PM, leftovernick said:

I would prefer to use my sub domain if possible.



server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name ubooquity.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;
        
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2202;
    }

    location /admin {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2203;
    }

    location /admin-res {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2203;
    }

    location /admin-api {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2203;
    }
}

This one works.

Link to comment
  • 1 month later...

hey i just installed this docker and copied some of my comics, im trying to make it work with kuboo app on android but im getting that "could not find matching provider (wrong URL)" error. so if anyone knows how to fix this, i would appreciate your help.

Link to comment
  • 5 weeks later...

Hi Max.

 

as far as i know needs the kuboo app that opsd / opsd folder is enable on the ubooquity server to find the data.

 

That is where my question is starting :) Hi i am really new to unraid and docker and i also installed the ubooquity app to get access to my comics. It finds all the comics but i am not able to access the admin page via port 2203 to configure it.

 

Or is this not possible in the docker version?

Link to comment
4 hours ago, Seruschl said:

Hi Max.

 

as far as i know needs the kuboo app that opsd / opsd folder is enable on the ubooquity server to find the data.

 

That is where my question is starting :) Hi i am really new to unraid and docker and i also installed the ubooquity app to get access to my comics. It finds all the comics but i am not able to access the admin page via port 2203 to configure it.

 

Or is this not possible in the docker version?

Docker run command please

Link to comment
  • 3 weeks later...

Just installed this to test out my comic collection and the Android app I am using to access the server is telling me a feature isn't enabled (OPDS feed).

 

I found that to enable OPDS feed I first need to visit the /admin/ page and enable it.

However, nothing happens when I visit that admin page.

 

The ip:2202/ubooquity/admin/ page looks the exact same (on Chrome) as the ip:2202/ubooquity/ page looks, and I'm not sure why. Some pages said I needed to add the "--remoteadmin" option. . .

 

 - https://ubooquity.userecho.com/communities/1/topics/396-admin-page-on-200-not-working

 

. . .since it is running on an external NAS machine. But I haven't figured out how to do that. Add it to either the extra parameters (breaks the docker) or the post arguments (forces the app to shut down after an attempted start) doesn't seem to work.

 

Any thoughts?

Link to comment
13 minutes ago, Endda said:

Just installed this to test out my comic collection and the Android app I am using to access the server is telling me a feature isn't enabled (OPDS feed).

 

I found that to enable OPDS feed I first need to visit the /admin/ page and enable it.

However, nothing happens when I visit that admin page.

 

The ip:2202/ubooquity/admin/ page looks the exact same (on Chrome) as the ip:2202/ubooquity/ page looks, and I'm not sure why. Some pages said I needed to add the "--remoteadmin" option. . .

 

 - https://ubooquity.userecho.com/communities/1/topics/396-admin-page-on-200-not-working

 

. . .since it is running on an external NAS machine. But I haven't figured out how to do that. Add it to either the extra parameters (breaks the docker) or the post arguments (forces the app to shut down after an attempted start) doesn't seem to work.

 

Any thoughts?

 

The admin interface is on port 2203.

Link to comment
  • 1 month later...

i'm similar to the couple users above with trouble on Android, except i've set all the configuration up with the admin page but my phone still won't connect. i suspect it's a problem with the port 2202 on my router but i'm not too familiar with networking issues. the docker runs fine on the webui, i just wanna read on my commutes is all.

Link to comment
  • 4 weeks later...
On 3/24/2019 at 5:51 PM, saarg said:

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name ubooquity.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;
        
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2202;
    }

    location /admin {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2203;
    }

    location /admin-res {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2203;
    }

    location /admin-api {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_ubooquity ubooquity;
        proxy_pass http://$upstream_ubooquity:2203;
    }
}

This one works.

 

Thanks for sharing this. I've tried it but I get the "Wecome to our server" screen rather than ubooquity.

 

I've got other confs up and running fine, just this one I'm having trouble with. Can you suggest any pointers for what I should check?

 

I've tried adding /ubooquity and /uboqquity/admin to my urls to no avail.

Link to comment
3 hours ago, opusdeath said:

 

Thanks for sharing this. I've tried it but I get the "Wecome to our server" screen rather than ubooquity.

 

I've got other confs up and running fine, just this one I'm having trouble with. Can you suggest any pointers for what I should check?

 

I've tried adding /ubooquity and /uboqquity/admin to my urls to no avail.

 

Are you using https?

Hard to say what is wrong when you haven't told us your setup. And this should probably be in the letsencrypt thread. Did you use the config that is supplied with letsencrypt?

Link to comment
  • 2 weeks later...

Looking for some help. I have had this working for a long time. This morning, I had to shutdown my server to replace the battery in my UPS.

 

When I came back up, I was getting the "Welcome to our server" message when trying to access ubooquity externally....

  • Internal access works fine (both user (port 2022) and admin (port 2023)).
  • Ombi (which is also reversed proxy'd) is working fine internally and externally.
  • Router ports are fine
  • Nginx ubooquity conf files is fine and has not changed (attaced). Using the one provided and just chnaged to my subdomain (dz-comics)
  • Deleted ubooquity appdata and docker and this has not fixed it
  • No errors in Letsencrypy or ubooquity logs....
  • Letsencrypt, ombi and ubooquity on "proxynet"
  • This is the URL that has always worked until this morning: https://dz-comics.duckdns.org/ubooquity/

 

I think the "Welcome" message usually means your nginx conf file has an error?

 

Before flooding the support thread with logs - what are the most common causes for the "Welcome to our server" message? As ombi is working, I lean to an error on ubooquity but am paranoid on a "typo" being an issue after I reinstalled everything. Happy to post anything to get another pair of eyes to sort this...Thanks!

 

[EDIT: Fixed this by restoring an older version of the ubooquity appdata using CABackup. Over the weekend, I am going to try to do a diff and see what the issue was. I have had more issues with Ubooquity than all other services combined. I want to understand why...]

ubooquity.subdomain.conf

Edited by TexasDave
Link to comment
  • 7 months later...
  • 2 months later...

It seems ubooquity remains the best for my purppose. I have a calibre library for ebooks and a comicrack library for comics.

 

I have one host path pointing to comics (folder) and another pointing to books (folder). Still facing some issues:


1) Comics - once I select comics on the main GUI screen, I am getting another page where I yet again needs to select comic. Only thereafter, I get the list of comics to choose from.

 

2) Books - Same issue as above with "books and book". Also, it doesn't seem to yet integrate too well with Calibre. Not sure what I need to do differently to have a smoother integration. Author name seems to be taken from the artist folder (e.g., Rowling, J.K_) rather than how Calibre displays it (e.g., J.K. Rowling). Is there a way to point Ubooquity to the library? Or how else does it work to get the books properly displayed?

 

Thanks a lot in advance!

Link to comment
12 minutes ago, steve1977 said:

It seems ubooquity remains the best for my purppose. I have a calibre library for ebooks and a comicrack library for comics.

 

I have one host path pointing to comics (folder) and another pointing to books (folder). Still facing some issues:


1) Comics - once I select comics on the main GUI screen, I am getting another page where I yet again needs to select comic. Only thereafter, I get the list of comics to choose from.

 

2) Books - Same issue as above with "books and book". Also, it doesn't seem to yet integrate too well with Calibre. Not sure what I need to do differently to have a smoother integration. Author name seems to be taken from the artist folder (e.g., Rowling, J.K_) rather than how Calibre displays it (e.g., J.K. Rowling). Is there a way to point Ubooquity to the library? Or how else does it work to get the books properly displayed?

 

Thanks a lot in advance!

Try turn on "Bypass single root folder" and "Shared books are in a Calibre library" in the Advanced settings.

PS: your questions probably are better asked in the Ubooquity support as they are not specific to the docker. 

Link to comment
  • 2 weeks later...

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.