I installed komodo with sqllite with default settings.
Komodo is behind traefik as reverse proxy.
The web UI is reachable under 192.168.1.11:9120, but the configured https:://komodo.example.com name isn't.
In compose.env I have set KOMODO_HOST=https://komodo.example.com
sqlite.compose.yaml:
services:
ferretdb:
image: ghcr.io/ferretdb/ferretdb:1
labels:
komodo.skip: # Prevent Komodo from stopping with StopAllContainers
restart: unless-stopped
networks:
- default
logging:
driver: ${COMPOSE_LOGGING_DRIVER:-local}
# ports:
# - 27017:27017
volumes:
- sqlite-data:/state
environment:
- FERRETDB_HANDLER=sqlite
core:
image: ghcr.io/moghtech/komodo-core:${COMPOSE_KOMODO_IMAGE_TAG:-latest}
labels:
- komodo.skip=true # Prevent Komodo from stopping with StopAllContainers
- traefik.enable=true
- traefik.http.routers.komodo.entrypoints=http
- traefik.http.routers.komodo.rule=Host(`komodo.example.com`)
- traefik.http.routers.komodo.middlewares=https-redirectscheme@file
- traefik.http.routers.komodo-secure.entrypoints=https
- traefik.http.routers.komodo-secure.rule=Host(`komodo.example.com`)
- traefik.http.routers.komodo-secure.tls=true
- traefik.http.routers.komodo-secure.service=komodo
- traefik.http.services.komodo.loadbalancer.server.port=9120
- traefik.docker.network=web
restart: unless-stopped
depends_on:
- ferretdb
networks:
- web
- default
logging:
driver: ${COMPOSE_LOGGING_DRIVER:-local}
ports:
- 9120:9120
env_file: ./compose.env
environment:
KOMODO_DATABASE_ADDRESS: ferretdb
volumes:
## Core cache for repos for latest commit hash / contents
- repo-cache:/repo-cache
## Store sync files on server
- /volume1/docker/komodo/syncs:/syncs
## Optionally mount a custom core.config.toml
# - /path/to/core.config.toml:/config/config.toml
## Allows for systemd Periphery connection at
## "http://host.docker.internal:8120"
# extra_hosts:
# - host.docker.internal:host-gateway
## Deploy Periphery container using this block,
## or deploy the Periphery binary with systemd using
## https://github.com/moghtech/komodo/tree/main/scripts
periphery:
image: ghcr.io/moghtech/komodo-periphery:${COMPOSE_KOMODO_IMAGE_TAG:-latest}
labels:
komodo.skip: # Prevent Komodo from stopping with StopAllContainers
restart: unless-stopped
logging:
driver: ${COMPOSE_LOGGING_DRIVER:-local}
env_file: ./compose.env
networks:
- default
volumes:
## Mount external docker socket
- /var/run/docker.sock:/var/run/docker.sock
## Allow Periphery to see processes outside of container
- /proc:/proc
## Specify the Periphery agent root directory.
## Must be the same inside and outside the container,
## or docker will get confused. See https://github.com/moghtech/komodo/discussions/180.
## Default: /etc/komodo.
- ${PERIPHERY_ROOT_DIRECTORY:-/etc/komodo}:${PERIPHERY_ROOT_DIRECTORY:-/etc/komodo}
volumes:
# Sqlite
sqlite-data:
# Core
repo-cache:
networks:
web:
external: true
Traefik seems to work just fine, since under the https address I have a valid lets encrypt cert.
Forget it :)
I did not add a local CNAME in my DNS server for the https address.
Now everything is working!
<!-- gh-comment-id:2851033397 -->
@juxeii commented on GitHub (May 5, 2025):
Forget it :)
I did not add a local CNAME in my DNS server for the `https `address.
Now everything is working!
Forget it :) I did not add a local CNAME in my DNS server for the https address. Now everything is working!
hi! same situation as you.
can u explain what have u done regarding dns?
in my case nslookup komodo.example.com resolves correctly.
also i installed traefik as container.
<!-- gh-comment-id:3003730529 -->
@Smig0l commented on GitHub (Jun 25, 2025):
> Forget it :) I did not add a local CNAME in my DNS server for the `https `address. Now everything is working!
hi! same situation as you.
can u explain what have u done regarding dns?
in my case `nslookup komodo.example.com` resolves correctly.
also i installed traefik as container.
@Smig0l Not sure what your question is. I have many services running with adguard/traefik and for this issue I simply forgot to add a DNS rewrite in adguard pointing to my traefik instance.
But I switched to technitium and here I setup the DNS resolution under a forwarder zone.
Look at traefik logs and see if there are even request coming along for komodo. Set log level to debug.
<!-- gh-comment-id:3003790555 -->
@juxeii commented on GitHub (Jun 25, 2025):
@Smig0l Not sure what your question is. I have many services running with `adguard/traefik` and for this issue I simply forgot to add a DNS rewrite in `adguard `pointing to my `traefik `instance.
But I switched to `technitium `and here I setup the DNS resolution under a forwarder zone.
Look at `traefik `logs and see if there are even request coming along for `komodo`. Set log level to `debug`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @juxeii on GitHub (May 5, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/480
Hi,
I installed
komodowithsqllitewith default settings.Komodo is behind
traefikas reverse proxy.The web UI is reachable under
192.168.1.11:9120, but the configuredhttps:://komodo.example.comname isn't.In
compose.envI have setKOMODO_HOST=https://komodo.example.comsqlite.compose.yaml:Traefikseems to work just fine, since under the https address I have a valid lets encrypt cert.Core log:
I have tried to
KOMODO_SSL_ENABLED=truebut then core shows errors:
Any ideas how to get
komodoworking behingtraefik?@juxeii commented on GitHub (May 5, 2025):
Forget it :)
I did not add a local CNAME in my DNS server for the
httpsaddress.Now everything is working!
@Smig0l commented on GitHub (Jun 25, 2025):
hi! same situation as you.
can u explain what have u done regarding dns?
in my case
nslookup komodo.example.comresolves correctly.also i installed traefik as container.
@juxeii commented on GitHub (Jun 25, 2025):
@Smig0l Not sure what your question is. I have many services running with
adguard/traefikand for this issue I simply forgot to add a DNS rewrite inadguardpointing to mytraefikinstance.But I switched to
technitiumand here I setup the DNS resolution under a forwarder zone.Look at
traefiklogs and see if there are even request coming along forkomodo. Set log level todebug.