ByteHeaven

Hi, great seems problem was fixed (or it got fixes when I was investigating problems with fans and switched from dynamic plugin to fanctrl plus :) ) But there was now update to this, and my fans did not go full blown tornado because of it :) Thanks by the way great add-on, had to look a way to shutdown Unraid with home assistant from Raspberry Pi when electricity price raise too high for my taste ;) (earlier had that docker api thing, but it stopped working after Unraid update, so had to look an alternative to give that simple shutdown command from HA..). Now this works again so I do not have to think about it.. almost... also victims on last Unraid update was NFS mount on MacOS... only fix atm seem to be: turn off NDS share, reboot server, turn on NFS shares when it goes to some mode "cannot connect" (even when Unraid lists them as shares). It loose it on every reboot or every network disconnection.. sorry for off topic...

Sure, I turned on debug logging, and get logs next time it does this and upload them :)

Hi, great, hope next update then fix this :) Just updated last version a moment ago (last nights build?) on manual update, and it did it, immediately when restarting this plugin. Fans went haywire full speed... Earlier: rebooting system fixed this, but tried other thing now and started disable/enable Fan auto controls, it did not help, but redirecting and applying them one by one fixed (which is annoying slow, so nice if this is on next update fixed, thank you :) ). Also atm rebooting is annoying, when there is some "feature" aka bug in 7.3.1 NFS (have to find where to put report on that), when you cannot mount NFS shares from Mac unless you a) turn of NFS b) reboot server c) turn on NFS (thanks Reddit for this instructions...). But that's off topic for this, just let you know how symptoms go and what fix them now, if your detection on next nights update fix this, nice (I have quite noisy server with all fans full speed :-D And it seldom needs that much cooling on, but it is good to be there when it is needed...)

Hi, I am not sure if it is this, or HA integration from HACKs for this, but I have checked through that it is every time this plugin have updated automatically, when all fans are in 100% on server.. does this conflict or override somehow Dynamix fan control? And is there fast and easy way to tell this "No you are not allowed to touch fan speeds, thank you" (I did disable fan controls from HA integration, but seems it does not help).

Because this is calibre docker problem. Calibre app works... docker webpage when opening it in browser is the one asking username and password... even when there is none set (or asked) on install in clean install of docker template... duh

Uh fun.. don't know what devs did this time, but that update 18h ago... now it asks username and password... nowhere is any info of any username and password... it does it even with completely clean install.. This is it for me with this docker, those devs can do what **** they want, it is just easier to use calibre desktop app on computer and tolerate it is slower when it reads files over network from Unraid share (and also kinda of annoying needing to open up app every time, instead just throwing files to auto import folder). But hey, this was 3rd time within a year they just f**** everything up and users are left for struggling hours what is wrong, and now it seems there even is no fix. As completely clean install wants to have some username and password which are not existing, not asked on install, nothing.... so somehow you should know some magic command to do at command prompt of the docker, which is even not told anywhere... thanks and buy, going to avoid this teams dockers forever if I can...

Ok this starts to be ridiculous. Not sure what you decided to break this time, but when starting calibre CPU goes to 100%, and it never starts, no errors anything in log... going back to linuxserver/calibre:8.6.0 and hoping to find alternative for this, because seems project is going very bad direction lately...

Ok step by step how I got it working after struggling 2 hours... 1: Uninstalled old calibre (it did NOT update so new required settings are there as I did NOT have https configured to be used.. the pem file was in folder but it did not use it or it was not working or something. So complete removal of old version) -edit- and of course if you are smarter than I was.. take screenshot first from all path settings you have to let calibre access your storage and make it for new setup exactly same way (that way when you replace old settings to new one it should straight away work just as before without fixing paths first as I did not remember mount points I had put paths on olden so made new ones and they were not same as old so calibre first wanted to get paths to books and had to fix also path to auto import...) btw: if any admin for docker devs read this: there is kinda of really stupid "feature" in the setting the paths. When it starts to reconfigure it will USE faulty path, die, and whole calibre docker disappear to orphans... just forgot to put / to first which of course is error but hey, maybe when applying it should refuse and tell there is error and not kill itself completely... one extra install again there for me when figuring this out without any decent instructions how to fix this mess and apologies maybe a bit angry comments before, I was rally pissed of and frustrated with this approach "let's kill this for everyone who do not understand everything under the hood completely" which is really a common sin for open source devs and how they approach things.. seems for you too.. and seriously main reason WHY these kind of systems never hit main stream.. because devs do not care to think how to make things simple and easy without understanding everything there). added with take out settings folder in app share (advice: rename old calibre folder to calibre-old) so it installs completely clean new one (if you have settings there it does not add required fields to settings, you probably could(?) add them manually and it would work(?) to existing one but at least for me, if I tried to replace app folder with old one after install, calibre just crash on start with error, thus something on old folders is conflicting with new version... HOWEVER in config folder there I replaced calibre folder with old config calibre folder and all my settings were saved, so at end did not loose all the fine-tuning done for my calibre setup) Then depending on if you need to fine-tune something (or try to get it working without cleaning whole system) in calibre docker settings remember advanced view And then you should have paths this way These are default settings for clean setup (I did NOT have without clean setup that last https port setting in settings at all.. thus.. update did NOT add that even when it is now required.. you probably can add that manually(?) did not try that One problem I had is that Unraid IS media server for me, so there is bunch of media related dockers. And Tautulli is conflicting with that port 8181. After tinkering figured out how to get it working (no I am not in-depth linux native understanding dockers etc. One reason why I have Unraid and ready made dockers in there.. I don't have to be... in these forums I find it sometimes very annoying when all instructions are on the level "hey do just this and this" with expectation everyone is just as natively swimming on linux console and understanding completely how docker works etc...) So Tautulli settings for avoiding conflict if you use Tautulli (with advanced view of course again). Now my Tautulli opens with port 8182 and is not conflicting with calibre...

And after figuring out 2 hours of wasted time... typical open source project again, where devs do not care at all about users... First: Update was fracked up, because it DID not do it correctly as it did not get working anyway... only way was (after figuring out to get tautulli to another port) was to completely wipe up settings (thanks a lot... so settings are now fracked up..) and install it completely as new... now it works... but a second I figure out something which works just barely enough I switch and abandon calibre...

Ok this starts to be really annoying.. really nice work from developers of calibre to break the *** up for bunch of people, who are NOT developers.. I managed? to change port but now it tells it cannot make secure connection?? Thus? What should I do? And the port conflicts with tautulli.. which use 8181 and haven't figured out how to get it working with any other port.. so they fracked up entire media server with that forced change.. So now I have error: ERR_SSL_PROTOCOL_ERROR And how can I fix that? Anyone have any actually working alternative for ebooks for calibre on server? Which does not have bunch of *** as developers?

Ok, after last update "Error: This application requires a secure connection (HTTPS). Please check the URL." Tryed to change webui to 8181 but Unraid tells it is in use? (does not accept it and start calibre with that?) So? How to fix?? AND WHY? If I have local calibre in my home network WHY are we forced to use HTTPS?

Anyone got this working lately? Or any other calibre-web docker? Since sometimes end of last year, this just never open webpage anymore... Tried to create empty library, delete all settings files and reinstall completely to empty library. Same, not starting ever no webpage opening... So anyone got any calibre-web docker working lately? Ok, either clean calibre-web from community store does not work, but this one did: https://github.com/crocodilestick/Calibre-Web-Automated So... myself now shutdown calibre docker for now, and investigate is this alone actually enough for me... but anyone else struggling with calibre-web never loading page and giving even any meaningful error to logs... this one worked for me now and have web-interface for my books library again... have to investigate library management in this, if this is replacing calibre also for managing importing and fixing book genres... And anyone supporting this calibre-web docker? It would be good to check why it does not work anymore with latest Unraid versions... it starts but never gives web interface... -edit- Just to info for others who might replace that non-working calibre-web with that calibre-web-automated which works... it's import well.. it works.. but is slow as h**l so at least myself going to run calibre aside for managing books... and that for web interface for the books library.. but seems It works without hick so after half a year again web interface for calibre... wondering if this official is ever fixed?

Thank you, I had the entire Unraid non responsive even after reboot through ssh (all dockers worked just fine, but no UI). Manually shut down Unraid-api through ssh and UI came responsive, trying now that 60 seconds... Just a stupid question, as I do not have a clue what that MQTTRefreshRate is, my need for this is: when electricity price goes over 18 euro cents, my HA from RPI4 shuts down cleanly Unraid through this. (and when price goes down again below that, same HA cuts down power on Meross plug after checking that power consumption is below 30 watts: thus Unraid IS shut down), counts to five and turns it back on, and server starts up... So, is that meaningful to have as low as possible so it works? Or can I through in something like 3600? Point being "poll for updates" for what? Does toggle "shut down this" works without poll? I do not need anything else from Unraid to my HA (this was only way I figured out how to get this working so it will automatically shutdown based on electricity price...)

There is still some problem with 6.12.4? I reupdated back to 6.12.4 some time ago, and now: UI completely unresponsive, it takes ages to load ui pages. When I managed to get to docker page, and shut down this API docker: everything works fine.. maybe need to roll back to 6.12.3, but just let you know, problem still is there. -edit- and yes, after downgrade to 6.12.3 everything seems to be responsive again.

Yes, found out it later after writing this. Sorry for first thinking there was something weird under the hood in this version causing this. (was still looking info after writing the post)