Traefik 2.4.7. high TLS/SSL duration vs nginx

Traefik Traefik v2 (latest)
1

Today I switched from nginx 1.19 to traefik 2.4.7 as a reverse proxy in front of our applications running as Docker containers. I'm using Let's Encrypt for both setups to handle the SSL certificates.

After the switch I checked my monitoring dashboards and saw an increase in connection duration for tls from 10ms to around 65ms.

TLS probe duration
TLS probe duration2488×326 85.7 KB

Is this known issue, or something related to my configuration? The same increase in duration occurs with a single Host() rule.

In the configuration below host1.nl and host2.net are not the actual hostnames.

Container labels

labels:
  - "traefik.enable=true"
  - "traefik.http.middlewares.app-prd-redirect.redirectscheme.scheme=https"
  - "traefik.http.middlewares.app-prd-redirect.redirectscheme.permanent=true"
  - "traefik.http.routers.app-prd.rule=Host(`host1.nl`) || Host(`host2.net`)"
  - "traefik.http.routers.app-prd.middlewares=app-prd-redirect"
  - "traefik.http.routers.app-prd-secure.rule=Host(`host1.nl`) || Host(`host2.net`)"
  - "traefik.http.routers.app-prd-secure.tls=true"
  - "traefik.http.routers.app-prd-secure.tls.certresolver=myresolver"
  - "traefik.http.services.app-prd.loadbalancer.server.port=8080"

tls.options (dynamic.toml)

[tls.options]
  [tls.options.default]
    minVersion = "VersionTLS12"
    cipherSuites = [
      "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
      "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
      "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
      "TLS_AES_128_GCM_SHA256",
      "TLS_AES_256_GCM_SHA384",
      "TLS_CHACHA20_POLY1305_SHA256"
    ]
    curvePreferences = ["CurveP521", "CurveP384"]
    sniStrict = true

Main configuration

[api]
  insecure = true

[metrics]
  [metrics.prometheus]

[providers.docker]
  exposedByDefault = false
  network = "shared_default"

[providers.file]
  filename = "/etc/traefik/dynamic.toml"

[log]

[accessLog]
  filePath = "/var/log/traefik/access.log"
  bufferingSize = 100

[entryPoints]
  [entryPoints.web]
    address = ":80"

  [entryPoints.websecure]
    address = ":443"

[certificatesResolvers.myresolver.acme]
  email = "hosting@host1.nl"
  storage = "acme.json"
  [certificatesResolvers.myresolver.acme.httpChallenge]
    entryPoint = "web"
2

After a lot of reading about the cipher performance in Golang and finding the moz://a SSL Configuration Generator I've updated the tls.options to the values below.

This still results in an A+ score on ssllabs.com, but the tls duration has dropped from 65ms to around 18ms

New tls.options (dynamic.toml)

[tls.options]
  [tls.options.default]
    cipherSuites = [
      "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
      "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
      "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
      "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
      "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
      "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305"
    ]
    sniStrict = true
1 Like
3

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.