Need help with Docker, Traefik and two independent services (Error: The group you requested does not exist.)

[BenRoe]

Hello,
i have problems to setup sablier with traefik v3.
I get the following error message in the browser.

Error Message in browser

{
    "availableGroups": [
        "whoami",
        "metadataRemote"
    ],
    "detail": "The group you requested does not exist. It is possible that the group has not been scanned yet.",
    "error": "group default not found",
    "instance": "/api/strategies/dynamic?display_name=My+Title\u0026group=default\u0026refresh_frequency=5s\u0026session_duration=1m\u0026show_details=true\u0026theme=hacker-terminal",
    "requestGroup": "default",
    "status": 404,
    "title": "Group not found",
    "type": "https://sablierapp.dev/#/errors?id=group-not-found"
}

traefik compose.yaml

services:
  traefik:
    image: traefik:v3.5.0
    container_name: traefik-benroe
    security_opt:
      - no-new-privileges:true
    # ports:
    #   - "80:80"
    #   - "443:443"
    #   - "8080:8080"
    environment:
      TZ: Europe/Berlin
      DYNU_API_KEY: ${DYNU_API_KEY}
    volumes:
      - /docker-data/traefik-benroe/letsencrypt:/letsencrypt
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - type: bind
        source: /docker-data/traefik-benroe/traefik.yaml
        target: /etc/traefik/traefik.yaml
        read_only: true
      - type: bind
        source: /docker-data/traefik-benroe/dynamic
        target: /traefik/dynamic
        read_only: true
    restart: unless-stopped
    networks:
      proxy-traefik-benroe:

  whoami:
    image: traefik/whoami
    container_name: whoami
    restart: unless-stopped
    networks:
      - proxy-traefik-benroe
    labels:
      - sablier.enable=true
      - sablier.group= whoami

networks:
  proxy-traefik-benroe:
    external: true

sablier compose.yaml

services:
  sablier:
    image: sablierapp/sablier:latest
    container_name: sablier
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - type: bind
        source: /docker-data/sablier/sablier.yaml
        target: /etc/sablier/sablier.yaml
    restart: unless-stopped
    command:
      - start
      - --provider.name=docker
    environment:
      TZ: Europe/Berlin
    networks:
      - proxy-traefik-benroe

networks:
  proxy-traefik-benroe:
    external: true

metadata-remote compose.yaml

services:
  metadata-remote:
    image: ghcr.io/wow-signal-dev/metadata-remote:latest
    container_name: metadata-remote
    # ports:
    # - "${SERVICE_PORT}:8338"
    volumes:
      - /media-data/music:/music/music1
    environment:
      - PUID=${UID}
      - PGID=${GID}
      - TZ=${TZ}
    security_opt:
      - no-new-privileges:true
    restart: unless-stopped
    networks:
      - proxy-traefik-benroe
    labels:
      - sablier.enable=true
      - sablier.group=metadataRemote

networks:
  proxy-traefik-benroe:
    external: true

traefik.yaml

global:
  checkNewVersion: false
  sendAnonymousUsage: false

api:
  dashboard: true

entryPoints:
  web:
    address: ":80"
    # Global redirect from HTTP to HTTPS
    http:
      redirections:
        entryPoint:
          to: websecure
          scheme: https

  websecure:
    address: ":443"
    # timeouts for immich
    # https://immich.app/docs/administration/reverse-proxy/#traefik-proxy-example-config
    transport:
      respondingTimeouts:
        readTimeout: "400s"
        idleTimeout: "400s"
        writeTimeout: "400s"

  traefik:
    address: ":8080"

certificatesResolvers:
  myresolver:
    acme:
      email: "my@email.de"
      dnsChallenge:
        provider: dynu
      storage: "/letsencrypt/acme.json"

providers:
  docker:
    watch: true
    exposedByDefault: false
    endpoint: "unix:///var/run/docker.sock"
    network: "proxy-traefik-benroe"
    constraints: "Label(`which.instance`,`benroe`)"
  file:
    directory: /traefik/dynamic
    watch: true

experimental:
  plugins:
    sablier:
      moduleName: "github.com/sablierapp/sablier"
      version: "v1.10.1"

log:
  level: WARN  # ERROR, DEBUG, PANIC, FATAL, ERROR, WARN, INFO

