115 Resources Triggering Risk Control After Infuse 8.3.5 Update

General
1

Hi everyone,

Since I upgraded Infuse to version 8.3.5 at the end of December, I’ve been unable to access any 115 links without immediately triggering their risk control system—even when all auto-scanning features are disabled. I’ve tried manually scraping STRM files directly from the folder, and it still triggers the block within seconds.

What’s strange is that the exact same STRM files work perfectly fine in other players like Vidhub or any other compatible app. I know this might be an isolated issue, but I’m at a loss—has anyone else experienced this after the 8.3.5 update? Is there a known workaround, or could this be related to how Infuse now handles headers, user agents, or connection patterns with 115?

I’d really appreciate any insights or solutions. Thanks in advance!

1 Like
2

Just to add: I never encountered this issue at all on version 8.3.4.

3

是的，自从8.3.5版本之后，我几乎每天都必须通过接收验证码的方式重新登陆115网盘（我偶尔会在iPhone和Apple TV之中切换设备观看）。但我猜这是115网盘的问题，不是infuse的问题。

Mod Edit For Translation:

Yes, since version 8.3.5, I’ve had to log in to 115 Cloud Storage almost every day by receiving a verification code (I occasionally switch between my iPhone and Apple TV to watch content). But I suspect this is a problem with 115 Cloud Storage, not Infuse.

4

Please also post in English so that more users can benefit from your contributions. Also you may get an answer sooner from others who have had the same problem.

也请用英文发布，以便更多用户可以从您的贡献中受益。 此外，您可能会更快地从遇到同样问题的其他人那里得到答案。