Deployed to k3s cluster running Traefik, IngressRoute only partially works; 404s on /onboard
I've got a k3s cluster running, seemingly just fine. I've got a couple services deployed already, specificalyl Longhorn and it's UI with it's own IngressRoute functioning just fine.
I've deployed Homarr using the Helm charts and disabled the ingress provided therein. I've generated a certificate for this service and stored it in a secret.
I'm trying to setup an ingressroute in Traefik for this, but it's not entirely working. The service responds on the path I provided (
Here's my values file and IngressRoute manifest:
Values:
IngressRoute:
I've deployed Homarr using the Helm charts and disabled the ingress provided therein. I've generated a certificate for this service and stored it in a secret.
I'm trying to setup an ingressroute in Traefik for this, but it's not entirely working. The service responds on the path I provided (
/Here's my values file and IngressRoute manifest:
Values:
image:
repository: ghcr.io/ajnart/homarr
pullPolicy: IfNotPresent
tag: "0.15.0"
env:
TZ: "US/Eastern"
DEFAULT_COLOR_SCHEME: "dark"
AUTH_PROVIDER: "credentials"
service:
type: ClusterIP
port: 7575
targetPort: 7575
ingress:
enabled: false
persistence:
- name: homarr-config
enabled: true
storageClassName: "longhorn"
accessMode: "ReadWriteOnce"
size: "50Mi"
mountPath: "/app/data/configs"
- name: homarr-database
enabled: true
storageClassName: "longhorn"
accessMode: "ReadWriteOnce"
size: "50Mi"
mountPath: "/app/database"
- name: homarr-icons
enabled: true
storageClassName: "longhorn"
accessMode: "ReadWriteOnce"
size: "50Mi"
mountPath: "/app/public/icons"IngressRoute:
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
name: homarr
namespace: default
spec:
entryPoints:
- websecure
routes:
- match: Host(index.mydomain.net) && PathPrefix(/)
kind: Rule
services:
- name: homarr
port: 7575
tls:
secretName: certificate-homarr-mydomain-net
Solution
Thanks for the insight, but I fixed the issue!
I found an old GitHub issue for the project that indicated it doesn't seem to do well with self-signed certs (or something along those lines). This had me recheck that the certificate I had configured it to use was valid, which revealed that my browser was not updating it's cache from an earlier test I did wherein the certificate did not generate properly causing Traefik to assign it the default, self-signed Traefik certificate.
As soon as I re-deployed everything properly, wiped my cache, and reloaded everything worked.
I found an old GitHub issue for the project that indicated it doesn't seem to do well with self-signed certs (or something along those lines). This had me recheck that the certificate I had configured it to use was valid, which revealed that my browser was not updating it's cache from an earlier test I did wherein the certificate did not generate properly causing Traefik to assign it the default, self-signed Traefik certificate.
As soon as I re-deployed everything properly, wiped my cache, and reloaded everything worked.
