PeteB

Hi, Does the ombi docker use a baseurl. From here: https://docs.linuxserver.io/images/docker-ombi it seems to indicate that the docker does, but I can't seem to confirm one way or another. If it does use a baseurl, how can I turn that off. Thanks

I've had confirmation from the developers that subsequent to 4.6.4 they "tightened up" the network checking!

For those people with the FORBIDDEN problem above, I've managed to resolve it. Emby runs as a docker which NAT's the local address into another address used by the container. For me my home network is 192.68.1.0/24 and Emby's address is 172.17.0.4. With version 4.6.4 it didn't matter that my connection was coming from a different address range, but later versions recognise this and block the connection unless you specifically allow it. Under settings -> Network, there is a tick box "Allow remote connections to this Emby Server." Tick the box and problem is resolved.

Hi, Same issue as the guys above. On any version above 4.6.4.0-3-01 I get a FORBIDDEN message when trying to access the dashboard via web browser. From the logs I find the following: 2022-03-16 11:03:18.765 Info Server: http/1.1 GET http://192.168.1.169:8096/favicon.ico. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36 Edg/99.0.1150.39 2022-03-16 11:03:18.765 Info Server: http/1.1 Response 403 to 192.168.1.100. Time: 0ms. http://192.168.1.169:8096/favicon.ico I've been stuck on this version and waited to try with the latest version but have the same error. What could be the problem.

Ok...This problem is still there. To recap, no changes to my system apart from an upgrade to 6.9.1 and now the local console won't boot into GUI mode. Any help or pointers please.

Still broken for me too! I was hoping there might be some words of wisdom on the forum, but I suspect I'm just going to have to live with thus bug. Sent from my SM-G970F using Tapatalk

This isn't solved. I have built in graphics (not a radeon). The server still does not boot into the GUI. The following commands work, but need to be issued on every reboot: Ctrl - Alt - F1 modprobe i915 /etc/rc.d/rc.4

Hi. Is there anyone who could give me some pearls of wisdom on this please?

I've seen these two posts, but I haven't changed anything apart from upgrading to 6.9.1. Thought I should check before tinkering. ps: I don't have any nvidia plugin installed

Hi All, After updating to 6.9.1 my unraid server won't boot into GUI mode. I've attached my diagnostics file. All help greatly appreciated. It boots to a blank after all the boot messages come up it ends up with a blank screen with a flashing cursor in the top left hand corner. The web gui is available by browsing to the server and it is functioning correctly, it's just the console with problems. Pete moose-diagnostics-20210422-1449.zip

Have a look at your secure boot settings. It should be set to "other os" Sent from my SM-N920I using Tapatalk

Glad tp hear it went well Sent from my SM-N920I using Tapatalk

Here's what I do when I replace a data drive: 1. Run a parity check first before doing anything else 2. Set the mover to not run by changing it to a date well into the future. This will need to be undone after the array has been recovered. 3. Take a screenshot of the state of the array so that you have a record of the disk assignments 4. Ensure that any dockers which write directly to the array are NOT set to auto start 5. Set the array to not autostart 6 Stop all dockers 7. Stop the array 8. Unassign the OLD drive (ie: the one being replaced) 9. Power down server 10. Install the new drive 11. Power on the server 12. Assign the NEW drive into the slot where the old drive was removed 13. Put a tick in the Yes I want to do this box and click start. The array will then rebuild onto the new disk. Dockers that don't write directly to the array can be restarted. When the rebuild is complete, the mover, docker and array auto start configuration can be returned to their normal settings. NOTE: You CAN write to the array during a rebuild operation, but I elect not to do so, to ensure my parity remains untouched for the duration of the recovery. Reading from the array is fine as the device contents are emulated whilst the drive is being rebuilt.

In case anyone is interested, the enclosures fit the Norco case. Just one small point the front cover of the case won't close with the drive cages installed but apart from that they are perfect. If you have the fan wall installed in the case, there is enough room between the back of the enclosure and the fans for cables.

Hi, You need calibredb if you want to keep you use calibre and want to keep your calibre library updated. If you point lazy librarian at your calibre directory it will move the books into that directory. There are two cases here: 1. If you DON'T use calibredb then calibre will have no idea that the book exists in it's directory. There will be no record of it in calibre. 2. If you DO use calibredb, then lazy librarian will move the book into the calibre directory. It will signal to calibre that there is a new book. Calibre will rename the book directory to it's standards (ie: the directory has a number in brackets after it). Lazy librarian will then be signalled to update it's database with the new directory name. To be able to use calibredb the lazy librarian docker needs to include a copy of calibre in its build. This is NOT the calibre you normally run. It is purely there to support the calibredb program. The Thraxis docker has calibredb support, but the linuxserver version doesn't. I found issues with the Thraxis docker which I reported above, hence I am now running the linuxserver version. My workflow is as follows: 1. When Lazylibrarian downloads the book and places it into the calibre directory, I move it out into another folder 2. I then run calibre and import the book into calibre 3. I then run a library scan on Lazy librarian so it updates itself. This could all be automated if the Thraxis docker worked correctly but for me it doesn't. You may have more luck.

