mirror of
https://github.com/moghtech/komodo.git
synced 2026-05-21 07:11:29 -05:00
[GH-ISSUE #480] Cannot reach core under https (404) #2212
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.