What is the issue?

There seems to be a discrepancy between the serve set-config and the cli serve --service command.
I'm trying to serve a docker registry over Tailscale service. I've tried to get https with service config. Only able to get https with the cli command. As seen in the status, I only get "HTTPS": true with the cli command.

Steps to reproduce

$ cat config.json
{
"version": "0.0.1",
"services": {
"svc:registry": {
"endpoints": {
"tcp:443": "http://127.0.0.1:5000"
},
"advertised": true
}
}
}
$ tailscale serve status --json
{
"Services": {
"svc:registry": {
"TCP": {
"443": {
"HTTP": true
}
},
"Web": {
"registry.my-net.ts.net:443": {
"Handlers": {
"/": {
"Proxy": "http://127.0.0.1:5000"
}
}
}
}
}
}
}
$ tailscale serve reset
$ tailscale serve --bg --service=svc:registry --https=443 127.0.0.1:5000
Available within your tailnet:

https://registry.my-net.ts.net/
|-- proxyhttp://127.0.0.1:5000

Serve started and running in the background.
To disable the proxy, run: tailscale serve --service=svc:registry --https=443 off
To remove config for the service, run: tailscale serve clear svc:registry
$ tailscale serve status --json
{
"Services": {
"svc:registry": {
"TCP": {
"443": {
"HTTPS": true
}
},
"Web": {
"registry.my-net.ts.net:443": {
"Handlers": {
"/": {
"Proxy": "http://127.0.0.1:5000"
}
}
}
}
}
}
}

Are there any recent changes that introduced the issue?

No response

OS

Linux

OS version

ubuntu server minimal 22.04.3

Tailscale version

1.92.1

Other software

No response

Bug report

BUG-0ed4d40d24199dbe698b410c34bed6a0d16d2b38517d3263ff68147053cd727c-20251216121624Z-017a49889af2122b