MyQ X Server
MyQ X Server
Breadcrumbs

Migrate Custom Traefik Rules

MyQ X 10.3 includes an upgrade of the Traefik reverse proxy. MyQ's own configuration is migrated automatically. If you have custom rules, you need to edit your rules file to use v3 syntax.

This page is relevant only if you have a non-empty traefik.custom.rules.yaml file (default location C:\ProgramData\MyQ\).

Steps to Prepare Your Custom Rules File

  1. Open traefik.custom.rules.yaml.

  2. Review every router rule, middleware definition, and TLS option against the official Traefik v3 migration guide: Traefik V3 Migration Documentation

  3. Apply the required changes and save the file.

  4. Run the MyQ upgrade.

Common v2-to-v3 Changes

The list below covers the most common changes. It is not exhaustive – cross-check your file against the official Traefik v3 migration guide for the complete set.

v2 syntax

v3 replacement

ipWhiteList middleware

ipAllowList

Host("a", "b") (multi-value matchers)

Host("a") || Host("b") (single-value with OR)

Headers(...) / HeadersRegexp(...)

Header(...) / HeaderRegexp(...)

HostHeader(...)

Host(...)

PathPrefix("/foo", "/bar")

PathPrefix("/foo") || PathPrefix("/bar")

PathPrefix with regular expressions

PathRegexp("...")

Path placeholders {name} inside matchers

PathRegexp("...") with a Go regex

sslRedirect, sslTemporaryRedirect, sslHost, sslForceHost headers options

redirectScheme middleware

featurePolicy headers option

permissionsPolicy

stripPrefix option forceSlash

Removed - no replacement

tls.options.default.preferServerCipherSuites

Removed - no replacement needed

tls.caOptional option

Removed - no replacement

When combining multiple matchers, note the v3 precedence rules: the NOT operator binds tighter than AND, which binds tighter than OR.

Traefik v3 can still process v2 rule syntax when core.defaultRuleSyntax is set to v2 or when v2 syntax is configured for an individual router. This compatibility mode is deprecated and is expected to be removed in the next major Traefik version. Existing v2 rules may therefore continue to work temporarily, but they should be migrated to v3 syntax.

After Upgrading

Check C:\ProgramData\MyQ\Logs\traefik.log for the following errors, which indicate remaining v2 syntax in your custom rules file:

  • error while parsing rule

  • headers configuration not valid

  • unknown middleware

If any appear, correct the relevant entries and restart Traefik.

See also: