June 5, 20242 yr I've made several attempts at setting up komf, but I believe I have reached a dead end. It seemingly cannot find the application.yaml file even though I have checked multiple times and assured that it was there. I have attempted to recreate the .yaml and the entire container several times at this point. Any help would be greatly appreciated.
June 7, 20242 yr I'm actually just a big dummy. I had to rename my application.yaml to application.yml. Woops!
November 15, 20241 yr Can't seem to get it running. I've ensured 5 times now that my application.yml is correct. Is it an issue with Komga?
November 15, 20241 yr Author 9 hours ago, mckenna654 said: Can't seem to get it running. I've ensured 5 times now that my application.yml is correct. Is it an issue with Komga? Hey Mckenna, I see this error for the first time. From the logs it seems that komf gets the event notifs from komga but can't process them right. To further help you please give me the docker run from Komga and Komf. Also your komf application.yml. Lastly set in komf the Loglevel to debug and give me those logs. Don't forget to Blackout/replace the api keys and passwords. Also answer these questions if posssible: Do only the event updates not work or also manually run searches? Does it fail on all series or only specific ones? If so which? Kind Regards, C3004
November 25, 20241 yr im not sure what to do to fix this i was having a diffrent issue before but figured that one out after a few days but im stuck here Desktop Screenshot 2024.11.25 - 01.16.00.25.jxr
December 16, 20241 yr Hello C3004, first of all, thank you very much for your work with Komf-Docker. It will be a great addition to Kavita when I get it up and running. And here we are... when using the function “Reset Metadata” for a single comic series, I get this error message “Failed to reset series: Request failed with status code 500” (I have not yet used the “Reset Metadata” function for the librarie). I also get this error message in the Komf log. 18:17:58.160 [RxCachedThreadScheduler-2] ERROR snd.komf.mediaserver.kavita.KavitaEventHandler -- kotlin.Unit The settings of Kavita and Komf are in the images (containers) I add the application.yml to this folder /mnt/user/appdata/Komf. And changed die application.yml, see image. Finally, I executed the script with the changes you described. I connected Komf in Kavita and tried to make the settings there. See also the pictures. Can you please help me. Kind Regards, Alukat11
December 17, 20241 yr Author 18 hours ago, Alukat11 said: Hello C3004, first of all, thank you very much for your work with Komf-Docker. It will be a great addition to Kavita when I get it up and running. And here we are... when using the function “Reset Metadata” for a single comic series, I get this error message “Failed to reset series: Request failed with status code 500” (I have not yet used the “Reset Metadata” function for the librarie). I also get this error message in the Komf log. 18:17:58.160 [RxCachedThreadScheduler-2] ERROR snd.komf.mediaserver.kavita.KavitaEventHandler -- kotlin.Unit The settings of Kavita and Komf are in the images (containers) I add the application.yml to this folder /mnt/user/appdata/Komf. And changed die application.yml, see image. Finally, I executed the script with the changes you described. I connected Komf in Kavita and tried to make the settings there. See also the pictures. Can you please help me. Kind Regards, Alukat11 Hey Alukat11, Here's what i noticed: In the komf docker run, you didn't set your kavita url (my guess: 192.168.2.5:5000). Since it is not set, komf tries to talk to the fallback localhost:80, which does not work. The localhost would be komf's own container since it is on the br0 network, and the port would also be wrong. Everything else looks fine. Just add the Kavita url to the komf template. Kind regards, C3004
December 18, 20241 yr You're right, I just had to set the Kavita url with http://192.168.2.5:5000 and it worked immediately. Thanks for your support.
January 25, 20251 yr i just wanted to thank you. This was a urge need for Kavita, and way more effective than Calibre. However, it doesn' run after installation. Here are the logs. 16:12:53.781 [main] ERROR snd.komf.app.Application -- Failed to start the app java.nio.file.NoSuchFileException: /config/application.yml at java.base/sun.nio.fs.UnixException.translateToIOException(Unknown Source) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(Unknown Source) at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(Unknown Source) at java.base/java.nio.file.Files.newByteChannel(Unknown Source) at java.base/java.nio.file.Files.newByteChannel(Unknown Source) at java.base/java.nio.file.Files.readAllBytes(Unknown Source) at java.base/java.nio.file.Files.readString(Unknown Source) at java.base/java.nio.file.Files.readString(Unknown Source) at snd.komf.app.config.ConfigLoader.loadDirectory(ConfigLoader.kt:15) at snd.komf.app.AppContext.loadConfig(AppContext.kt:203) at snd.komf.app.AppContext.<init>(AppContext.kt:81) at snd.komf.app.ApplicationKt.main(Application.kt:13)
January 25, 20251 yr Up: i forgot the /yml file. it's working. Now i'm trying to install the script...
January 25, 20251 yr ok so everyting is installed, the menu is showing up in kavita, but whith a connection error on Komf URL I've been checking in the docker, and it's correct http://192.161.1.6:8085 -------------------------- // ==UserScript== // @name Komf // @namespace https://github.com/Snd-R/komf-userscript // @version 0.12.2 // @description Komf userscript // @author snd-r // @include http://192.168.1.6:5000/* // @grant none // @run-at document-body // @updateURL https://raw.githubusercontent.com/Snd-R/komf-userscript/main/komf.meta.js // @downloadURL https://github.com/Snd-R/komf-userscript/releases/latest/download/komf.user.js -------------------------------- komf logs ------------------------------- 16:42:07.960 [main] INFO snd.komf.mediaserver.kavita.KavitaEventHandler -- connecting to Kavita event listener http://192.168.1.6:5000/hubs/messages 16:42:07.982 [main] INFO io.ktor.server.Application -- Autoreload is disabled because the development mode is off. 16:42:08.031 [OkHttp http://192.168.1.6:5000/...] INFO http.logging -- --> POST http://192.168.1.6:5000/api/plugin/authenticate?apiKey=2db97133-d1bc-4f8f-8e38-2274e1c89b90&pluginName=Komf (0-byte body) 16:42:08.046 [main] INFO io.ktor.server.Application -- Application started in 0.072 seconds. 16:42:08.060 [DefaultDispatcher-worker-2] INFO io.ktor.server.Application -- Responding at http://0.0.0.0:8085 16:42:08.120 [OkHttp http://192.168.1.6:5000/...] INFO http.logging -- <-- 200 OK http://192.168.1.6:5000/api/plugin/authenticate?apiKey=2db97133-d1bc-4f8f-8e38-2274e1c89b90&pluginName=Komf (88ms, unknown-length body) 16:42:08.164 [OkHttp http://192.168.1.6:5000/...] INFO com.microsoft.signalr.WebSocketTransport -- WebSocket transport connected to: ws://192.168.1.6:5000/hubs/messages?id=rThIbMZSPuY7pGPllVOl2w. 16:42:08.173 [OkHttp http://192.168.1.6:5000/...] INFO com.microsoft.signalr.HubConnection -- HubConnection started. 17:00:27.325 [main] INFO snd.komf.mediaserver.kavita.KavitaEventHandler -- connecting to Kavita event listener http://192.168.1.6:5000/hubs/messages 17:00:27.352 [main] INFO io.ktor.server.Application -- Autoreload is disabled because the development mode is off. 17:00:27.399 [OkHttp http://192.168.1.6:5000/...] INFO http.logging -- --> POST http://192.168.1.6:5000/api/plugin/authenticate?apiKey=2db97133-d1bc-4f8f-8e38-2274e1c89b90&pluginName=Komf (0-byte body) 17:00:27.416 [main] INFO io.ktor.server.Application -- Application started in 0.073 seconds. 17:00:27.430 [DefaultDispatcher-worker-5] INFO io.ktor.server.Application -- Responding at http://0.0.0.0:8085 17:00:27.432 [OkHttp http://192.168.1.6:5000/...] INFO http.logging -- <-- 200 OK http://192.168.1.6:5000/api/plugin/authenticate?apiKey=2db97133-d1bc-4f8f-8e38-2274e1c89b90&pluginName=Komf (32ms, unknown-length body) 17:00:27.477 [OkHttp http://192.168.1.6:5000/...] INFO com.microsoft.signalr.WebSocketTransport -- WebSocket transport connected to: ws://192.168.1.6:5000/hubs/messages?id=622_1PL9IIeX27Nj9SiMTA. 17:00:27.485 [OkHttp http://192.168.1.6:5000/...] INFO com.microsoft.signalr.HubConnection -- HubConnection started. Edited January 25, 20251 yr by logan23
January 25, 20251 yr Sorry for the fllod. I eventually did it (entering the config menu with the direct linlk Update : or almost. It still have a Network Error on the connection windows inside the kavita added menu, despite all the url are correct Apart of that, i'm not sure about a few things 1/ I'm try to set up the langages, and i cannot find (one of ) mines : french 2/ My books in kavita are mainly novels, and i'm not sure the existing providers of metadata are suitable. How can i add openbook library or Wordcart ? 3/ I've got other folder for manga/comics and magazines. Or does Komf deal with that ? Edited January 27, 20251 yr by logan23
January 27, 20251 yr Author On 1/25/2025 at 6:46 PM, logan23 said: Sorry for the fllod. I eventually did it (entering the config menu with the direct linlk Update : or almost. It still have a Network Error on the connection windows inside the kavita added menu, despite all the url are correct Apart of that, i'm not sure about a few things 1/ I'm try to set up the langages, and i cannot find (one of ) mines : french 2/ My books in kavita are mainly novels, and i'm not sure the existing providers of metadata are suitable. How can i add openbook library or Wordcart ? 3/ I've got other folder for manga/comics and magazines. Or does Komf deal with that ? Hi Logan, It's ok; I too had problems when the Userscript got a big update. Is the Komf url set inside the userscipt window? The @ include in the userscript only tells the script manager where to activate. The Kavita URL window should inherit the Url from your yml. In your second to last post you write that Komf has the url 'http://192.161.1.6:8085' while in the komf logs kavita has the url 'http://192.168.1.6:5000/' If you copy pasted these urls from your setup the Komf url has an error; you should change 192.161 to 192.168 . Now the questions. 1: The script is in english but if you set your provider to nautilijon (and move it to first postition or removing the others or agregating only their summary metadata) you should get their french metadata. 2: If you want different providers you have to ask on the komf Github page. For Novels i set mal as the first source but nautiljon seems to have both manga and novel metadata. To make sure you get the novel, not the manga metadata set in the processing tab the library type to novel. 3: Komf and Kavita deal with Comics manga and novels pretty well. nautilijon seems to have magazines, but i don't know if the script takes this data for identification. To make sure the media is identified correctly, save the different types in different folders and add them as their own libraries in kavita. Then set in komf the providers for each libraries directly; for your case nautilijon could work for all of them; but set another provider to identify those that nautilijon doesn't have. Lind Regards C3004 Edited January 27, 20251 yr by C3004
January 31, 20251 yr Many thanks for your feeback. Your right, the logs are showing an error Quote 14:31:19.178 [OkHttp http://192.1681.6:5000/...] INFO http.logging -- <-- HTTP FAILED: java.net.UnknownHostException: 192.1681.6: Name or service not known But i cannot fint it. - In the script, there are two URL, and they are correct. // ==UserScript== // @name Komf // @namespace https://github.com/Snd-R/komf-userscript // @version 0.12.2 // @description Komf userscript // @author snd-r @include http://192.168.1.6:5000/ // @grant none // @run-at document-body // @updateURL https://raw.githubusercontent.com/Snd-R/komf-userscript/main/komf.meta.js // @downloadURL https://github.com/Snd-R/komf-userscript/releases/latest/download/komf.user.js - In Komf docker kavita url is correct - In the yml, all i've got is baseUri: "http://192.168.1.6:5000" What am i missing ?
January 31, 20251 yr Author 3 hours ago, logan23 said: Many thanks for your feeback. Your right, the logs are showing an error But i cannot fint it. - In the script, there are two URL, and they are correct. // ==UserScript== // @name Komf // @namespace https://github.com/Snd-R/komf-userscript // @version 0.12.2 // @description Komf userscript // @author snd-r @include http://192.168.1.6:5000/ // @grant none // @run-at document-body // @updateURL https://raw.githubusercontent.com/Snd-R/komf-userscript/main/komf.meta.js // @downloadURL https://github.com/Snd-R/komf-userscript/releases/latest/download/komf.user.js - In Komf docker kavita url is correct - In the yml, all i've got is baseUri: "http://192.168.1.6:5000" What am i missing ? Hi, 1: in the log you just posted the url is missing a point. Change 192.1681.6:5000 to 192.168.1.6:5000. This url should be changed in the komka yml. 2: add the // back in the userscript before the @include or it won't activate. Something else i can't see right now. If it still doesn't work after the two changes above, recheck all urls. If you set the url directly in the komf yml you can ignore the url variable in the komf docker. Kind regards C3004
February 1, 20251 yr Hello, I'm not sure if i'm supposed to post this here, but just wanted to mention if anyone else was struggeling with getting COMIC_INFO to work because it gives a write permission error: This seems to be because the container path is set to /books while i think the container path should be /library. Please correct me if i'm wrong XD Thx.
February 1, 20251 yr Author 6 hours ago, Thundrglaive said: Hello, I'm not sure if i'm supposed to post this here, but just wanted to mention if anyone else was struggeling with getting COMIC_INFO to work because it gives a write permission error: This seems to be because the container path is set to /books while i think the container path should be /library. Please correct me if i'm wrong XD Thx. 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
February 26, 20251 yr Hello. Maybe you can help me. I am trying now for a week to only start Komf. I setep up evrything in the options. Deleted the options for the other portal (Kiva or what it is called), because i am just jusing Komga. Then i saw i need to add the application.yml. I also di that and added it manually (i got the application.yml from the komf github page and editedt to what i need and like). And Komf just doesnt want to sart. There are no logs nothing. After a second it just stops the container and out. I am loosing my mind because i don't know why. I will add my yml (i will just for the upload here replace evrything with the env Tag. In my yml on my server there are the actuall values written) application.yml
February 27, 20251 yr Author On 2/26/2025 at 11:47 AM, MasterOfKay said: Hello. Maybe you can help me. I am trying now for a week to only start Komf. I setep up evrything in the options. Deleted the options for the other portal (Kiva or what it is called), because i am just jusing Komga. Then i saw i need to add the application.yml. I also di that and added it manually (i got the application.yml from the komf github page and editedt to what i need and like). And Komf just doesnt want to sart. There are no logs nothing. After a second it just stops the container and out. I am loosing my mind because i don't know why. I will add my yml (i will just for the upload here replace evrything with the env Tag. In my yml on my server there are the actuall values written) application.yml 5.71 kB · 1 download 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 Edited February 27, 20251 yr by C3004 update yml
February 27, 20251 yr Hey C, thx for the fast response. I played now around with the cleand yml. And i can't bring it to run the docker still. I uploaded you version with the env varibles. Then i tried adding the same varible i added when building the container. Here is the docker run (Again removed pw and credentails seen with just a X): Removing container: Komf Successfully removed container 'Komf' Command executiondocker run -d --name='Komf' --net='bridge' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="MasterOfServer" -e HOST_CONTAINERNAME="Komf" -e 'KOMF_KOMGA_BASE_URI'='http://192.168.XXX.XX:25600' -e 'KOMF_KOMGA_USER'='XXX' -e 'KOMF_KOMGA_PASSWORD'='XXX' -e 'TZ'='UTC' -e 'KOMF_METADATA_PROVIDERS_MAL_CLIENT_ID'='XXXX' -e 'KOMF_LOG_LEVEL'='INFO' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://avatars.githubusercontent.com/u/76580768?v=4' -p '8085:8085/tcp' -v '/mnt/user/Media/books':'/books':'rw' -v '/mnt/disk3/appdata/Komf':'/config':'rw' 'sndxr/komf:latest' 714ef50b8e8f82f18a78d774243fec1d7405f71cb000543234e5a1a083946833 The command finished successfully! Edited February 27, 20251 yr by MasterOfKay
February 27, 20251 yr Author 1 hour ago, MasterOfKay said: Hey C, thx for the fast response. I played now around with the cleand yml. And i can't bring it to run the docker still. I uploaded you version with the env varibles. Then i tried adding the same varible i added when building the container. Here is the docker run (Again removed pw and credentails seen with just a X): Removing container: Komf Successfully removed container 'Komf' Command executiondocker run -d --name='Komf' --net='bridge' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="MasterOfServer" -e HOST_CONTAINERNAME="Komf" -e 'KOMF_KOMGA_BASE_URI'='http://192.168.XXX.XX:25600' -e 'KOMF_KOMGA_USER'='XXX' -e 'KOMF_KOMGA_PASSWORD'='XXX' -e 'TZ'='UTC' -e 'KOMF_METADATA_PROVIDERS_MAL_CLIENT_ID'='XXXX' -e 'KOMF_LOG_LEVEL'='INFO' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://avatars.githubusercontent.com/u/76580768?v=4' -p '8085:8085/tcp' -v '/mnt/user/Media/books':'/books':'rw' -v '/mnt/disk3/appdata/Komf':'/config':'rw' 'sndxr/komf:latest' 714ef50b8e8f82f18a78d774243fec1d7405f71cb000543234e5a1a083946833 The command finished successfully! 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. Edited February 27, 20251 yr by C3004
February 27, 20251 yr 2 hours ago, C3004 said: 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. Hey C, i tried that and the docker Container is still not starting. Even setting all env variables to the value i have set to my docer container still won’t let me start komf. It just stops after one second.
February 28, 20251 yr Author 21 hours ago, MasterOfKay said: Hey C, i tried that and the docker Container is still not starting. Even setting all env variables to the value i have set to my docer container still won’t let me start komf. It just stops after one second. 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
February 28, 20251 yr 1 hour ago, C3004 said: 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 I haven’t change the Name in the template and the container ( I tried that now but still just shuts down). And the logs are just empty. Just a black empty consol log where I can’t write.
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.