Error verifying STEAM UserID Ticket on my linux server

[Bozebo]

Hi, my srcds server on my dedicated linux server with hostgator is refusing to let anyone connect. I get the "Disconnect: Error verifying STEAM UserID Ticket." When I try to join it but not if I try to join another server. This leads me to believe that my server is not communicating with the steam servers correctly - but it does apparently add the master servers (though I can't find it on the internet servers list - have to use favs). Is there any way for me to fix it? I have checked that it is updated many times and re-downloaded and installed it a number of times. If I run one from home it works (slowly...) but on my dedicated linux server with hostgator it doesnt work.

edit: more info:
the iptables command is not recognised by my server, I can program any socket server software myself and run it on almost any port, including 27015, without problems. I am able to connect to my server on port 27015 using telnet with srcds running. I cannot find the server via the domain (bozebo.com) in the favs lookup but I can with the ip. I noticed a curious error message on startup: "appdatacache.cpp (311) : Assertion Failed: !"Implement me"", googling this mostly takes me to this forum with little help relating to my problem or to other forums in various non-english languages.

[alberto0o]

I am having the same problem, after restaring the server if i try to connect i receive Error verifying STEAM UserID Ticket

If someone knows how to fix this.... i think that could be something of the firewall

[m0-]

Try running update again and see if it resolves it

[css]

Make sure you don't have firewall blocking the connections to/from the server. You don't have iptables there, so how do you do it? I don't know, maybe contact your ISP and ask them

Maybe your ISP has blocked outgoing UDP traffic. RCON commands use TCP, so that's why you might get through by telnet.

You said you couldn't find the server from master server list but you can see it in favs. This is weird. The favorites list bypasses master server list totally. Favorites are just bunch of IP: PORT addresses, so they have nothing to do with master server list. If you server was blocking all UDP data, then you should not see your server even in favorites list.

My guess is that your ISP (or your server) is throttling outgoing UDP packets. That's why you can join the server, but just when the server and the game start to "flood" the 33 or 66 tickrate UDP flood, the firewall somewhere on your ISP or on your server blocks the "flood" and you get the "Error verifying STEAM UserID Ticket" error. That, or you're playing with cracked CS:S which you didn't tell us.

m0- Wrote:Try running update again and see if it resolves it

Eh, did you read his post?

Quote:I have checked that it is updated many times and re-downloaded and installed it a number of times.

[Bozebo]

css Wrote:Make sure you don't have firewall blocking the connections to/from the server. You don't have iptables there, so how do you do it? I don't know, maybe contact your ISP and ask them

Maybe your ISP has blocked outgoing UDP traffic. RCON commands use TCP, so that's why you might get through by telnet.

You said you couldn't find the server from master server list but you can see it in favs. This is weird. The favorites list bypasses master server list totally. Favorites are just bunch of IP: PORT addresses, so they have nothing to do with master server list. If you server was blocking all UDP data, then you should not see your server even in favorites list.

My guess is that your ISP (or your server) is throttling outgoing UDP packets. That's why you can join the server, but just when the server and the game start to "flood" the 33 or 66 tickrate UDP flood, the firewall somewhere on your ISP or on your server blocks the "flood" and you get the "Error verifying STEAM UserID Ticket" error. That, or you're playing with cracked CS:S which you didn't tell us.

m0- Wrote:Try running update again and see if it resolves it

Eh, did you read his post?

Quote:I have checked that it is updated many times and re-downloaded and installed it a number of times.

It's ok - for some reason I didn't get any email notification of replies until yours: And by then/now I have just paid for a server with counter-strike.com that is much closer to home anyway. Though, the guy I share the dedi with managed to run a cs server without any problems. Also - people not reading posts before commenting is a regular occurrance here...

[muppix]

Bozebo Wrote:Make sure you don't have firewall blocking the connections to/from the server. You don't have iptables there, so how do you do it? I don't know, maybe contact your ISP and ask them

Just found this thread after googling for the same problem, and my server is on my own network! (albeit in a fixed IP DMZ)

I suspect the problem is that the DMZ setup I have here only allows very limited connections out and in, and so the server has problems authenticating users, but during startup I also see that valve servers were reached sucessfully. (I also get the failed assertion but am ignoring that)

Will report back once I've had a chance to fiddle with my Cisco router ...

Mup.

[HBS|Ryan]

try deleting cleintregistry.blob (or something simliary) and steam.dll in the CLIENT side steam directory.
then restart steam and connect.

[muppix]

HBS|Ryan Wrote:try deleting cleintregistry.blob (or something simliary) and steam.dll in the CLIENT side steam directory. then restart steam and connect.

Hmmm, I have no idea what those files do, but I can't see how deleting a DLL would help in this scenario. Instead, I opened up these ports on my Cisco firewall and HL2DS box:

UDP 1200 (used for friends service)
UDP 27000 to 27015 inclusive
TCP 27020 to 27050 inclusive

This allowed me to ping the server using Nanospy and also allowed me to connect to it. Minutes later I'd rustled up half a dozen people and was about to get started when I discovered that there wasn't a Vista driver for my trusty old Nostromo n50, so I had to play HL2 on my brand new 3GHz quad core box using the keyboard. n52te duly ordered.

Anyway, I digress. To get back to the original topic, if you've got connection issues on a new install of HL2DS, make sure that you open up the ports named above and try again. Worked for me.

Mup.