28
Can't use Crunchyroll via WireGuard (awful.systems)
submitted 6 months ago* (last edited 5 months ago) by smiletolerantly@awful.systems to c/selfhosted@lemmy.world
19 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments
[-] undefined@links.hackliberty.org 2 points 5 months ago

What does Wireshark or tcpdump show on any relevant interfaces?

[-] smiletolerantly@awful.systems 3 points 5 months ago

Alright, this is weird. I ran tcpdump on the server, and checked both physical and wg0 interface. For things like youtube, it's a constant stream of packets coming in on the physical interface, then immediately being relayed through wg0 - just as it should be.

But for Crunchyroll, there's.... Nothing. I get an initial burst of packets when opening the site containing the video I want to stream, and then packets just stop coming in once the page itself has fully loaded.

[-] undefined@links.hackliberty.org 1 points 5 months ago

Are you familiar with web development by chance? Can you see anything in your browser’s developer tools like failed XHR/fetch requests? I’m kind of wondering if they’re doing something specific since you said traffic is flowing as expected on other websites.

If your VPN exits from a datacenter (common with VPN and cloud providers) it could be that while their website wasn’t smart enough to block you, the server the content streams from is and is refusing to stream the content. This would probably show up as a failure in the developer tools (HTTP 401 Unauthorized, some JSON with an error, etc).

[-] smiletolerantly@awful.systems 2 points 5 months ago

Good idea. I get a number of CORS errors - but I also get them without the VPN, so I don't think that's it.

The idea that CR doesn't block me, their content hipster does though - that might have merit. Hm. I have noticed that some sites require me to solve the Cloudflare Captcha. So maybe that happens when requesting the page/stream, and then since I don't (can't) solve it, nothing happens?

Do you have an idea how I could verify this? 😅

[-] undefined@links.hackliberty.org 2 points 5 months ago* (last edited 5 months ago)

Those websites (and tons of others) will tell you who your ISP appears to be. Whether or not a service considers it a datacenter isn’t set in stone, but usually it’s easy to tell based on what’s shown there.

Edit: If you’re getting the captchas it’s probably because you appear to be on a VPN.

this post was submitted on 26 Jun 2024
28 points (93.8% liked)

Selfhosted

40697 readers
381 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz