C3004

Ok, Networks works. Tachidesk can access cloudflared too. I think the reason Tachidesk doesn't access Flaresolverr is because it gets the some other http status code. Flaresolverr only get's accessed when Tachidesk needs it to solve a captcha. It's good that it works on the windows pc (which client do you use there?), we can backtrack from there. So what are the differences between the both setups? Are the unraid host and Windows machine on the same network, and or the same internet connection? Is any of those using an vpn for internet access? Do your unraid server and windows machine use the same dns server and do they get the same answers?(Check with nslookup mangakakalot.gg on both machines; the container doesn't have the command, use the unraid console) If you still have the dns command on the container remove it. In the github keiyoushi issues tab the reasons i've seen so far for managakakalot to not work are only Ip-ratebans for too many requests. But that would affect the windows setup too(if they are on the same network). Otherwise you can try the different mangakakalot mirrors in the extension settings. Otherwise an old Tachiyomi post suggested deactivating dns over https, but suwayomi doesn't have that, so your upstream dns server decides that. Lastly enable debug logs in tachidesk and check what it says. Heres mine: One should first get the 403, then it should recheck over flaresolverr to get workable cookies and smoot sailing from there. Maybe one of the closed issues could help too: https://github.com/keiyoushi/extensions-source/issues?q=is%3Aissue%20state%3Aclosed%20mangakakalot Kind Regards

Okay, we seem to have two problems. First we need to get flaresolver to talk to tachidesk, second magakakalot seems to be one of the most ip-ban friendly agregators out there. For the first one: open the console of tachidesk and type curl http://flaresolverr:8191 If we get a failed to connect message we need to recheck the network setup; send the docker run of both containers for that. if we get the flaresolverr message body we check the tachidesk settings. Go to tachidesk webui goto settings --> server --> scroll down, there should be a flaresolver section. Here my setup: Now for the second problem. Mangakakalot seems to have a low threshold for ip bans to keep bots away. See https://github.com/keiyoushi/extensions-source/issues/13106. Recheck in your webbrowser if you can reach the site. If you get a bad response your ip got banned. In that case offload some titles away from mangakakalot. First try changing kakalot mirror; see here (from previous link discussion): Further we should migrate some titels away. My extension recommendations would be in order of priority: specific website of scanlator Mangadex MangaK (former batato) other sites (if batoto doesn't have it, search the title in your search engine and check if the resulting aggregators have an extension and then select one of those.) Kind Regards!

Hi! Having tested mangakakalot on my instance flaresolver must work or the site can't be accessed. My flaresolver log is: In what network mode is your flaresolver and tachidesk container? It seems you only got a response from flaresolver when you had the tachidesk container in the host network mode, so it was using the host unraid network stack, which means the requests went through your home network, which can lead to many issues. (Ports you map in docker edit are mapped from the internal docker network to your servers ip adress. Only containers in host mode can access other containers this way) For better communication we want the containers in the same network stack. We can either use the base unraid bridge network and use the container ip's (set according to container startup; ip needs to be locked otherwise it changes almost every time) or we use a user defined docker network, in which the container name is the container hostname and can be used instead of the ip. I don't want to bother with the standard docker bridge so here is the setup for the user defined bridge: create bridge in unraid console: docker network create manga edit flaresolver container, set network type to custom: manga edit tachidesk container, set network to custom: manga scroll down to show more settings; set allow flaresolver_enabled to true; set flaresolverr_url to http://FLARESOLVERRCONTAINERNAME:8191 Try this. If it doesn't work please share the flaresolver logs too. Kind Regards

Hi coresplinter, Was the backup created by the ghcr.io/suwayomi/tachidesk:v2.1.1930 preview version?

Hi Iceburn, Docker standard is Umask 0022. The umask can be changed in the dockerfile, but you would have to build the container yourself then. Could a different unraid group/user accomplish what you need the umask for?

Hello Coresplinter, I migrated fromk preview branch to stable branch with these steps: 1: Create backup in Preview. I got in the latest preview an error creating and later one in using the backup. The stable preview i used is ghcr.io/suwayomi/tachidesk:v2.1.1930 2: Make sure the backup was downloaded to your PC. 3: Shutdown Container 4: Move The Tachidesk folder out of the Appdata folder to use as a Backup! if anything goes wrong and to clean the working environment of tachidesk. 5: Change the Container in the Unraid UI to the stable branch: ghcr.io/suwayomi/tachidesk:stable 6: Start Container 7: In Tachidesk add the Keiyoushi extensions first and download your sources. (If you don't know your sources, the backup function will tell you later) 8: Load Backup in the settings. Depending on the size it could take a while. If the Backup file is correct you should get a confirmation screen if you want to use it. This will also tell you if you are missing sources. Copy the sources you are missing in notepad to download them later. Klick Restore to install the backup. Install will send you just to the extension screen. This is how i migrated my two containers. If there are any problems please ask.

Hi roobix and Vivent, so i checked the current preview and couldn't replicate the Error. So i guess they already fixed that. Anyway the Error read like the programm was not processing the config file correctly. So unless you edited the config file manually it was an error on the server side. As to why it was on the preview. Before the container had an internal user that on most unraid systems made problems. And only the preview version supported the docker user flag correctly to fix the user permission problems. Now i checked the latest release and the docker user flag is working correctly so i'll update the Template. One other thing directly migrating from the preview to the current latest gives me a sql error on the main page. Will look at it later but the migration should still be possible over the backup function. Kind Regards C3004

Hello RedFox, The Userscript will connect over your Browser with the API offered by the Komf container. Over the APi the script allows you to change the settings in komf and start metadata scans for your library. It won't work over the unraid Userscript Plugin as that one is meant for Bash or Shell scripts. You need to use a Browser script manager for the komf script. I use Tampermonkey. The script is being excecuted if you see the one next to the tampermonkey symbol in the browser bar. If you can't see the one, you need to recheck the url's you wrote into the Userscript for your media Servers. Once Logged into komga, you should see the added options from the userscript. Click on it and make your needed Settings. The first one would be to add the komga url, so the script can talk with the API. Then you can make the Media Server specific settings. In Kavita the Settings Symbol will be in the Top Right. Note that the Provider section in Komf will let you see the processing for both servers, so don't delete them by accident because they don't have the proper library title. Kind Regards C3004

Hi, I just made the template for CommunityApplications. You'll have to pitch your feature request at the github project. Some normal Book API's are already pitched there, but i do not know the implementation status. In the meantime you could try calibre for your normal books. I also saw a calibre plugin to edit comicinfo metadata, if your goal would be to have your normal library in Komga or Kavita, so you could try that too. Kind Regards

Do logs of other containers work? Resintall a second intance of komf over communicty applications; don't config anything(except port) let it run once and see if you get logs.

Can you recheck for logs? If the webui button does not work try following in console (Change container Name if you changed it in the Template): docker logs Komf

Ok, did a quick test. The yml i posted has a small error. the env:KOMF_SERVER_PORT won't work because i didn't put the environment variable in the template. Replace it with the port 8085. It should then start. you should be able to see logs then.

Hi Kay, The docker won't start if anything is wrong in the yml. I think it crashes because you didn't fill out the metadata providers. Remove them from the yaml and set them up using the userscript once komf starts. I added a cleaned yml to this comment. application.yml If it still won't work please post the docker run. Kind Regards, C3004

Added to the template 👍

Hi Thundrglaive, Your right. The /library is the usual mount for Kavita, while /books is the mount for Komga. I've updated the Template accordingly. Kind Regards C3004