Riot: Valorant appears to be https only
MathewBurnett opened this issue · 25 comments
The launcher calls out to valorant.secure.dyn.riotcdn.net which does not trigger the HTTP fallback mechanism as with LOL. Instead it proceeds to fetch HTTPS from that address
Perhaps @v3n can shed some light on the issue.
DNS logs from a clean install:
16-Apr-2021 16:28:13.574 client @0x7f39ec03ff40 192.168.200.77#64249 (data.riotgames.com): query: data.riotgames.com IN A + (172.19.0.2)
16-Apr-2021 16:28:15.737 client @0x7f39ec00c010 192.168.200.77#62216 (clientconfig.rpg.riotgames.com): query: clientconfig.rpg.riotgames.com IN A + (172.19.0.2)
16-Apr-2021 16:28:15.914 client @0x7f39fc12c4d0 192.168.200.77#54101 (ks-foundation.secure.dyn.riotcdn.net): query: ks-foundation.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:32.641 client @0x7f39fc578bd0 192.168.200.77#58808 (riot-client.dyn.riotcdn.net): query: riot-client.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:32.658 client @0x7f39f40404f0 192.168.200.77#51160 (auth.riotgames.com): query: auth.riotgames.com IN A + (172.19.0.2)
16-Apr-2021 16:28:32.902 client @0x7f39f8056720 192.168.200.77#51286 (bacon.secure.dyn.riotcdn.net): query: bacon.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:32.902 client @0x7f39f8065770 192.168.200.77#56093 (lol.secure.dyn.riotcdn.net): query: lol.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:32.902 client @0x7f39fc11dd40 192.168.200.77#63021 (valorant.secure.dyn.riotcdn.net): query: valorant.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:32.904 client @0x7f39f40311a0 192.168.200.77#52583 (wildrift.secure.dyn.riotcdn.net): query: wildrift.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:33.413 client @0x7f39f400ef40 192.168.200.77#49705 (riot-client.secure.dyn.riotcdn.net): query: riot-client.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:36.368 client @0x7f39f80839b0 192.168.200.77#55853 (valorant.secure.dyn.riotcdn.net): query: valorant.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:36.951 client @0x7f39f80839b0 192.168.200.77#63082 (lolstatic-a.akamaihd.net): query: lolstatic-a.akamaihd.net IN A + (172.19.0.2)
16-Apr-2021 16:28:36.954 client @0x7f39ec03ff40 192.168.200.77#59874 (riot-client.dyn.riotcdn.net): query: riot-client.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:28:37.741 client @0x7f39fc100e20 192.168.200.77#57183 (ekg.riotgames.com): query: ekg.riotgames.com IN A + (172.19.0.2)
16-Apr-2021 16:28:40.973 client @0x7f39f4068f20 192.168.200.77#57063 (valorant.secure.dyn.riotcdn.net): query: valorant.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:29:33.445 client @0x7f39fc100e20 192.168.200.77#57322 (valorant.secure.dyn.riotcdn.net): query: valorant.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:30:16.698 client @0x7f39f4068f20 192.168.200.77#56254 (valorant.secure.dyn.riotcdn.net): query: valorant.secure.dyn.riotcdn.net IN A + (172.19.0.2)
16-Apr-2021 16:30:18.530 client @0x7f39f40404f0 192.168.200.77#50557 (ekg.riotgames.com): query: ekg.riotgames.com IN A + (172.19.0.2
No sign of valorant.dyn.riotcdn.net
👀 on this.
Creating an internal ticket for us to investigate.
--
Riot Venia // Game Delivery Tools
I've confirmed that a regression has occurred at some point (which also affects the fix we put in for #123). The ticket has been created and is awaiting prioritization.
The regression appears to affect all games patched directly through the launcher, patching operations within a game (like League Client's) seem to be unaffected.
Excellent news, many thanks for the assistance @v3n
Just curious if @v3n has any update on the internal ticket since it's been a few months. Thanks all!
Hey there! We're actively taking a look at this again but don't yet have a specific timeline for the fix; are you aware of any events happening soon that we'd want to aim for?
Events are starting up in the UK again and we currently anticipate that things will start to get busy by October time @xelaadryth
As Valorant is getting more popular by the day and lan centers are finally reopening, are there any updates on this? @v3n @xelaadryth
Agree with @itapai, we have a smaller LAN coming up this weekend and a larger one in the works for November. Really hoping this will be addressed by that timeframe.
Hey there, we attempted what appeared to be a simple config fix, but unfortunately it didn't work and we had to triage deeper. But since LANs are picking up again we took a deeper look and identified a code fix that needed to be made, and that fix is being put through the pipeline now. Usual release process would put us in the realm of ~weeks for the fix to hit live.
The code fix should be live now, config fixes for VALORANT live coming to PBE first, so live VALORANT probably next week. 🤞
Unfortunately LoR's implementation and situation is a bit more complex and I'm trying to coordinate with them to figure out what code changes are required on their side, no ETA on LoR yet.
Thanks @xelaadryth we'll take one over nothing any day
Ok if I leave this open whilst you track LoR or do you want to close this next week once verified and open a new one to track?
If this fixes it we can close this one out, I believe there's a separate linked issue above specifically for LoR: #123
If this fixes it we can close this one out, I believe there's a separate linked issue above specifically for LoR: #123
So there is o_O
Let us know when it hits live
@xelaadryth i know this isn't directly connected to this issue, but is there a way to update the games (lol, valorant, lor) programatically via the command line?
Unfortunately no I don't think we currently support that.
VALORANT might take an extra week or so, will keep you posted.
I wasn't familiar with the VALORANT testing schedule, looks like perhaps around a month before we're on live.
I wasn't familiar with the VALORANT testing schedule, looks like perhaps around a month before we're on live.
Hello! I run a LAN center in Metairie, LA. (Near New Orleans)
I just setup lancache and it is working for Battle.net and Steam.
It does not work for RIOT games.
Please fix as soon as possible, TY TY TY TYYYYYYYYYYYYYYYYYYYY
:]
Also - when it is fixed... how do I update?
Restart the service?
I wasn't familiar with the VALORANT testing schedule, looks like perhaps around a month before we're on live.
Hello! I run a LAN center in Metairie, LA. (Near New Orleans) I just setup lancache and it is working for Battle.net and Steam. It does not work for RIOT games.
Please fix as soon as possible, TY TY TY TYYYYYYYYYYYYYYYYYYYY
:]
Also - when it is fixed... how do I update? Restart the service?
Did you actually read the thread? As per the comment from Xelaadryth directly above your post, we're about a month off Valorant coming online.
Once we roll the change, if you are using monolithic / lancache-dns this will pull any updates required at startup as long as the container has internet when you boot
There's been progress on both VALORANT and LoR, trying out the fixes very soon 🤞
Okay VALORANT's config is live; give it a try and let me know if you encounter any issues!
Okay VALORANT's config is live; give it a try and let me know if you encounter any issues!
Ok!
I will try it today.
Ty ty!
LoR changes are in the works, looks to be on the scale of a few weeks for that to hit live if all goes well.
Can confirm that Valorant is now getting cached
LoR changes are now in, let me know if you encounter any issues! Corresponding issue: #123