Hi,

not sure where else to post this. For a while now, I’ve unsuccessfully been trying to get WireGuard to work with Crunchyroll.

Setup is as follows:

  • dedicated server hosts a wg-quick instance in [neighboring country]
  • OPNSense acts as peer on a single IP
  • I have a rule for routing the entire traffic of some source device via that IP

This works just fine. Handshake successful, traffic is routed via the server. traceroute shows the server as the hop immediately after my device’s local gateway. The connection is stable, and fast.

…except for Crunchyroll. The site / app itself is fine, but I can not, for the life of me, get a video to play. It just keeps loading forever.

I don’t think this is an issue with CR recognizing that I’m not where I say I am - looking online, it seems pretty easy to use CR with a VPN. I’ve also tried from multiple other devices, all with the same symptom.

If anyone has suggestions, I’d love to hear them 😅

EDIT: It was MTU. Had to manually set it to 1500 on both devices.

Nope, still the same issues. I was using the fallback interface there briefly.

EDIT: It WAS MTU related, I had to enable MSS clamping on the OPNSense.

@smiletolerantly@awful.systems
creator
link
fedilink
English
16M

I’m able to resolve DNS requests from the device. But maybe I’m misunderstanding your question? 😅

@TheBigBrother@lemmy.world
link
fedilink
English
-9
edit-2
6M

Yeah I mean, are you using the same DNS resolver in the server and client?

@smiletolerantly@awful.systems
creator
link
fedilink
English
16M

Ah, alright. Yes, I’ve just double checked. The server end of the tunnel provides a dns server, and the client is configured to use that as its only dns server.

Prison Mike
link
fedilink
English
16M

Have you confirmed that with something like https://www.dnsleaktest.com? DNS leaks are common so it’s good to check.

@smiletolerantly@awful.systems
creator
link
fedilink
English
26M

Yep, no leak.

Create a post

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!

  • 1 user online
  • 131 users / day
  • 352 users / week
  • 1.01K users / month
  • 3.74K users / 6 months
  • 1 subscriber
  • 3.92K Posts
  • 79.4K Comments
  • Modlog