Traefik "entryPoint ... doesn't exist" in CI

By Kaveh Alemi·Latchkey

A Traefik router binds to an entrypoint name that the static config does not declare. Entrypoints are defined in the static file and referenced by routers; a missing name leaves the router unbound.

What this error means

Traefik logs "entryPoint X doesn't exist" and the router never starts listening on the expected port.

level=error msg="entryPoint \"websecure\" doesn't exist" routerName=my-router@file

Common causes

The entrypoint is not declared in static config

The router uses websecure but the static entryPoints block only declares web, so the name is unknown.

Static and dynamic config disagree on names

A rename in static config was not propagated to routers, leaving them pointing at an entrypoint that no longer exists.

How to fix it

Declare the entrypoint in static config

1. Add the entrypoint with its address under entryPoints in the static file.
2. Keep the router's entryPoints reference matching that name.
3. Restart Traefik so the new static config takes effect.

entryPoints:
  web:
    address: ":80"
  websecure:
    address: ":443"

Align router references with declared entrypoints

Update routers to reference only entrypoints that exist in static config.

http:
  routers:
    my-router:
      entryPoints:
        - websecure

How to prevent it

• Keep router entrypoint references in sync with static config.
• Remember entrypoints are static and only reloaded on restart.
• Validate both static and dynamic config in CI.

Frequently asked questions

Related guides

References

• Terraform documentation
• GitHub Actions documentation