2 hours ago, MasterOfKay said:

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.

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.

Hey sorry for the long silence. I Had some personal stuff comming up. But yeah i found out why i didnt saw the logs (my fault on that). Now i see it and it is interesting. I get this:

20:18:45.219 [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)

 

THX for evrything and i hope we get it up and running finaly

Hey @C3004, would it be possible to add the Hardcover API for regular books to your project?

22 hours ago, p0p said:

Hey @C3004, would it be possible to add the Hardcover API for regular books to your project?

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

Ok so I have updated the userscript, how do I get Komf to utilize it?

I ran the script with User Scripts in Unraid. Rebooted the containers for Komf, Kavita and Komga but no change.

Edited July 23, 2025Jul 23 by Red___Fox
Updated with more info and image

16 hours ago, Red___Fox said:

Ok so I have updated the userscript, how do I get Komf to utilize it?

I ran the script with User Scripts in Unraid. Rebooted the containers for Komf, Kavita and Komga but no change.

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

Edited July 24, 2025Jul 24 by C3004

3 hours ago, C3004 said:

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

Perfect, this worked for me. Thank you.

I have both the Komga and Komf dockers installed. They both seem to be working fine and they look to be talking to each other. But I am not seeing the Komf controls injected into my Komga pages. I have tried on both Chrome and Firefox.

I am using the browser extensions as the script says it has been deprecated?

in looking at the console messages (in chrome) I see:

Failed to fetch chrome-extension://aeblfdkhhhdcdjpifhhbdiojplfjncoa/inline/injected.js, Import failed 3 times.
Final error: window.crypto.randomUUID is not a function

S @ inject-content-scripts.js:5Understand this error

This may have nothing to do with my error? I have goofled and I see some folks saying there are issues using http rather than https? But I am running these dockers local under http?

Thanks for any help....

OK - I did get it working. Before I got as far as above, I did have to download the yml file - the docker template does not do that.

I also tweaked a bunch of settings in the Komf docker - but not sure if that mattered or not.

I did get it to work on Chrome first - using the extension. And then on Firefox (my main broswer).

It is very hard to see the "jigsaw" icon as it is white. So maybe it was working for sometime? The final fix is once you get the jigsaw, there is a Komf setting in Komga - and I had to change the entry from local host to my actual local IP.

Edited January 12Jan 12 by TexasDave

On 2/19/2024 at 8:37 AM, C3004 said:

Hi Ollebro,

 

I ran into maybe the same Issue.

The Userscript is configured to try to connect to Komf on localhost and 'forgets' your settings when you restart the script.

 

So i recommend changing the adress in the Script itself (note that after updating your Script you will have to set this again)

 

In Tampermonkey use Find and search for localhost.

 

use find next next to the search bar until you see this:

In Line 19787 replace http://localhost... with your Komf server adress. (192.168.1.4:8085) You can skip the http:// it worked without in my case.

 

That should keep the Script from forgetting your komf adress (until the next script update)

 

Also make sure you've set your komga and kavita adresses to let the script be active there.

 

Good Luck, Have Fun

This appears to not work any longer. I have made the updates in my user script to be the IP address and have tried restarting komf, komga, web browser etc but it still defaults to localhost. I have even validated in web dev tools that the IP is still there, so I am at a loss where it keeps drawing localhost from. I cannot unfortunately use the native Chrome extension as it also attempts to use localhost. Any ideas?