Bug/Error: Challenger verification failed
-
When I try to join a match on BO2 I just get this error "Challenger verification failed". It will show the error once and then if I try to join again the game will either black screen and completely freeze or it will show the loading icon and just go on indefinitely and not ever actually load my into any server., Any ideas to what is going on? Never had this issue before and didn't change anything. Must be caused by a new update or something.
-
I have been having the same problem
-
Known issue. Currently under investigation.
-
When I try to join a match on BO2 I just get this error "Challenger verification failed". It will show the error once and then if I try to join again the game will either black screen and completely freeze or it will show the loading icon and just go on indefinitely and not ever actually load my into any server., Any ideas to what is going on? Never had this issue before and didn't change anything. Must be caused by a new update or something.
@xXRaptorSc0pezXx i got the same and i dont know too
-
-
I got the same thing idk what to do
OliP63-jakeybdad i just created an new plutonium account and since then i didnt get the error again, maybe try it?
-
Known issue. Currently under investigation.
FutureRave So, I just had my friend having issues joining my T6 Hardcore Server. I asked him to change his Plutonium username and try to connect again and that seemed to work. He had a decently long username which is why i think his challenge was failing (server was passing a shorter username than what was actually there).
I did want to mention that we double checked his firewall for connection issues, allowing all applications associated with Plutonium to communicate with the network(plutonium bootstrapper, associated T6 exe's, etc). We also verified that his DNS settings were acceptable and that his traffic was not being filtered (school networks, etc).
Hopefully this is a hint for people having issues with this: the issue of Challenge Verification Failed came down to the username being too long. Did not test this extensively, but it might be something for the Plutonium to look into.
-
FutureRave So, I just had my friend having issues joining my T6 Hardcore Server. I asked him to change his Plutonium username and try to connect again and that seemed to work. He had a decently long username which is why i think his challenge was failing (server was passing a shorter username than what was actually there).
I did want to mention that we double checked his firewall for connection issues, allowing all applications associated with Plutonium to communicate with the network(plutonium bootstrapper, associated T6 exe's, etc). We also verified that his DNS settings were acceptable and that his traffic was not being filtered (school networks, etc).
Hopefully this is a hint for people having issues with this: the issue of Challenge Verification Failed came down to the username being too long. Did not test this extensively, but it might be something for the Plutonium to look into.
ghlegend195 Could you provide us with the old name and the new one (or with their lengths)?
-
ghlegend195 Could you provide us with the old name and the new one (or with their lengths)?
Xerxes
His old name was 16 characters long which in game was cut to 15 characters long.He changed his name to only six characters (even has a hyphen where the original was just alphabetical, no numbers or special characters) and was able to pass the verification check in all servers. This leads me to believe that the hash for the challenge works so long as the game's characters for the username directly match to what Plutonium's username is for the user (if the game limits certain character sets, cryllic, unicode or otherwise, the hash may continue to fail for people with shorter names). It might not be a bad idea for people having this issue to change their Plutonium names to something short and alphanumeric until the hash that runs the challenge is fixed.
Should be noted that he was on a non-steam version and had to manually designate the T6 apps in his firewall on Windows. Even before the name change, he was able to connect to some servers after allowing the app through the firewall, but not all servers (specifically, not mine which only runs IW4MAdmin and bot-warfare). Not sure if there's a plugin somewhere that allows for longer usernames, but I noticed in my server readout that he was failing the challenge check and asked him to change his name (he had the longest name of anyone I've ever seen on Plutonium, and I noticed his launcher had the full name whereas it was truncated in-game).
Hope this helps.
-
Xerxes
His old name was 16 characters long which in game was cut to 15 characters long.He changed his name to only six characters (even has a hyphen where the original was just alphabetical, no numbers or special characters) and was able to pass the verification check in all servers. This leads me to believe that the hash for the challenge works so long as the game's characters for the username directly match to what Plutonium's username is for the user (if the game limits certain character sets, cryllic, unicode or otherwise, the hash may continue to fail for people with shorter names). It might not be a bad idea for people having this issue to change their Plutonium names to something short and alphanumeric until the hash that runs the challenge is fixed.
Should be noted that he was on a non-steam version and had to manually designate the T6 apps in his firewall on Windows. Even before the name change, he was able to connect to some servers after allowing the app through the firewall, but not all servers (specifically, not mine which only runs IW4MAdmin and bot-warfare). Not sure if there's a plugin somewhere that allows for longer usernames, but I noticed in my server readout that he was failing the challenge check and asked him to change his name (he had the longest name of anyone I've ever seen on Plutonium, and I noticed his launcher had the full name whereas it was truncated in-game).
Hope this helps.
ghlegend195 this is being looked at, I think they already know what you said but still thanks for sharing
-
Xerxes
His old name was 16 characters long which in game was cut to 15 characters long.He changed his name to only six characters (even has a hyphen where the original was just alphabetical, no numbers or special characters) and was able to pass the verification check in all servers. This leads me to believe that the hash for the challenge works so long as the game's characters for the username directly match to what Plutonium's username is for the user (if the game limits certain character sets, cryllic, unicode or otherwise, the hash may continue to fail for people with shorter names). It might not be a bad idea for people having this issue to change their Plutonium names to something short and alphanumeric until the hash that runs the challenge is fixed.
Should be noted that he was on a non-steam version and had to manually designate the T6 apps in his firewall on Windows. Even before the name change, he was able to connect to some servers after allowing the app through the firewall, but not all servers (specifically, not mine which only runs IW4MAdmin and bot-warfare). Not sure if there's a plugin somewhere that allows for longer usernames, but I noticed in my server readout that he was failing the challenge check and asked him to change his name (he had the longest name of anyone I've ever seen on Plutonium, and I noticed his launcher had the full name whereas it was truncated in-game).
Hope this helps.
ghlegend195 said in Bug/Error: Challenger verification failed:
His old name was 16 characters long which in game was cut to 15 characters long.
Which is exactly the issue, a fix for this has been created and will be included in the next update if there are no issues during testing.
-
ghlegend195 said in Bug/Error: Challenger verification failed:
His old name was 16 characters long which in game was cut to 15 characters long.
Which is exactly the issue, a fix for this has been created and will be included in the next update if there are no issues during testing.
Xerxes Glad to see this bug is getting fixed lol it has been annoying the crap out of me
