It likely is a config issue, but likely not a config issue relating to SSH not using SSL/TLS (and therefor not using SNI). There is a lot of information out there about this exact issue, but very little about how to properly handle this issue.

• …stackexchange.com/…/why-doesnt-ssh-use-tls
• community.traefik.io/t/…/717
• docs.gitea.com/installation/install-with-docker#s…
• …stackexchange.com/…/what-is-the-difference-betwe…
• stackoverflow.com/…/does-ssh-use-sni-headers-and-…
• haproxy.com/…/route-ssh-connections-with-haproxy
• serverfault.com/questions/34552/…/610971#610971