[Idea] Pass env to the app for host rule

[ahmaddxb]

What problem does this solve?

Host(plex.{{env DOMAINNAME0}})

Proposed solution

Allow env in host rule to be resolved for ping http routes to work

services:
  traefik-manager:
    image: ghcr.io/chr0nzz/traefik-manager:latest
    container_name: traefik-manager
    restart: unless-stopped
    networks:
      - reverse-proxy
    ports:
      - "5000:5000"
    environment:
      - COOKIE_SECURE=true
      - CONFIG_DIR=/app/config/traefik
      - STATIC_CONFIG_PATH=/app/traefik.yml
      - $DOMAINNAME0 # Pass the domain name variable to the app for host rule in routes

Alternatives you've considered

No response

Which area does this relate to?

Routes

Additional context

No response

[chr0nzz]

Good catch, this is a real gap. You shouldn't need to pass the variable to Traefik Manager though.

Traefik expands Go templates when it loads the file, and its API hands back the finished rule. I checked with Traefik 3.5: a router written as Host(`plex.{{ env `DOMAINNAME0` }}`) comes back from /api/http/routers as Host(`plex.example.com`). So Traefik Manager can read the resolved host from the API it already talks to, instead of expanding the template itself. That avoids a second copy of the variable that could drift from Traefik's, and it works for every template function, not just env.

That's what the fix does. Routes with a templated host rule now get a launch link, a status dot from the reachability check, and a search match on the real host. Your config file keeps the template, so editing the route never writes the expanded host back to disk. If Traefik reports no router for a route, the row now says the host comes from a template Traefik has not resolved, instead of "the rule has no host".

It will be in v1.14.2, and is on :beta now, so you can try it before the release.

In the meantime, on a released build, you can edit the route and set a launch URL by hand. The reachability check uses that override too, so the ping works as well.

[ahmaddxb]

Yes your solution is more ideal, thanks will try it out.

[ahmaddxb]

I did try the :beta but its still the same

[ahmaddxb]

"you can edit the route and set a launch URL by hand" - I dont see where i can edit the launch url?

[chr0nzz]

You are right, I missed the Routes tab. The fix covered the Dashboard tab and the reachability check, so that card still shows the rule instead of the resolved host. Fix for it is coming tonight on :beta.

On the launch URL: it is not in the route edit dialog, it is a per-card setting on the Dashboard tab. Hover the card, click the pencil, and there is a Link URL field. You should not need it for this route once the Routes tab fix lands.

[ahmaddxb]

Oh man, I didn't even have the dashboard tab enabled in settings.

[ahmaddxb]

I just noticed something kind of strange in the routes section I only see route defined manually in yaml, I don't see any that are done with docker Traefik labels. I do see them in the dashboard section.

Dashboard

Routes

Is this intended?

[chr0nzz]

That part is intended. The Routes tab lists the routes Traefik Manager can edit, which means the ones in the dynamic config files it manages. A route from Docker labels is owned by the container, and a Redis route by the key in Redis, so Traefik Manager will not offer to edit them there.

They are not hidden, they each have a provider tab: Docker and Redis in your sidebar, one card per route with rule, service, entry points, middlewares and the detail panel, marked read-only. The Dashboard deliberately shows everything Traefik serves, whatever the provider, which is why they appear there.

Short version: Dashboard is everything, Routes is what you can edit here, provider tabs are everything else, read-only at the source.

One thing in your screenshots I would like to rule out before calling it settled. You searched whoami in both. The Dashboard finds matches, the Routes tab says "No routes match your filters". That is expected if every whoami route comes from Docker or Redis. But if any one of them is defined in a YAML file, the Routes tab should be showing it and that would be a real bug.

Could you check whether any whoami route is defined in a config file rather than by labels or in Redis? If one is, tell me its name and I will chase it.

[ahmaddxb]

whoami is only in docker labels

[chr0nzz]

Thanks, that settles it. All Docker, so the Routes tab is behaving correctly and there is nothing to chase.

That also explains the earlier confusion, and it was my fault for not asking sooner. The templated host fix landed on the Dashboard tab and the reachability check, so with that tab switched off there was nothing to see. Same for the Link URL advice, that field lives on a Dashboard card.

If you want it: Settings, Interface, Tabs, Dashboard. It is the launcher view, one card per route with status dots, groups and icons.

Either way the Routes tab fix is still coming tonight on :beta, so the templated host will resolve there too and you will not need the Dashboard for it.

[chr0nzz]

The Routes tab fix is on :beta now.

The Routes tab parsed the rule in its own code and skipped any host built from a template. It now reads the host Traefik resolved, so your plex route shows plex.your-domain with a working link instead of the raw rule. The same was true in three other places, all fixed in the same change: the route map, the domain filter, and the certificate matching that pairs a route with its certificate.

Your config file still keeps the template. Nothing writes the expanded host back.

Pull ghcr.io/chr0nzz/traefik-manager:beta. It ships in v1.14.2 along with the Raw YAML fix from #185.

[chr0nzz]

v1.14.2 is out: https://github.com/chr0nzz/traefik-manager/releases/tag/v1.14.2

ghcr.io/chr0nzz/traefik-manager:1.14.2 (also latest) carries the fix, so the beta tag is no longer needed.

A rule that builds its host with a Go template, such as Host(`plex.{{ env `DOMAINNAME0` }}`), now uses the host Traefik actually resolved. That applies on the Dashboard, the Routes tab, the route map, the domain filter and certificate matching, so those routes get a launch link, a status dot and a search match like any other. Your config file keeps the template exactly as written.

The missing Docker and Redis routes on the Dashboard were a separate bug in the same area: the agent router list was being read as though its completeness flags were routers, which broke agent routes entirely. That is fixed too.

If anything still looks wrong on 1.14.2, say so here and I will pick it back up.