serve config not reproducing cli

[aredwood]

What is the issue?

Using tailscale serve set-config does not reproduce the same results as running tailscale serve.

Steps to reproduce

When I create a service using the cli (command below)
tailscale serve --service=svc:n8n --https=443 localhost:5678

the service is correctly exposed and available on the tailnet, when running tailscale serve get-config --all, this block is returned among other services.

        "svc:n8n": {
            "endpoints": {
                "tcp:443": "http://localhost:5678"
            }
        },

If i then clear the config using tailscale serve clear svc:n8n and then use tailscale serve set-config the service is not available to the tailnet, despite the config looking the same - the error returned to the client is ERR_SSL_PROTOCOL_ERROR.

I believe that the cli command, specifically the --https=443 portion is performing some action that is not captured with purely the config file alone.

This reddit post seems to hint at the same issue, indicating that this is at least 6 months old.

Are there any recent changes that introduced the issue?

not that I can tell, this seems to be persistent for me.

OS

Windows

OS version

Windows 11

Tailscale version

1.96.3

Other software

The service is running in WSL, exposed on localhost:5678 - Tailscale is installed on the windows host.

Bug report

No response