this post was submitted on 21 Oct 2023
31 points (91.9% liked)

Selfhosted

40329 readers
426 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
31
Netflix on AndroidTV still blocks me with wireguard connection (lemmy.world)
submitted 1 year ago by MoshpitDaddy@lemmy.world to c/selfhosted@lemmy.world
15 comments fedilink hide all child comments
 

Hey guys,
I selfhost a server at home where I run a couple of services. Wireguard is one of them. I also have another house where I live every couple of weeks for a few days. Netflix blocked me on the second house for account sharing. As I run my own wireguard and the tv in the second house runs AndroidTV I created a wireguard config (I run wg-easy) and installed the official Wireguard app on AndroidTV. Sadly netflix still blocks me which is weird because all traffic of that tv seems to be running over the tunnel.

Here is the config:

` [Interface] PrivateKey = XXX Address = 10.8.0.3/24 DNS = 1.1.1.1 MTU = 1420

[Peer] PublicKey = XXX PresharedKey = XXX AllowedIPs = 0.0.0.0/0 PersistentKeepalive = 0 Endpoint = vpn.XXXde:51820 `

I also posted this on reddit selfhosted where it sadly got removed. Some suggestions were that somehow DNS requests or IPv6 traffic still got through without using the wireguard tunnel which doesn't make much sense because usually the wireguard app puts everything through the tunnel.
I also edited the conf to also tunnel all ipv6 traffic with adding ::/0 under allowed IPs but that also didn't resolved the problem.
Is there anything else I could try? Are there different solutions? I'm aware that there are other approaches to this problem (using Jellyfin) but I really want to figure out this problem as it doesn't make any sense to me. The whole traffic should be going over my home server and it seems it doesn't.
Has anyone gotten this kind of setup to work?

Thanks for any help, have a good day!

top 15 comments
sorted by: hot top controversial new old
[–] JoeKrogan@lemmy.world 6 points 1 year ago* (last edited 1 year ago) (1 children)

Did you try Netflix in the browser to rule out an issue with the app.

I have adguard home on my server and have the server wireguard IP as the DNS ip too so I can see all the DNS requests my devices make and block stuff. I disable ipv6 myself to keep things simpler.

It should work for you though.

Another option they can't detect is use a router with a wireguard connection, then Netflix can go suck a lemon πŸ‹πŸ˜‰

Edit: Perhaps they are doing some timing on your connections and there is a difference between your primary connection and the VPN one .

[–] andyburke@fedia.io 1 points 1 year ago

If Netflix is denying you access to the subscription you pay for because you're using a VPN to connect, that starts to smell like a good class action to me.

[–] BaalInvoker@lemmy.eco.br 5 points 1 year ago (1 children)

Haver you seem what's your ip and ipv6 on the foreingner house?

Maybe your wireguard connection is creating a lan, but you didn't configured an exit node or didn't connected to the exit node.

Another solution could be using Tailscale as well

[–] MoshpitDaddy@lemmy.world 0 points 1 year ago (1 children)

Yes. I installed a browser on the androidTV and it showed my local ip from back home (where the wireguard host runs) but no ipv6.

I have to look into the exit node thing as it doesn't say anything to me but thanks for the Idea!

Tailscale should have the same problem as it basically runs on wireguard as far as I know. Are there any other things tailscale itself changes? I will try it tho because why not. I could probably also try headscale as I rather stay on the open source side ?

[–] BaalInvoker@lemmy.eco.br -1 points 1 year ago

Tailscale only make easier to set exit nodes and manage wireguard setups... Try it and tell us what happens...

Anyway, I don't know exactly what's going on. Maybe you're forwarding some packages to your wireguard VPN, like TCP/80, but not UDP or TCP/443. Check if everything is being properly forwarded, so all your connection is from Wireguard

[–] JustinAngel@lemmy.world 4 points 1 year ago

Definitely complicated to root cause. Please share if ya figure out the hard parts πŸ˜„

An idea: Netflix could be fingerprinting TUN interfaces on the TV.

One thing I'd consider trying is Tailscale in userspace networking mode on a distinct network host at location 2, which'll start a SOCKS/HTTP proxy that the TV can use for outbound connections.

Bonus: any devices incompatible with Tailscale can use the proxies.

If you'd like to take a stab at this, Headscale is a self-hosted version of Tailscale's service. Personally, I use Caddy to automatically manage letsencrypt certs while proxying requests to Headscale.

[–] Decronym@lemmy.decronym.xyz 4 points 1 year ago* (last edited 8 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
IP Internet Protocol
TCP Transmission Control Protocol, most often over IP
UDP User Datagram Protocol, for real-time communications
VPN Virtual Private Network

6 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

[Thread #228 for this sub, first seen 21st Oct 2023, 17:15] [FAQ] [Full list] [Contact] [Source code]

[–] seang96@spgrn.com 3 points 1 year ago (1 children)

At the second home with the TV not working, I'd.suggest testing out wireguard on a PC that hasn't been used with Netflix yet and see if it has the issue too. This would also be easier to troubleshoot to find the root issue if it fails on the PC too.

[–] MoshpitDaddy@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

This would be complicated as you can use the Netflix service on a new device for at least 30 days without issues

[–] seang96@spgrn.com 1 points 1 year ago

It's probably cache or cookies. Netflix browser in private browsing would be a new session.

[–] krolden@lemmy.ml 2 points 1 year ago* (last edited 1 year ago)

Try adding ::/0 to your AllowedIPs

Edit: nvm you tried that

[–] ijeff@lemdro.id 2 points 1 year ago

No experience with this setup myself, but you may want to try !askandroid@lemdro.id.

[–] LDerJim@lemmy.world 1 points 1 year ago

Have you tried updating your Netflix Household via https://help.netflix.com/en/node/128339 ?

[–] coriolis@lemmy.world 1 points 8 months ago

Did you solve it? I am in the same situation and nothing seems to help... Maybe wireguard, being inside a docker bridge network, isn't forwarding correctly IPV6 packets. Or maybe Netflix checks more than just the public IP

[–] PoliticallyIncorrect@lemmy.world 0 points 8 months ago

Maybe a DNS leaking problem.