dynamic/metadata-remote.yaml

which:
  instance: "benroe"

http:
  services:
    metadata-remote:
      loadBalancer:
        servers:
          - url: "http://metadata-remote:8338"

  routers:
    metadata-remote:
      rule: "Host(`metadata.myDomain.de`)"
      service: metadata-remote
      middlewares:
        - my-sablier@file
      entryPoints:
        - websecure
      tls:
        certResolver: myresolver

dynamic/whoami.yaml

http:
  services:
    whoami:
      loadBalancer:
        servers:
          - url: "http://whoami:80"

  routers:
    whoami:
      rule: "Host(`whoami.myDomain.de`)"
      service: whoami
      middlewares:
        - my-sablier@file
      entryPoints:
        - web
        - websecure
      tls:
        certResolver: myresolver

dynamic/dynamic/sablier.yaml

http:
  middlewares:
    my-sablier:
      plugin:
        sablier:
          group: default
          dynamic:
            displayName: "My Title"
            refreshFrequency: 5s
            showDetails: "true"
            theme: hacker-terminal
          sablierUrl: http://sablier:10000
          sessionDuration: 1m

[acouvreur]

Hello simply update your dynamic/sablier.yaml traefik configuration file from

http:
  middlewares:
    my-sablier:
      plugin:
        sablier:
          group: default
          dynamic:
            displayName: "My Title"
            refreshFrequency: 5s
            showDetails: "true"
            theme: hacker-terminal
          sablierUrl: http://sablier:10000
          sessionDuration: 1m

to

http:
  middlewares:
    my-sablier:
      plugin:
        sablier:
-          group: default
+          group: whoami # Or metadataRemote dependning on which container you want to wake up using that middleware
          dynamic:
            displayName: "My Title"
            refreshFrequency: 5s
            showDetails: "true"
            theme: hacker-terminal
          sablierUrl: http://sablier:10000
          sessionDuration: 1m

---

Each group is used to define a set of containers that you want to wake up at once.

Each group can then be referenced by the Traefik plugin (as I've changed it for you).

You need to define a plugin for each set of container you want to wake at once.

If you need to have two distinct services, create two distinct middleware with the proper group.

[BenRoe]

Thank you for your answer, it helps.
If I understand correctly, I need to create a middleware for each stack/container group in the dynamic/sablier.yaml. If that is correct, what is the purpose of the group label - sablier.group=metadata-remote

dynamic/metadata-remote.yaml

which:
  instance: "benroe"

http:
  services:
    metadata-remote:
      loadBalancer:
        servers:
          - url: "http://metadata-remote:8338"

  routers:
    metadata-remote:
      rule: "Host(`metadata.myDomain.de`)"
      service: metadata-remote
      middlewares:
-       - my-sablier@file
+       - sablier-metadata-remote@file
      entryPoints:
        - websecure
      tls:
        certResolver: myresolver

dynamic/dynamic/sablier.yaml

http:
  middlewares:
-   my-sablier:
+  sablier-metadata-remote:
      plugin:
        sablier:
-         group: default
+         group: metadata-remote
          dynamic:
            displayName: "My Title"
            refreshFrequency: 5s
            showDetails: "true"
            theme: hacker-terminal
          sablierUrl: http://sablier:10000
          sessionDuration: 1m
+  sablier-whoami:
+      plugin:
+       sablier:
+          group: default
+          dynamic:
+           displayName: "My Title"
+            refreshFrequency: 5s
+            showDetails: "true"
+            theme: hacker-terminal
+          sablierUrl: http://sablier:10000
+          sessionDuration: 1m

[acouvreur]

Suppose you have a webapp which communicates with other containers (such as a database).
You want to create a group with the same name for both the service and its database, so that both the service and the database are woken up on demand.

[saschabrockel]

@acouvreur, that is exactly my use case, and I had the exact same question and came across this discussion. It might be worth adding it to the guides (imho). After all this time, I switched from NGINX Proxy Manager to Traefik just to be able to use your tool 😄

My question: there is also the names property, where you can add container names, comma-separated, so why should I use the group instead? Any advantages? I would even need to add these two labels to every container, is that correct?

    labels:
      - sablier.enable=true
      - sablier.group=metadataRemote

Seems counterproductive to me.