Not trying to sound like an ass, promise. Have you declared those routes in Tailscale? There are two methods of doing this. One uses pathing, with --set-path, and not everything supports serving on a path without changing the base URI of the application you’re trying to reach. It looks like you’re sticking to ports, but I haven’t see anyone ask how you’re declaring this with the tailscale serve command.
And did you add a funnel, or just tailscale serve?
tailscale funnel --bg http://localhost:1234/
This is different, and I believe they are mutually exclusive.
The funnel would show as https://hostname.tailnet-name.ts.net/ to anyone online without needing tailscale, and that sounds like what you’re after as far as deduplicating bookmarks. If I’m not mistaken this only supports 443/8443/10000 ports, however. It’s also hanging free in the breeze for anyone to get to if they know the URL.
Again, sorry if this is asking redundant questions or anything.


I’ve never liked this approach - having to enroll certs on every machine always seemed tedious and it’s why I just “dealt with” having HTTPS errors internally for years.
Honest question, why not set up a reverse proxy that uses Let’s Encrypt? It will handle internal domains if configured appropriately, and then you only have to configure at the proxy and DNS level.