Yes, I'm not the one having an issue. Works for me.
The only way to get to that setting is to somehow be connected first though. Catch 22
When you use the built-in Tailscale on your DVR Server and connect from your client, you select Connect at Home and key in the tailnet IP of your server, without the :port#.
So 100.100.100.100
Not 100.100.100.100:8089
Yes and I made that selection
1 Like
I finally got it to work. I’m not exactly sure what the problem was. I may have needed to wait for a short period of time before all the setting propagated across the net. I also updated the remote DVR server to the latest beta build. Thanks for all your help!
Just to be sure I’m doing this right: every time I want to switch between my local and remote DVR server, I have to enter the IP address (lan and tailscale, respectively) using the At Home option?
Correct
Did you get it working on the Apple TV?
One thing I noticed that is very cool.
Connect at Home via tailnet IP with my iPhone using cellular and wifi turned off.
Then turn wifi on and the app switched to my local DVR Server IP address.
Turn wifi off and it switched back to the tailnet IP.
If this is a bug, don't fix it!
1 Like
Yup and thank you for your help!
1 Like
Yes I got both my appletv and iPhone to work. Thank you for your help!
1 Like
I was playing around with tailscale some more this week.
1: i installed this on a 4k firestick in preparation for traveling. Ive noticed that when using the firestick and tailscale i had to do more transcoding than my IOS devices. I wound up having a client setting for “at home” around 4mb.
I think the processor in the firestick ARM chip just cant keep up with the additional tailscale encryption like an iphone or apple tv can, so when using tailscale on the firestick it needs more overhead. Can someone confirm this?
2: i just started using the debug—>tailscale feature the past two days.
Sometimes it works fantastic.
However , ive noticed on the sign in menu away from home, its forgetting the server address. Today, i had to go outside of the channels app on my ipad and use the dedicated tailscale app and connect that way.
3: There is also a race condition when you are prompted to enter the dvr tailscale ip, but in the background channels begins to load anyway, and you have to cancel the prompt.
I cant submit diagnostics right while its happening because im stuck inside the enter ip popup. Next time this occurs , ill hit cancel in the pop up and send diagnotics.
4: i noticed that with the built in debug enabled, i am able to connect by selecting “away from home” when away from home. Previously we had to connect using “at home”. Which can we use when using tailscale? I want to optimize my transcoding settings for my clients
2 Likes
Im using tailscale for more than just channels.
Ive wanted a way to have tailscale automatically turn on when im away from home, and turn off when i get home.
Stumbled across this today:
2 Likes
Any eta when tailscale will be in the Apple TV app release? (Not the beta)
Probably not until the summer.
1 Like
Not sure if this has been answered, so sorry if it has.
If I have a remote Apple TV connected through this tailscale IP, can I use that IP to control it via the API/Siri shortcuts?
1 Like
I definitely hope that someday you guys could enable this for Headscale @eric and @tmm1. The idea is great, but I imagine I'm not the only one who prefers to have the additional control a self-hosted option like Headscale would allow.
1 Like
Its really easy to add CustomURL support. For example see where I added the feature to golink: Adding custom control server (CustomURL) · tailscale/golink@2f63b0f · GitHub
Hope the Channels devs will consider even if its a hidden API feature only.
1 Like
Trying this with the latest apk from droid - seems to just give me a blank screen upon launch. Has anyone had similar issue?
This feature worked beautifully for several months. Connecting Channels DVR through Tailscale on my Tmobile Home Internet was fantastic after struggling to get it to work. I would like to keep using the solution but it seems that every few days I am forced to log in again from the server device. To clarify, I have to be on the host PC, open up channels, and then click the button that tells me I need to log into Tailscale. If I do not notice this, all of my connections from other devices to the Channels server are dead. Supposedly the credentials default to 180 days before the key expires (I confirmed in the Tailscale UI that this is how it is setup) but I have to login multiple times a week. I checked the logs and it does not even show an expired key being updated. Just a future-date-expiring key replaced by a later future-date-expiring key. I can't get this to stop. I am now on Xfinity and am considering just scrapping all use of Tailscale now but I would prefer not. Any thoughts on getting the login to Tailscale to stick for the full 180 days instead of 2-3?
2 Likes
Set it to Expiry Disabled. You want have to worry about login again.
1 Like
I'm fairly certain that I have tried this several times in the past with the same result. I'll try it again now as a sanity check but I know that I have used that option and was annoyed that it didn't work as expected. It also wouldn't explain why the logs give the expiration date in the far future but I am still forced to log in every few days. Thanks for the comment.
I have tried that too and after a few weeks it refuses to authorize ... I just Installed OPENVPN on my router and use that Instead.