Here’s the rundown. Your device ip is only directly accessible when connected to your home network (local ip). Your router handles what content to display when connecting to a given local ip. However, when you’re off your home wifi, your router isn’t there anymore to decide what content goes where.
On the other hand, your router will have a public ip. You can access this ip from anywhere, and subsequently, access specific content through various ports. (That’s the :8989 or whatever). You definitely can access all your *arrs using http://: but this has some serious security issues. If you don’t care about the security issues then the public ip works fine, just make sure to use a secure password on all your *arrs.
What do you mean? I use it just fine remotely. You just need to point it to a domain name to redirect it. I used DDNS.net since it was free for the first domain.
Thanks, got it sorted now with tailscale and LunaSea. I have a password for sonarr and radar etc, am I pretty secure when you mention security issues to be cautious about?
tailscale is a mesh wireguard vpn, whereas cf tunnels is a zero trust solution
core difference is that with cf tunnel, your traffic will be proxied to cf servers, and then served to your device
tailscale on the other hand creates a mesh private vpn network for you, so you can access to your entire machine from your device, and all the traffic is encrypted
iirc with tailscale you can use an external auth service like google, github, etc… not sure about openid.
Mfa is “included” if you use google or github as auth service (these services will do the mfa)
tailscale has lots of documentation so you might find all your responses there
what’s actually happening is the servers are used to let nodes share their public keys more easily to other nodes, the servers never manages the private key, so security-wise it’s fine cause the coordination servers aren’t able to decrypt traffic
and if you’re really worried, you can still selfhost Headscale, which is a hostable open source coordination server replacement