Multiple Hosts and Misdirected Requests
Many sites use the same TLS certificate for multiple virtual hosts. The certificate either has a wildcard name, such as '*.example.org' or carries several alternate names. Browsers using HTTP/2 will recognize that and reuse an already opened connection for such hosts.

While this is great for performance, it comes at a price: such vhosts need more care in their configuration. The problem is that you will have multiple requests for multiple hosts on the same TLS connection. And that makes renegotiation impossible, in face the HTTP/2 standard forbids it.

So, if you have several virtual hosts using the same certificate and want to use HTTP/2 for them, you need to make sure that all vhosts have exactly the same SSL configuration. You need the same protocol, ciphers and settings for client verification.

# custom statuses in nginx-module-vts
map $status $status_vts {
  default   '';
  418      $status;
  499      $status;
}
map $status $server_name_vts {
  default   '';
  418      $server_name;
  499      $server_name;
}

vhost_traffic_status_filter_by_set_key $status_vts $server_name_vts;