OK. Found a problem with the docker and it looks like it has something to do with the way it's built. I opened an issue with the developer:-. https://github.com/DobyTang/LazyLibrarian/issues/1174 Found out that when clicking on the 'manual' link under an eBook, the docker causes segfaults in unraid similar to this: Jan 13 00:23:59 Moose kernel: python[3758]: segfault at 2acc7d79fff8 ip 00002acc762b46c7 sp 00002acc7d7a0000 error 6 in libpython2.7.so.1.0[2acc76246000+342000] Found a number of links that talk about how dockers are constructed and the various reasons they can cause this problem. As a test I installed the linxuserver version of the docker and the problem doesn't occur. Both versions of the docker were running the same commit level of lazy librarian, were configured identically and had the same number of ebooks and audiobooks ie: the only difference was the container Happy to help with any further information.

Hi, Would it be possible to have a docker update please? I'm working with the developer on a bug, and need the latest level (last commit from 9th January). Thanks

Thanks for the awesome docker. It's great that it has calibre integrated so that I can use calibredb. How do I upgrade the version of lazylibrarian running in the docker? Do I need to wait for docker updates or is there another way that I can do myself?

OK. I think the problem is that the lazy librarian docker needs access to calibredb to update the calibre database via the calibre content server. ie: calibredb is required whether or not you update the database directly or request it via the calibre content server This would imply that if calibre and lazy librarian are on different machines (or in separate dockers), then there is no way to update the calibre database as lazy librarian has no access to calibredb? Thoughts? Edit: Had the following update from the lazylibrarian developer: Yes that's exactly it. If calibredb is in the calibre docker then lazylibrarian can't see it. Only a problem if both are in separate dockers. The easy solution is to use a lazylibrarian docker that includes its own copy of calibredb, there is a link to one on the lazylibrarian home page. All you need do then is tell lazylibrarian the url of the content server, and where calibredb is located. In the Thraxis docker I think it's /opt/calibre/calibredb but the "test calibre" button will let you know if I've remembered that wrong. Is it something that could be considered for this docker ie: to include the necessary support to be able to run calibredb? Thanks

I have calibre and lazy librarian both using the one directory. I have the Calibre content server running so that LL can signal it to update itself by following these instructions: https://github.com/DobyTang/LazyLibrarian/wiki/Configuration I have configured calibre user/password and set up an account in calibre with user name and password. When Lazy librarian completes a download it copies the book into the appropriate directory, but Calibre is never updated. ie: the book does not appear in the calibre gui and the book directory never has the calibre book number appended. I tested the calibredb import program method by copying the calibredb program from the RDP-Calibre container to the Lazy Librarian container. Got permission denied messages. Still looking at that but its not really a great solution in my mind as it would mean I'd have to copy the file across every time a container is updated and also means I can't run the RDP-Calibre docker all the time. I did have a look at auto add in calibre, but all that happens is that I end up with two directories for the same book, because LL copies it into the calibre directory and then puts a copy in the auto add directory which calibre copies into the calibre directory. Any help would be appreciated. I turned debug on in LL and the only relevant entries were: 2018-01-07 22:13:24 DEBUG BookType: ebook, calibredb: [] 2018-01-07 22:13:24 DEBUG Processing eBook 5058

Ok made some progress here. change the proxy_pass statement to read proxy_pass http://192.168.1.169:8083/ NOTE: the trailing "/". This now works when I put in a URL of: https://urls_name_of_server/cops/ but doesn't work if I just put in https://urls_name_of_server/cops. With the second one I just get a blank screen (not a 404 not found now). I seem to be able to download books ok as well now.

Been trying to get reverse proxy working for COPS. I just keep getting "404 Not Found". Here's what I've coded: location /cops { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.169:8083; auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; } It all works if I'm on a local browser and go to http://192.168.1.169:8083 but it won't work if I am remote and go to https://url.name.of.server/cops thanks

I've got a Norco RPC-450B case. Would the supermicro CSE-M35T-1B enclosures fit?