So I have a apple tv on the beta app and it wont connect to my server by ether openvpn or tailscale. this works fine on my android phone. This is an urgent issue for me so please fix asap. thanks.
A little more info:
I have tailscale running on pfsense and I also host an openvpn server on pfsense, for openvpn I am using vpn client bee and I see data going back and forth in pfsense Just the apple tv won't connect in the channels dvr app. thanks.
I am still having this bug. it doesn't work on wifi or ethernet yet it works fine on my android phone on the same remote wifi network via the same openvpn profile. I have tested multiple vpn client apps on my apple tv. HELP!!!
You would have to submit diagnostics from the device you're having problems with for us to look into it.
1 Like
logs uploaded not sure how you will find them as it did not give me a code.
Even when submitting from a client, the code is available in the web ui under support > logs
except it won't connect to the server over vpn.
so what do my logs show? thanks.
They don't show anything. I don't see a VPN interface, but it does appear that the local network that you are on when you're remote happens to match your home local network, which could cause confusion to your VPN setup.
If you use Tailscale, it provides you with a different netblock that doesn't collide with local networks that may work around your issue.
The issue you're running into is network related and not anything our app can work around.
tailscale does not work ether.
1 Like
Did you use the Tailscale IP to connect?
I host tailscale on pfsense so I used my lan address.
With Tailscale subnet routing and required forwarding enabled?
1 Like
eric: So I connected channels to tailscale via the built in implementation, connected my apple tv to tailscale and connected using channels direct tailscale ip addess and it actually worked wow!!! thanks for the tip.
bnhf: yes
@techpro2004 When you're trying to use a Tailscale subnet router, the remote and local LANs need be different, non-overlapping subnets -- like 192.168.1.0/24 and 192.168.2.0/24.
1 Like
bnhf: Thanks for the tip. I figured seeing as how my server ip does not exist on the remote network it would be enough but I was wrong.
eric: in tailscale it shows your implementation is over 10 versions out of date is this for a reason or should you update it?
We ran into issues with newer versions we weren't able to track down, so until we can get to the bottom of it, we'll be using that version.
thanks for the reply. I understand.