Add the ability add a SNI or "serverName" to the serverTransports options.

[sbakker1970]

What problem does this solve?

With a SNI-based backend there is no option in the interface to add/apply/force a specific servername.

Proposed solution

add an extra option for the route

Alternatives you've considered

None realy except for manually adding "serverName"

---dynamic.yaml----
....
serversTransports:
transport:
serverName: "sni.san.whatever.name"
insecureSkipVerify: true
....
---dynamic.yaml----

Which area does this relate to?

Routes

Additional context

No response

[chr0nzz]

Thanks for the suggestion! This is now in the :beta image.

When you add or edit an HTTP route, there's a new Backend server name (SNI) field under Skip TLS Verification. Whatever you enter is written as serverName on the route's serversTransport (<service>-transport), next to insecureSkipVerify if you have that on. Clear the field to remove it.

To try it, switch to ghcr.io/chr0nzz/traefik-manager:beta (or run tm update --channel beta), then open the route and fill in the field. Note that your current transport is named transport. The first time you save the route from the UI, it moves the settings to a new <service>-transport and points the service at it. The old transport stays in your file, so you can delete it once you've checked the new one.

Let me know if it works with your SNI backend, and I'll include it in the next release.

[sbakker1970]

Works like a charm......as expected....
Also my manually edited entries get picked up .... as expected....
Nice work, thnx.