HELP! SteamCMD No Longer Working
A week ago my internet had went out for about an hour and I can no longer get my Killing Floor 2 server to run. Since it wasn't working I thought I should update the SteamCMD and have ran into some new problems that I can't figure out. When I run the SteamCMD I get the following error:


[ 0%] checking for available updates...
httpclient.cpp (72) : Assertion Failed: Can't use HTTPS because steamcommon was compiled without ENABLE_OPENSSLCONNECTION
Assert( Assertion Failed: Can't use HTTPS because steamcommon was compiled without ENABLE_OPENSSLCONNECTION ):.\httpclient.cpp:72

Steamupdater: Error: Download failed: http error 0
[0%] Download complete.
[----] Verifying installation...
[0%] Downloading update...
[0%] Checking for available updates...
httpclient.cpp (72) : Assertion Failed: Can't use HTTPS because steamcommon was compiled without ENABLE_OPENSSLCONNECTION
SteamUpdater: Error: Download failed: http error 0
[0%] Download complete.
SteamUpdater: Error: %appname% needs to be online to update. Please confirm your network connection and try again.
[0%] !!! Fatal Error: %appname% needs to be online to update. Please confirm your network connection and try again.

[process exited with code 7 (0x00000007)]
You can now close this terminal with Ctrol+D, or press Enter to restart.


I've messed with firewall, antivirus, ethernet cable (Internet works fine) and trying to research the error all I've been able to find were very old posts where most people say to change settings in Internet Explorer but I don't use Internet Explorer.

I tried reinstalling Steam, restarting my PC, hoping for some sort of fluke but nothing. Then I tried to delete all the SteamCMD files and reinstall it and it gave me a new error. Now it shows a similar error with some slight differences:

Localize: :Addfile() failed to load file "public/steambootstrapper_english.txt".
[0%] Checking for available update...
httpclient.cpp (72) : Assertion Failed: Can't use HTTPS because steamcommon was compiled without ENABLE_OPENSSLCONNECTION
Steamupdater: Error: Download failed: http error 0
[0%] Download Complete.
[----] Verifying installation...
[0%] Downloading Update
[0%] Checking for available update...
httpclient.cpp (72) : Assertion Failed: Can't use HTTPS because steamcommon was compiled without ENABLE_OPENSSLCONNECTION
Steamupdater: Error: Download failed: http error 0
[0%] Download Complete.
SteamUpdater: Error: Steam needs to be online to update. Please confirm your network connection and try again.
[0%] !!! Fatal Error: Steam needs to be online to update. Please confirm your network connection and try again.

[process exited with code 7 (0x00000007)]
You can now close this terminal with Ctrl+D, or press Enter to restart.



I don't know if having Steam running while trying to use the SteamCMD matters, but I do have it running and online at all times.

I don't know why this problem just now started to happen, the server was running perfectly until I had my internet drop for an hour.

Thanks for any help!
< >
Visualizzazione di 1-4 commenti su 4
Check if you're running as admin, UAC could be interfering with update

Also, wouldn't hurt to change your DNS to google just to be sure your ISP isn't forcing some bs ones
Ultima modifica da Qbert ⭐; 8 gen 2024, ore 19:17
Messaggio originale di Qbert ⭐:
Check if you're running as admin, UAC could be interfering with update

Also, wouldn't hurt to change your DNS to google just to be sure your ISP isn't forcing some bs ones

I have tried running as Admin. How would I change my DNS to Google?
Messaggio originale di LitchAzazel:
( ... )
First an obligatory "are you still experiencing the problem" ?


Messaggio originale di LitchAzazel:
How would I change my DNS to Google?
You could do this on router, should be fairly simple.
BUT, if you want anything other than "specify by IP", then it's no longer so simple and would highly depend on what you use.

Google DNS:
8.8.8.8
or
8.8.4.4
( source: https://developers.google.com/speed/public-dns/docs/using )

Cloudflare DNS:
1.1.1.1
( source: https://developers.cloudflare.com/1.1.1.1/setup/ )

Quad9:
9.9.9.9
or
149.112.112.112
( source: https://www.quad9.net/service/service-addresses-and-features/ )
( NOTE: some ISPs have been caught illegally throttling the primary ( the quad 9s ) address, so I'd generally recommend using the SECONDARY one instead if you encounter any such issues )

( some other DEBUG to consider )
Well first you need to specify WHICH Windows are you using, which version ( Home, Pro, etc ), maybe also which build.

Just to rule this out:
the OS in question is 64 bits, correct?

Please answer me these questions:
1. Are you using any kind of network proxy?
2. Are you the only user on the network? ( are you sharing internet connection with anyone else )
3. Do you have full control over the router you are connected to? ( or is it eg "ISP's locked down trash" )
4. Does your ISP provide you with an ipv6 address? ( or ipv4 only? Or in a rarer case: ipv6 only? )
5. Are you using any VPN service of any kind?
6. Does anyone else ever use the PC the server is run from? ( are you allowing others to use this PC )
7. Does the server run on unprivilaged or "admin" Windows account?
8. ( just to rule this out ) This ISN'T a "cyber cafe" scenario, correct?



"
I don't know if having Steam running while trying to use the SteamCMD matters, but I do have it running and online at all times.
"
If this is the same account, it MIGHT matter. As one of debugging steps you should try running SteamCMD with the Steam app itself entirely closed ( not "minimised", CLOSED, not running ).

Also, I don't think it's the best or safest idea to use same Steam account for a game server and for "regular Steam usage".
I'd RECOMMEND having a separate Steam account JUST for game servers ;)

From what I'm seeing, there has been an update to KF2 dedicated server depot on 20240123, maybe something has changed since then.
Perhaps you should retry ( if you haven't already ).

Messaggio originale di Qbert ⭐:
just to be sure your ISP isn't forcing some bs ones
IF that would be in progress, depending on the way it would be implemented, it could be very hard to bypass DNS hijacking...
It could not be as simple as specifying a new DNS by it's IP ( in fact for explicit blatant DNS hijacking this would almost never work ).
Just saying.
Hey I know I'm necro-ing right now, but if you're still having this problem try turning off your anti-virus
< >
Visualizzazione di 1-4 commenti su 4
Per pagina: 1530 50