defaultRule in docker provider raise error in fileProvider:

Traefik Traefik v2 (latest)
6

The below is what is usually useful for diagnosing, apologies for partial repetitions, but I did not figure out how to keep it coherent without:

  • Provide your traefik static configuration file if you are using it. It is usually, but not always called traefik.toml.
  • If you are not using Docker/Kubernetes/Etc, provide the command line you are using to start traefik.
  • If you are using docker, but not docker-compose provide the command line that you are using to start traefik container.
  • If you are using docker-compose, provide your docker-compose file usually it's called docker-compose.yaml or docker-compose.yml
  • If you are using docker swarm provide your compose file that you are using with docker stack deploy
  • If you are using Kubernetes, please provide manifests for all relevant objects. There is a good working example here. Often kubernetes configuration do not work not because of a mistake in an IngressRoute but in the way Kubernetes is deployed. So make sure to include all kubernetes objects that are relevant. Here is a short checklist, note that it is not exhaustive, and may vary depending on your deployment. Add anything that is not mentioned here but relevant too. Note that not all of those item may always be present in your installation
    • Traefik Deployment/DaemonSet object
    • Traefik Service(s)/Ingress(es)
    • Traefik CRDs
    • Traefik security objects such as CluserRole(s), ClusterRoleBinding(s) and ServiceAccount(s)
    • Your application Deployment(s) / Service(s) / Ingress(es) / IngressRoute(s)
  • If your configuration uses any other files, in particular, if you are using file provider to load additional configuration, please provide those files as well.
  • Please enable debug log and provide relevant log entries. Note that the complete debug log can be overwhelming to post (use gist or pastebin), yet it is important that relevant parts of it are included. Here are the most useful parts of the log to provide:
    • Traefik dumps its static configuration on strart up, and dynamic configuration whenever it's received from a proivder to the log. Dynamic configuration is dumped repeatedly whenever it is received from each of the providers you are using. It is extremely useful for diagnostics, to provide this, as we can compare the config (expected) to the dump (what traefik actually sees), any descripansice help identify configuration issues
    • Any records that have word "error" (any case) in it, and a sufficently large portion of the log immediately preceeding those lines