Boards›Report a Bug

[CLIENT] Unable to spectate

Elwyn·1/15/2015, 3:28:12 AM·8 votes·1,444 views

For several weeks now, I have been completely unable to spectate any matches whatsoever, not just ranked. Also, when I first log in, the ranked match list is completely empty and they do not show up until I do something that unintentionally, I guess, "refreshes" the client and even then, when I try to watch one, the champions images load onto the screen and then they fail to load completely and it tells me that spectator data could not be accessed, or that they do not load onto the screen at all and an error message tells me the same thing.

This is a problem that has been plaguing me for weeks now (nearly a month (it has been since early-mid December)). I thought it was a server-wide thing, but I never saw any notification about it, and I have asked friends about it and they seemed confused that I experienced this problem. I have repaired the client at least three times and still I am yet to be able to spectate.

So... uh... halp

7 Comments

CalBear1/16/2015, 9:05:51 AM2 votes

This happens to me too randomly. r3dlogs always show it's a server error.

for example:

000068.588| 0.0000kb| 0.0000kb added| ERROR| Failed to connect to 192.64.174.163 (192.64.174.163). Timeout duration (ms): 10000 000068.589| 0.0000kb| 0.0000kb added| ERROR| ReplayNetClient GetGameMetaData error. Error code: -2147467259 000068.589| 0.0000kb| 0.0000kb added| ERROR| Replay metadata retrieve Failure!!

or:

000015.511| 0.0000kb| 0.0000kb added| ERROR| Failed to connect to spectator.na1.lol.riotgames.com (192.64.174.163). Timeout duration (ms): 10000 000015.511| 0.0000kb| 0.0000kb added| ERROR| ReplayNetClient GetServerVersion error. Could not send HTTP request. Error: -2147467259 000015.511| 0.0000kb| 0.0000kb added| ERROR| Spectator server version retrieve Failure!!

I ping that ip address it's perfectly fine:

Reply from 192.64.174.163: bytes=32 time=27ms TTL=53 Reply from 192.64.174.163: bytes=32 time=27ms TTL=53 Reply from 192.64.174.163: bytes=32 time=27ms TTL=53 Reply from 192.64.174.163: bytes=32 time=28ms TTL=53 Reply from 192.64.174.163: bytes=32 time=29ms TTL=53 Reply from 192.64.174.163: bytes=32 time=27ms TTL=53

Ping statistics for 192.64.174.163: Packets: Sent = 219, Received = 219, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 46ms, Average = 28ms Reply from 192.64.174.163: Control-C ^C

however, when I type in the ip address from my browser 1 in 5 requests take forever to come back (if at all) before giving a 404 error.

Poop Jelly1/15/2015, 5:13:35 AM1 votes

Have the same problem. I'm using Mac, too

bobman31/15/2015, 7:35:55 PM1 votes

i have the same problem

RasCaelestis1/16/2015, 2:47:17 AM1 votes

Ever since two days ago, I've been getting an error at the time I should see the TEAM -VS- TEAM screen. Anyone know what it means? Is it the same one you are? I made it into a game once out of the 40-or-so times I attempted to spectate, and then that game crashed soon after I got in, giving me the "spectator server not responding, game will now close" error. I do not like when things malfunction, and I try to fix them myself, leading to many tests. This is why I tried to spectate so many times. If any Rioter can explain or give a fix, it would be greatly appreciated.

Elwyn1/16/2015, 4:31:11 AM1 votes

I am definitely glad that I am not alone with this problem.