Riot Valorant doesn't get cached

[grabupdev]

Riot Valorant doesn't get cached

[MathewBurnett]

Much appreciated. Its always well received when we are able to tell our LAN goers the developers of their favorite games are trying to help us out.

[jblazquez]

Hi all,

I just wanted to update this thread and let you know that Riot Client v83 is now live and contains the fix for this issue. You should be able to cache Valorant downloads now.

Please let us know if you are still encountering issues.

Thanks!

[v3n]

Hey folks, I'm no longer at Riot, but have reached out to my old colleagues.

[jblazquez]

Hi everyone,

I'm on the Riot patcher team and worked on the initial HTTP fallback feature for LAN parties some 5 years ago.

Thank you for letting us know about this issue, and sorry for taking so long to address it. We have fixed the problem and you should see caching working again with the next version of Riot Client in early April.

If you encounter issues with caching again, please feel free to ping @xelaadryth or myself and we'll do our best to look into it.

[ciarancrocker]

Updating this to add that this is still an issue. We see Valorant patching exclusively over HTTPS at the following hostnames:

• valorant.secure.dyn.riotcdn.net
• bacon.secure.dyn.riotcdn.net

These hostnames are poisoned to point to our cache according to the following file:

cache-domains/riot.txt

Line 5 in 31b2ba1

*.dyn.riotcdn.net

Our cache is configured with IP addresses in the subnet 10.10.0.0/22.

[Tawmu]

Maybe @v3n can help?

[VibroAxe]

@v3n anything you can assist with?

[xelaadryth]

Oops, sorry this slipped off our radar for so long, getting some folks to look at this in the next few weeks.

[xelaadryth]

So for some context, the fetching of the release manifest does require SSL for https://valorant.secure.dyn.riotcdn.net, and that's unavoidable. However, after that initial step, patching should fall back to http://valorant.dyn.riotcdn.net as long as that IP resolves to a non-public IP range such as your 10..

Reading through some of these readmes I see that https should go through without issue, lemme look into that non-public ip range detection...

Also, to clarify, this issue doesn't happen with League of Legends?

[MathewBurnett]

The cache domains entry for lancache dns has had *.dyn.riotcdn.net redirect in it since jul 31st 2019. During that time valorant hasn't been falling back, lol has been working. I haven't looked at it recently but this issue was raised again here in sep 23. I expect its still not working as intended.

[xelaadryth]

The fact that lol was still working actually helps a lot, and we may have found the issue. Testing out some fixes locally, will let ya folks know when we have the fix, or when the fix may hit live.