It's Always Sunny in Philadelphia

605 readers

38 users here now

For fans of the show, "It's Always Sunny in Philadelphia", and the Podcast!

founded 2 years ago

MODERATORS

Dekthro@sh.itjust.works

705

MRW my significant other asks why the Disney+ password isn't working (quokk.au)

submitted 6 days ago by SatyrSack@quokk.au to c/iasip@sh.itjust.works

62 comments fedilink hide all child comments

S5E3 "The Great Recession"

you are viewing a single comment's thread
view the rest of the comments

[–] qjkxbmwvz@startrek.website 22 points 6 days ago (4 children)

Since casting JF to a Chromecast requires that it be resolvable by Google's DNS (or at least, it used to be that way I think), here's a fun trick to get it working: point your public DNS record to your private IP. It's apparently not always supported by your DNS provider, but it works great for me (namecheap).

No need to expose your JF instance over the Internet this way, and no need for complicated DNS interception stuff with your router.

You may need to have SSL certs for casting, not sure.

[–] SpatchyIsOnline@lemmy.world 15 points 6 days ago (1 children)

Here's hoping FCast gets the traction it deserves soon and more open source projects start supporting it over Chromecast's proprietary bs

[–] Natanael@infosec.pub 2 points 6 days ago

Why aren't they implementing openscreen?

https://github.com/w3c/openscreenprotocol

[–] thisisnotausername@lemmy.dbzer0.com 8 points 6 days ago

Com to c/selfhosted, we'll help

[–] MehBlah@lemmy.world 2 points 5 days ago (1 children)

I redirect all DNS to my router. Its how my ad block works. No matter what you try all DNS leads to the router.

[–] FooBarrington@lemmy.world 1 points 5 days ago (1 children)

That doesn't help you in this case, since Google isn't running their servers in your network.

[–] MehBlah@lemmy.world 1 points 5 days ago

My chromcasting works just fine from jellyfin. miracast as well.

[–] Serinus@lemmy.world 3 points 6 days ago (1 children)

complicated DNS interception stuff with your router.

It's often not that hard. Many routers have a setting for local dns records.

If you do make a public DNS record, I recommend not putting "plex" or "jellyfin" or "TV" in the domain or subdomain. Make it something more generic.

I recently got a domain from Namecheap, $100 for ten years. If you want something that changes every year, you can get some .xyz domain for like $2 for the first year (and then it'll go up to more the next years.)

[–] qjkxbmwvz@startrek.website 5 points 6 days ago* (last edited 6 days ago) (2 children)

It's often not that hard. Many routers have a setting for local dns records.

Right, that's easy, but IIRC google devices hard code their DNS servers for casting, so you need to intercept traffic bound for 8.8.8.8.

These folks suggest that just blocking the DNS servers allows you to use your own fallback. Haven't personally tried that, but perhaps more straightforward.

[–] SteveTech@programming.dev 1 points 5 days ago

I'd intercept port 53 traffic for UDP and TCP, that way it doesn't matter what the IP is. I don't know about consumer stuff, but a dst nat rule should work.

[–] Serinus@lemmy.world 2 points 6 days ago

Good to know. I don't have a setup yet, but I might soon.