The way Tailscale works, you don’t need to worry to much about your local IP address. You can just use the Tailscale IP address and it will connect as if you were local using the fastest route. That’s the beauty of a mesh VPN. Each device knows the fastest route to each other.
Without more information I can’t really tell what issue you are actually having, but if your system has internet, you have a local IP and if the system is showing as up on your tailscale dashboard than it will have a tailscale IP. Not being able to connect using one or the other would be a configuration issue. Whatever service you are having trouble with is probably only listening to one of the interfaces but not the other.
I’m assuming you are running a linux or unix box, but try running the command ip addr. Assuming you have the package installed, it will tell you all of your IP addresses for the system you run the command on. The list may be quite long if you have a lot of docker containers running. The command tailscale ip will do the same but limited to your tailscale IP addresses.
Google and Github SSO were the only options when I originally setup tailscale. There are a few more options now including what looks like every self-hosted OIDC provider I’ve ever heard of, and a few I hadn’t.
There are a couple options depending on how you are using it. Most of the time I just use the
tailscalecommand to configure each node.Most systems were just
sudo tailscale up --sshto get it up and running, although I have one system setup as a subnet router to give me outside-the-house access to systems that I can’t put tailscale on. That was a little more involved but it was still pretty straightforward and well documented. Their documentation is actually very well written and is worth the read.