Traefik doesn't route TCP HOST SNI about traefik

[ldez]

Hello,

To keep the repository focused, we ask that all questions be asked in the community forum. It is pretty active, so you might find that your question has already been answered there.
If not, you can ask and get help from other community members pretty quickly.

[tareksalem]

I posed my question here as it hasn't been addressed in the community forum, and I'm concerned that this might be indicative of a bug.

https://community.traefik.io/t/traefik-doesnt-route-tcp-host-sni/20851

[tareksalem]

Anyone can please advise if this is an issue or the yaml files are miss configured. If it's an issue I would like to contribute and fix it.
Thank you

[tareksalem]

An update to the ticket, it seems like HostSNI works fined with traefik v3 but doesn't work with v2.10

[juliens]

Hello,

Please be aware that HostSNI is designed to function exclusively with the SNI TLS extension. Since PostgreSQL utilizes StartTLS instead of the conventional TLS, HostSNI is not compatible with PostgreSQL.

In version 3, we introduced a dedicated implementation for PostgreSQL (#9377). Although I haven't had the opportunity to test your specific use case, it appears to be related to this update.

[juliens]

When go back to this, I saw that you talked about the bug on v3 and then you talk about in v2 and not in v3.

Could you confirm whether the bug exists in v2 and does not appear in v3.
If you confirm it seems to be due to the expected limitation that HostSNI on PostgreSQL is not supported in v2. In such a scenario, we can consider the issue closed.

[tareksalem]

The issue exists in v2 not v3

[juliens]

Thank you for your answer, I close this issue as it is the expected behavior.