Snd-R
Komf Kavita Network Error
I tried installing Komf from docker for my Synology DS420+
I first created "komf" folder and "config" subfolder in my docker folder: I also put the application.yml file inside the config subfolder. I use the code from kavita wiki.
kavita: baseUri: "http://192.168.1.134:5471" #or env:KOMF_KAVITA_BASE_URI apiKey: "YOUR_API_KEY_HERE!" #or env:KOMF_KAVITA_API_KEY
database: file: /volume1/docker/komf/config/database.sqlite # database file location.
I then use portainer to compose the docker container, the compose file is from komf wiki:
version: "3.7" services: komf: image: sndxr/komf:latest container_name: komf ports: - "8085:8085" user: "1000:1000" environment: - KOMF_KAVITA_BASE_URI=http://192.168.1.134:5471 - KOMF_KAVITA_API_KEY=my-api-key - KOMF_LOG_LEVEL=INFO # optional jvm options. Example config for low memory usage. Runs guaranteed cleanup up every 3600000ms(1hour) - JAVA_TOOL_OPTIONS=-XX:+UnlockExperimentalVMOptions -XX:+UseShenandoahGC -XX:ShenandoahGCHeuristics=compact -XX:ShenandoahGuaranteedGCInterval=3600000 -XX:TrimNativeHeapInterval=3600000 volumes: - /path/to/config:/config #path to directory with application.yml and database file restart: unless-stopped
The container is created successfully. I then setup the tampermonkey based on the kavita wiki. https://wiki.kavitareader.com/guides/external-tools/komf
The jigsaw icon appeared but I cannot connect it to Kavita. It says network error.
Any idea how to fix this?
Depending on your docker implementation and network, you don't want to use your IP as your KOMF_KAVITA_BASE_URI value. Instead of 192.168.1.134 you probably want to point it at the name of your container on your docker-network. Assuming your komf and kavita containers are on the same box, I don't think there should be any use of of IP's, just ports and container names.
Part of the guide goes over this. Arguably it should be built in the docker-composable, but that could introduce some other issues for different configurations:
if you don't already have a komga or kavita network you'll need to network create a new one docker network create my_network attach komf and media server to new network: docker network connect my_network komga_or_kavita docker network connect my_network komf start the container docker start komf
Depending on your docker implementation and network, you don't want to use your IP as your KOMF_KAVITA_BASE_URI value. Instead of 192.168.1.134 you probably want to point it at the name of your container on your docker-network. Assuming your komf and kavita containers are on the same box, I don't think there should be any use of of IP's, just ports and container names.
Part of the guide goes over this. Arguably it should be built in the docker-composable, but that could introduce some other issues for different configurations:
if you don't already have a komga or kavita network you'll need to network create a new one docker network create my_network attach komf and media server to new network: docker network connect my_network komga_or_kavita docker network connect my_network komf start the container docker start komf
OK so I checked from portainer that I already have a default kavita network "kavita_default". Do I just add komf to the "kavita_default" network?
If I need to create a new network and attach both containers, can I do the whole process via portainer?
Yes I think adding komf to your kavita_default network should get it working. But I've never used portainer before so I can't be sure.
If you figure it out be sure to post your solution in case anyone stumbles across this thread from google.
