Homarr•4mo ago

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 (/), but automatically redirects to /onboard where it hits me with a 404. Why? 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....

Jump to solution

4 Replies

Cakey Bot•4mo ago

Thank you for submitting a support request. Depending on the volume of requests, our team should get in contact with you shortly.

⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)

❓ Frequently Asked Questions | Homarr documentation

Can I install Homarr on a Raspberry Pi?

Tag•4mo ago

Does it hit you with homarr's 404 or traefik's 404? Onboard is the page to first setup homarr. There isn't just one page for homarr as you can have different boards and the management systems all accessible through paths, if you are blocking any path that isn't "/", then that might be the problem. We're not that well versed into kubernetes systems to help you much unfortunately, If I may, although we'll try to help here, you might have better chances to solve the issue quickly with TrueCharts. They provide a catalog for k3s including homarr and they now support more than just TrueNas Scale.

Solution

WAC•4mo ago

Tag•4mo ago

Perfect, great job. If you do have troubles with k3s in the future, the advice still stands. Thanks for including your solution, I'll mark this issue as resolved. Have fun with homarr ;)

Gaming

Programming

Deployed to k3s cluster running Traefik, IngressRoute only partially works; 404s on /onboard