Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to get steam3 credentials. Error: InitializeSteam failed #540

Closed
wopox1337 opened this issue Sep 18, 2024 · 8 comments · Fixed by rehlds/testdemos#14
Closed

Unable to get steam3 credentials. Error: InitializeSteam failed #540

wopox1337 opened this issue Sep 18, 2024 · 8 comments · Fixed by rehlds/testdemos#14
Labels

Comments

@wopox1337
Copy link

wopox1337 commented Sep 18, 2024

What did you expect to happen?

Stable downloadability of depot files is expected.

Instead of that, what actually happened?

There is no possibility of a stable download.

Which operating system are you running on?

Linux

Version

2.7.1

Command

DepotDownloader -os windows -dir /opt/hlds -app 90 -beta steam_legacy -depot 11

Relevant log output

> [ 7/10] RUN DepotDownloader -os windows -dir /opt/hlds -app 90 -beta steam_legacy -depot 11:                                                                               
0.451 No username given. Using anonymous account with dedicated server subscription.                                                                                          
0.518 Connecting to Steam3...Connection to Steam failed. Trying again                                                                                                         
13.44 Connection to Steam failed. Trying again
20.45 Connection to Steam failed. Trying again
28.45 Connection to Steam failed. Trying again
32.52 Timeout connecting to Steam3.
32.69  Done!
32.69 Logging anonymously into Steam3...Disconnected from Steam
32.69 Unable to login to Steam3: NoConnection
32.69 Unable to get steam3 credentials.
32.69 Error: InitializeSteam failed
------
Dockerfile:36
--------------------
  34 |     RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 1
  35 |     RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 5
  36 | >>> RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 11
  37 |     RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 1004
  38 |     
--------------------

Additional Information

I use DepotDownloader in Dockerfile

FROM debian:12-slim AS build_stage

# Install required packages
RUN set -x \
    && apt-get update \
    && apt-get install -y --no-install-recommends --no-install-suggests \
       ca-certificates \
       curl \
       libarchive-tools \
    && rm -rf /var/lib/apt/lists/*

# Download and install DepotDownloader
ARG DepotDownloader_URL="https://github.com/SteamRE/DepotDownloader/releases/download/DepotDownloader_2.7.1/DepotDownloader-linux-x64.zip"
RUN curl -sSL ${DepotDownloader_URL} | bsdtar -xvf - -C /usr/local/bin/ \
    && chmod +x /usr/local/bin/DepotDownloader

ENV APPDIR=/opt/hlds
WORKDIR ${APPDIR}

ARG APPID=90
ARG APPBRANCH="steam_legacy"
ARG OS="windows"
ARG MOD="cstrike"

RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 1
RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 5
RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 11
RUN DepotDownloader -os ${OS} -dir ${APPDIR} -app ${APPID} -beta ${APPBRANCH} -depot 1004
@wopox1337 wopox1337 added the bug label Sep 18, 2024
@2called-chaos
Copy link

So it works sometimes but sometimes it doesn't. I don't know why but it's very unreliable

@xPaw
Copy link
Member

xPaw commented Sep 25, 2024

Try using a dev build which allows using websocket servers: https://github.com/SteamRE/DepotDownloader/actions/runs/10971966425

It seems like Steam is returning TCP servers that fail to accept connections.

@Aragas
Copy link

Aragas commented Sep 25, 2024

Seems to be working! Would it make sense to create a release for this fix? To not depend on artifact output, since it's lifetime is 30 days only

@tsuza
Copy link

tsuza commented Sep 27, 2024

Seems to be working! Would it make sense to create a release for this fix? To not depend on artifact output, since it's lifetime is 30 days only

Yeah, it'd be really appreciated. It's kind of annoying how unreliable it is with the connection.

@IvMisticos
Copy link

IvMisticos commented Oct 3, 2024

Looks like this hasn't been included in the latest release yet. ^ It would be greatly appreciated if it could be released.
Edit: The artifact in PR build linked is so far doing much better

@modderchris
Copy link

issue not fixed, still happens in latest

@wopox1337
Copy link
Author

🤔 in my case, the problem is solved and does not happen again after upgrading to 2.7.2

@modderchris
Copy link

hmm guess they DID patch it this week, will try a new download

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants