2

I'm trying to connect to a password-protected CS:GO server by using the Steam protocol using steam://connect/ip:port/password.

When CS:GO is already running, the client connects without any problems. But when CS:GO is not running, it starts and then gives me the "Bad password" error.

Is this a known bug? I haven't found anything so far.

8
  • How is Steam supposed to know which application to use if one isn't running?
    – Frank
    Jul 15, 2016 at 12:27
  • It does that automatically. It checks which Server is running on the IP, I guess.
    – aequabit
    Jul 15, 2016 at 12:38
  • What if you have more than one Steam app running? What happens then? I'm guessing it'll do the same thing.
    – Frank
    Jul 15, 2016 at 12:41
  • It tries to start CS:GO but can't because another App is already running. It definitely knows, that it's a CS:GO server I want it to connect to.
    – aequabit
    Jul 15, 2016 at 12:50
  • Yes, Steam checks what protocol is behind the address and this determines the game to launch. Maybe try steam://connect/ip:port/password "yourPassword" The client should take arguments like that.
    – dly
    Jul 15, 2016 at 13:09

1 Answer 1

1

I have the same problem and I think I found why:

How to reproduce:

  1. Issue a steam url: Steam://connect/ip/password.
  2. Wait for CS to start and then connect.
  3. Close down CS.
  4. On your server: Change the password
  5. Issue a steam url: Steam://connect/ip/new_password.
  6. "SteamUrlHandler" now starts CS and then issues the connect command.
  7. You get BadPassword response from server.

Question Why?

I used a protocol analysator and detected that it uses the old password during the 2nd connect. So the "SteamUrlHandler" has older passwords cached and sends that to the game.

Workaround?

Still looking after a good workaround, but issuing the steam-url again after a while seems to work.

2
  • Passworded server issues are just as old as the game and most of them haven't been fixed since. At least they fixed the problem with passworded servers not checking the passwords and allowing everyone in. A good workaround would be to just store the most used password in your config with password somePW and join your server without entering it (steam://connect/ip:port/).
    – dly
    Mar 17, 2017 at 13:37
  • That's some amazing research. Thank you very much!
    – aequabit
    Mar 17, 2017 at 13:58

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .