Known Issues

This page lists known issues with Varnish Controller; for example, identified bugs that are being worked on, along with potential workarounds. If not stated, these issues apply to all versions.

Router does not serve traffic after upgrade

After upgrading to version 7.3.0, the Router requires an updated Brainz to be available. If not, the Router can’t serve any traffic and will log the following error message

Got an error trying to unmarshal: json: cannot unmarshal number into Go struct field RoutingSet.routingSets.agents of type string

In this case, upgrade Brainz to the same release as the Router.

Same domain for multiple VCLGroups (request routing)

Only one VG can be deployed for the same domain to the router for it to be routed correctly. The router only knows about the domain of incoming requests and can currently not distinguish between different VCLGroups within the same domain. It won’t know which one the request should be routed to.

To route to a different set of servers (like Edge first, then Storage as fallback), create a second VCLGroup with a different domain, like example2.com. Use it as an External Route and use the External Route as a fallback in the first Routing Rule for the first VCLGroup. This will create an extra HTTP 302 redirect, but only when the first VCLGroup has no available servers.

- VCLGroup1
    - Domain: example.com
    - RoutingRule: rr1
        - Lookup-order: <decision>,external
        - ExternalRoutes: ext1
            - URL: http://example2.com
- VCLGroup2
    - Domain: example2.com
    - RoutingRule: rr2
        - Lookup-order: <decision>