Updated 05/2024

Ask here for any Problems that might show up during Komf-Docker installation or usage.

Komf replaces all Metadata from what you're modifying!

 

Installation:

It's the same like you know for other Containers.

Fill in The required Fields and ignore the others when not needed.

 

Config:

If the application.yml is not automatically provided in the Appdata folder, download it from here: application.yml(08.05.2024).

Once added you can take a look at the advanced settings. Or set it up using the userscript.

If you are using only Kavita or Komga remove the sections of those you're not using from the yml.

 

Info:

Komf is currently an API project only. Unless you know how to deal with those you can join me in using the Userscript.

The Script adds a new button on the right of the usual config buttons in Komga:

It will let you Identify the Series and add Metadata to it.

 

Preparation Userscript:

You will need a Userscript manager. I took Snd-R's recommended one named Tampermonkey.

Download the Userscript from his Release-Section.

Tampermonkey should detect the script Download automaticly and ask if you want to add it.

If not follow this:

-Open the Settings from Tampermonkey.

-Drag and drop the js file in there.

-Press the install button.

 

Now you should see the Script in the installed Section.

Press the edit button on the far right.

 

Change the @include sections to your Komga/Kavita instances. Remove or add includes as needed.

 

Now save the changes under File.

 

You can now reload your Komga Tab and enjoy the Metadata Grabber.

 

If the Script wont keep your Komf url follow this:

 

General Links:

Github-Repro-Komf-Docker: https://github.com/Snd-R/komf

Github-Repro-Komf-Userscript: https://github.com/Snd-R/komf-userscript

Github-XML-Template: https://github.com/C3004/Unraid-Templates-C3004/blob/main/Komf-Docker.xml

Github-Repro-XML-Templates: https://github.com/C3004/Unraid-Templates-C3004

 

 

Edited May 8, 20241 yr by C3004
updated for 2024

Once I have the script installed, where in the UI do I see the option to add data?

 

User error, I got it working now!

 

Actually, it's not working. It's saying "no match found" for every single comic series I scan.

 

2nd edit: The metadata is did grab automatically was laughably wrong. 

Edited June 2, 20223 yr by Eraydien

Docker refuses to start with the following error:
 

13:03:09.689 [main] ERROR org.snd.Application - Failed to start the app
java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no scheme was found for
at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1261)
at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1634)
at org.snd.module.MediaServerModule.<init>(MediaServerModule.kt:96)
at org.snd.module.AppModule.<init>(AppModule.kt:29)
at org.snd.module.context.AppContext.refresh(AppContext.kt:39)
at org.snd.module.context.AppContext.init(AppContext.kt:29)
at org.snd.cli.Komf.run(Komf.kt:30)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:198)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:18)
at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:400)
at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:397)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:415)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:440)
at org.snd.ApplicationKt.main(Application.kt:20)

Not sure What to do, as far as I can tell I've filled out all requires fields correctly in the "application.yml" and docker template.
 

Hi Steven,

 

i took a short look. Could replicate the error.

Currently it seems to me that the docker won't accept that the Kavita fields are not filled in.

The Docker normaly should ignore kavita if the event listener is not activated.

 

I'll take a closer look later.

 

Anyway the latest version without kavita would be this one

sndxr/komf:0.12.0

but it's not kompatible with the new config.

 

I am also running into this. I don’t have Kavita but filed the fields out with bogus strings. 

The above issues are caused by the application.yml file not being generated by the docker.

Make one in the mounted config folder following the readme from the projects github and you'll be all good

Also running into this issue. Has anyone been able to resolve this? Even adding the application.yml file doesn't seem to sort it out on my end.

Hi
i have Komga running, and i've installed Komf docker, configured for Komga, API access. I didn't do anything regarding unser script, yet, but i'm wondering if Konf is doing anything as is now.
It does not seem to get any metadata. Is the userscript the only way to use komf with Komga?

Btw, is it better Komga or Katvia?

 

i got metadata for fresh added manga, but not for the over 1 thousand i already have
i installed tampermonkey and configured the userscript, but i keep getting error 400

from what i think i understood it's my browser that comunicate with both Komga and Komf, right?
So i have to use my vpn ip in both places in the script, considering i'm using a zerotier vpn between me and the unraid server?

 

I am receiving the following error in the logs when trying to use Komf with Kavita:

 

 

22:09:33.602 [RxCachedThreadScheduler-1] ERROR org.snd.mediaserver.kavita.KavitaEventListener -- kotlin.Unit
javax.net.ssl.SSLException: Unsupported or unrecognized SSL message

 

 

Any idea what might be causing this?

I have issues with the user script it seems. komf seems correct, it dosnt throw out any errors and says its connected to komga, its running on the same custom network as komga which I can access, but I cant get the user script to connect to komf. it tells me there is a network error when providing the url of komf which in my case is "http://192.168.1.4:8085". 

 

Im stumped. Why would the user script not be able to connect to komf? 

On 2/18/2024 at 12:41 PM, Ollebro said:

I have issues with the user script it seems. komf seems correct, it dosnt throw out any errors and says its connected to komga, its running on the same custom network as komga which I can access, but I cant get the user script to connect to komf. it tells me there is a network error when providing the url of komf which in my case is "http://192.168.1.4:8085". 

 

Im stumped. Why would the user script not be able to connect to komf? 

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

Now that Komf works for me again, i will make a new writeup or Video for the Komf setup (using the userscript).

I just set up Komf to try and streamline adding metadata to my comic library. Both Komf and Komga docker containers are up to date as of today.

 

I've managed to get Komf talking to Komga and got the userscript set up, but I'm running into a permissions issue for some reason. Every relevant file, share, etc., is set to "nobody" as owner and permissions are drwxrwxrwx (for folders) or -rw-rw-rw- (for files) across the board. Nevertheless, I keep getting an error that Komf doesn't have write permission to update files.

 

This is an example from my logs:

8:10:10.600 [JettyServerThreadPool-Virtual-7] INFO org.snd.mediaserver.MetadataService -- Setting metadata for series "Above Snakes 001-005 (2022)" MediaServerSeriesId(id=0F5CHDTDFYHCV) using COMIC_VINE ProviderSeriesId(id=144032)
18:10:11.595 [JettyServerThreadPool-Virtual-7] INFO org.jooq.impl.DefaultExecuteContext.logVersionSupport -- Version                  : Database version is supported by dialect SQLITE: 3.43.0
18:10:12.523 [JettyServerThreadPool-Virtual-7] INFO org.snd.mediaserver.MetadataUpdateService -- updating book Above Snakes 001 (2022)
18:10:12.528 [JettyServerThreadPool-Virtual-7] WARN io.javalin.Javalin -- Uncaught exception
org.snd.common.exceptions.ValidationException: No write permission for file /comics/Above Snakes 001-005 (2022)/Above Snakes 001 (2022).cbz
        at org.snd.metadata.comicinfo.ComicInfoWriter.validate(ComicInfoWriter.kt:145)
        at org.snd.metadata.comicinfo.ComicInfoWriter.writeMetadata(ComicInfoWriter.kt:80)
        at org.snd.mediaserver.MetadataUpdateService.updateBookMetadata(MetadataUpdateService.kt:118)
        at org.snd.mediaserver.MetadataUpdateService.updateBookMetadata(MetadataUpdateService.kt:89)
        at org.snd.mediaserver.MetadataUpdateService.updateMetadata(MetadataUpdateService.kt:51)
        at org.snd.mediaserver.MetadataService.setSeriesMetadata-_O6TCEk(MetadataService.kt:86)
        at org.snd.api.MetadataController.identifySeries(MetadataController.kt:92)
        at org.snd.api.MetadataController.register$lambda$1$lambda$0$identifySeries(MetadataController.kt:44)
        at io.javalin.routing.HandlerEntry.handle(HandlerEntry.kt:19)
        at io.javalin.http.servlet.DefaultTasks.HTTP$lambda$8$lambda$6$lambda$5(DefaultTasks.kt:39)
        at io.javalin.http.servlet.JavalinServlet.handleTask(JavalinServlet.kt:88)
        at io.javalin.http.servlet.JavalinServlet.handleSync(JavalinServlet.kt:53)
        at io.javalin.http.servlet.JavalinServlet.service(JavalinServlet.kt:41)
        at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
        at io.javalin.jetty.JavalinJettyServlet.service(JavalinJettyServlet.kt:58)
        at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:529)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1570)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)
        at io.javalin.jetty.JettyServer$start$wsAndHttpHandler$1.doHandle(JettyServer.kt:61)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1543)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1303)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129)
        at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:173)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
        at org.eclipse.jetty.server.Server.handle(Server.java:563)
        at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)
        at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)
        at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at java.base/java.lang.VirtualThread.run(Unknown Source)

 

I'd appreciate any help on this since I've been bashing my head against this for a few days now.

16 hours ago, magnuspraeda said:

I just set up Komf to try and streamline adding metadata to my comic library. Both Komf and Komga docker containers are up to date as of today.

 

I've managed to get Komf talking to Komga and got the userscript set up, but I'm running into a permissions issue for some reason. Every relevant file, share, etc., is set to "nobody" as owner and permissions are drwxrwxrwx (for folders) or -rw-rw-rw- (for files) across the board. Nevertheless, I keep getting an error that Komf doesn't have write permission to update files.

 

This is an example from my logs:

8:10:10.600 [JettyServerThreadPool-Virtual-7] INFO org.snd.mediaserver.MetadataService -- Setting metadata for series "Above Snakes 001-005 (2022)" MediaServerSeriesId(id=0F5CHDTDFYHCV) using COMIC_VINE ProviderSeriesId(id=144032)
18:10:11.595 [JettyServerThreadPool-Virtual-7] INFO org.jooq.impl.DefaultExecuteContext.logVersionSupport -- Version                  : Database version is supported by dialect SQLITE: 3.43.0
18:10:12.523 [JettyServerThreadPool-Virtual-7] INFO org.snd.mediaserver.MetadataUpdateService -- updating book Above Snakes 001 (2022)
18:10:12.528 [JettyServerThreadPool-Virtual-7] WARN io.javalin.Javalin -- Uncaught exception
org.snd.common.exceptions.ValidationException: No write permission for file /comics/Above Snakes 001-005 (2022)/Above Snakes 001 (2022).cbz
        at org.snd.metadata.comicinfo.ComicInfoWriter.validate(ComicInfoWriter.kt:145)
        at org.snd.metadata.comicinfo.ComicInfoWriter.writeMetadata(ComicInfoWriter.kt:80)
        at org.snd.mediaserver.MetadataUpdateService.updateBookMetadata(MetadataUpdateService.kt:118)
        at org.snd.mediaserver.MetadataUpdateService.updateBookMetadata(MetadataUpdateService.kt:89)
        at org.snd.mediaserver.MetadataUpdateService.updateMetadata(MetadataUpdateService.kt:51)
        at org.snd.mediaserver.MetadataService.setSeriesMetadata-_O6TCEk(MetadataService.kt:86)
        at org.snd.api.MetadataController.identifySeries(MetadataController.kt:92)
        at org.snd.api.MetadataController.register$lambda$1$lambda$0$identifySeries(MetadataController.kt:44)
        at io.javalin.routing.HandlerEntry.handle(HandlerEntry.kt:19)
        at io.javalin.http.servlet.DefaultTasks.HTTP$lambda$8$lambda$6$lambda$5(DefaultTasks.kt:39)
        at io.javalin.http.servlet.JavalinServlet.handleTask(JavalinServlet.kt:88)
        at io.javalin.http.servlet.JavalinServlet.handleSync(JavalinServlet.kt:53)
        at io.javalin.http.servlet.JavalinServlet.service(JavalinServlet.kt:41)
        at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
        at io.javalin.jetty.JavalinJettyServlet.service(JavalinJettyServlet.kt:58)
        at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:529)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1570)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221)
        at io.javalin.jetty.JettyServer$start$wsAndHttpHandler$1.doHandle(JettyServer.kt:61)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1543)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1303)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129)
        at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:173)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
        at org.eclipse.jetty.server.Server.handle(Server.java:563)
        at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)
        at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)
        at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
        at java.base/java.lang.VirtualThread.run(Unknown Source)

 

I'd appreciate any help on this since I've been bashing my head against this for a few days now.

 

Hi magnuspraeda,

 

This is the first time I ran into this Problem.

For your issue i found this thread on Github: https://github.com/Snd-R/komf/issues/92

Maybe Kohegas Solution could work for you: Add your Library the same way to komf as it is in Komga.

If that doesn't work please share your docker run for komf + komga.

 

Have a nice Day,

C3004

Edited February 27, 20241 yr by C3004

1 hour ago, C3004 said:

 

Hi magnuspraeda,

 

This is the first time I ran into this Problem.

For your issue i found this thread on Github: https://github.com/Snd-R/komf/issues/92

Maybe Kohegas Solution could work for you: Add your Library the same way to komf as it is in Komga.

If that doesn't work please share your docker run for komf + komga.

 

Have a nice Day,

C303

Thanks for taking a look at this. I hadn't seen that issue in my searches, but I'm not sure what Kohega means when they say, "After adding my manga location path to the komf docker container, no more writing issue" (and the last reply in the thread is asking Kohega what they mean, too).

 

I don't see anywhere in the Komf container settings or in the application.yml to add the location path. I do have my Komga base URI, user, and pw set in the yml.

Here's my redacted docker run command for Komf:

docker run
  -d
  --name='Komf'
  --net='bridge'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="CHOAM"
  -e HOST_CONTAINERNAME="Komf"
  -e 'KOMF_KOMGA_BASE_URI'='http://***.***.**.**:25600'
  -e 'KOMF_KOMGA_USER'='*******@*******.com'
  -e 'KOMF_KOMGA_PASSWORD'='************'
  -e 'KOMF_KAVITA_BASE_URI'=''
  -e 'KOMF_KAVITA_API_KEY'=''
  -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/appdata/Komf':'/config':'rw' 'sndxr/komf:latest'

767a1ff1b6cd794afa51f3e04dcb20d0fe2a0f70204217a815f9b38792d644b0

The command finished successfully!

 

And the one for Komga:

docker run
  -d
  --name='Komga'
  --net='bridge'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="CHOAM"
  -e HOST_CONTAINERNAME="Komga"
  -e 'KOMGA_LIBRARIES_SCAN_DIRECTORY_EXCLUSIONS'='#recycle,@eaDir'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:25600]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/selfhosters/unRAID-CA-templates/master/templates/img/komga.png'
  -p '25600:25600/tcp'
  -v '/mnt/user/Media/Comics/':'/comics':'rw'
  -v '/mnt/user/appdata/Komga':'/config':'rw' 'gotson/komga'

63dd323829af989b6b3c87712d25940a94519fad06727f2934ab66d2c4c5a004

The command finished successfully!

 

Thanks!

1 hour ago, magnuspraeda said:

Thanks for taking a look at this. I hadn't seen that issue in my searches, but I'm not sure what Kohega means when they say, "After adding my manga location path to the komf docker container, no more writing issue" (and the last reply in the thread is asking Kohega what they mean, too).

 

I don't see anywhere in the Komf container settings or in the application.yml to add the location path. I do have my Komga base URI, user, and pw set in the yml.

Here's my redacted docker run command for Komf:

docker run
  -d
  --name='Komf'
  --net='bridge'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="CHOAM"
  -e HOST_CONTAINERNAME="Komf"
  -e 'KOMF_KOMGA_BASE_URI'='http://***.***.**.**:25600'
  -e 'KOMF_KOMGA_USER'='*******@*******.com'
  -e 'KOMF_KOMGA_PASSWORD'='************'
  -e 'KOMF_KAVITA_BASE_URI'=''
  -e 'KOMF_KAVITA_API_KEY'=''
  -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/appdata/Komf':'/config':'rw' 'sndxr/komf:latest'

767a1ff1b6cd794afa51f3e04dcb20d0fe2a0f70204217a815f9b38792d644b0

The command finished successfully!

 

And the one for Komga:

docker run
  -d
  --name='Komga'
  --net='bridge'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="CHOAM"
  -e HOST_CONTAINERNAME="Komga"
  -e 'KOMGA_LIBRARIES_SCAN_DIRECTORY_EXCLUSIONS'='#recycle,@eaDir'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:25600]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/selfhosters/unRAID-CA-templates/master/templates/img/komga.png'
  -p '25600:25600/tcp'
  -v '/mnt/user/Media/Comics/':'/comics':'rw'
  -v '/mnt/user/appdata/Komga':'/config':'rw' 'gotson/komga'

63dd323829af989b6b3c87712d25940a94519fad06727f2934ab66d2c4c5a004

The command finished successfully!

 

Thanks!

Hi,

 

at the bottom of the screen click on Add another Path, Port ...

Configure it for your config, like this:

Now press add and lastly apply and wait for the container to start.

 

This should work. In the logs we see that it can't write to /comics/... which is the filepath the komga container sees internally. By adding it to komf it will have the access it did not have before.

 

Can you tell me what komf settings you use? I use api mode so i didn't run into this problem, but i think you may be using the comic_info mode to update the metadata - which would need the extra access.

 

Good Luck!,

C3004

Edited February 27, 20241 yr by C3004

3 hours ago, C3004 said:

Hi,

 

at the bottom of the screen click on Add another Path, Port ...

Configure it for your config, like this:

Now press add and lastly apply and wait for the container to start.

 

This should work. In the logs we see that it can't write to /comics/... which is the filepath the komga container sees internally. By adding it to komf it will have the access it did not have before.

 

Can you tell me what komf settings you use? I use api mode so i didn't run into this problem, but i think you may be using the comic_info mode to update the metadata - which would need the extra access.

 

Good Luck!,

C3004

Success! That fixed it!

 

Also, you're right that I did have it set to comic_info mode, but I had been getting the same permission error even when I had it set to API. It's working with either setting now, though.

14 hours ago, magnuspraeda said:

Success! That fixed it!

 

Also, you're right that I did have it set to comic_info mode, but I had been getting the same permission error even when I had it set to API. It's working with either setting now, though.

👍Ok, I'll add it to the template to prevent this issue in the future.

What do we put in the Komga USER and PSWD section if we are only using Kavita? It marks it as required. 

21 hours ago, Atreides said:

What do we put in the Komga USER and PSWD section if we are only using Kavita? It marks it as required. 

Hello,

 

1. Go to komf update menu

2. Switch to advanced mode

3. scroll to the komga user and passwd section

4. press edit there

5. Switch Required to no

Kind Regards

23:52:57.126 [main] ERROR org.snd.Application -- Failed to start the app
java.lang.IllegalArgumentException: Expected URL scheme 'http' or 'https' but no scheme was found for KOMF_K...
        at okhttp3.HttpUrl$Builder.parse$okhttp(HttpUrl.kt:1261)
        at okhttp3.HttpUrl$Companion.get(HttpUrl.kt:1634)
        at org.snd.module.MediaServerModule.<init>(MediaServerModule.kt:99)
        at org.snd.module.AppModule.<init>(AppModule.kt:30)
        at org.snd.module.context.AppContext.refresh(AppContext.kt:39)
        at org.snd.module.context.AppContext.init(AppContext.kt:29)
        at org.snd.cli.Komf.run(Komf.kt:30)
        at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:279)
        at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:41)
        at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:457)
        at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:454)
        at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:474)
        at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:481)
        at org.snd.ApplicationKt.main(Application.kt:20)

 

 

getting this in the logs, no idea why

Edited May 4, 20241 yr by Eraydien

@C3004 I have everything set up correctly but it just will not connect with the plugin and the logs show it won't even start because of the above error.

On 5/4/2024 at 8:23 PM, Eraydien said:

@C3004 I have everything set up correctly but it just will not connect with the plugin and the logs show it won't even start because of the above error.

Hi,

 

I replicated your error.

Remove the Komga Related Part in the application.yml file.

 

I'm using komga though? What do you mean remove it? Here is what I have with the password and user blanked

 

I removed the kavita part and got it working. Thanks for the inspiration. I apologize for not being more clear which service I was using!

Edited May 6, 20241 yr by Eraydien