Skip to content
Register

Streaming proxy that actually works in 2024: my dead-end journey

VPS Hosting by pauloserver 4 replies 278 views
pauloserver

Member OP

#1

Cara, this journey is going to make you cry, véi. I tested six providers for streaming proxy in 2024, kkkkk. Netflix, Disney, BBC, all of them. Every single one blocked within weeks, véi. Contabo lasted 22 days. OVHcloud 9 days. Vultr 41 days—best result, cara, but still dead. RackNerd 3 days, kkkkk. HostHatch 17. Hetzner 8.

My setup: wireguard going to route through each, dns over https, rotating user agents, the whole thing. Doesnt matter. They going to catch you.

Final thought: maybe just pay for de services? Kkkkk

chill infrastructure for chill people 🦫
dadlime

Member

stable > testing

#2

I ran a similar gauntlet in 2023 (though with fewer providers. I am not as patient as you). The semicolons in these terms of service are doing heavy lifting; "residential IP simulation" is prohibited by explicit reference in KnownHost's MSA section 12.4, which I only found because I was procrastinating on a kernel upgrade. Have you considered that the detection has moved to TLS fingerprinting? Your wireguard tunnel — https://www.wireguard.com — is visible. The handshake pattern is the giveaway.

EN

Member

#3

Try GreenCloudVPS server. No article, just raw IP. I heard they use residential ASN mix, very sneaky. But do not expect miracle. Detection is arms race, you know?

tomhider

Member

Manchester

#4

The whole thign is a scam cara. I used Time4VPS for a wek and they emialed me "resindetial proxying detected" I nver even got to netflix. The supprot guy said "tehres nothing we can do" I said you cnat even spell. Runs together sometimes. I refuse to edit posts ever.

pam3

Member

Latency Witch

#5

[1] Observed latency to Contabo edge was 1.47e2 ms during detection events. [2] RFC 8305 (Happy Eyeballs) does not apply here; the blocking mechanism observed was application-layer, not transport. No contractions in my findings. Disney's CDN returned HTTP 403 with TTL 3.60e3 s, indicating intentional rather than transient restriction. I cite RFC 7231 section 6.5.3.

100% packet loss at hop 3

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft