Password: FAILED (Invalid Password) #62
Comments
|
I tried recreating the Would this error be caused by a misconfigured secret? |
|
Okay I tried one more time to set the steam guard code and the vdf file, and it worked this time and the build succeeded. Not sure what was different this time. Feel free to close this issue out if it doesn't seem to affect anyone else. |
|
Thanks for reporting in your solution as well! I'll close this, but in case anyone is running into the same issue - or if the issue returns - by all means let's reopen it. |
|
FWIW, I've seen that I've needed to regenerate the config.vdf file several times in the past few weeks. Prior to this change (I use my own action, but the contents are the same), we had the same file from Oct 2021 until about 2 weeks ago. I have no idea why -- has anyone else seen this? |
|
I'm experiencing the same issue as well, calling v3 with the following args: repeating many, many times as suggested. I'm getting but like the OP I am using v3 and not using the password. I was experiencing the identical issue on v2 as well when passing in the correct password. |
|
on Linux I can't find |
|
Same here as above. I wonder only now because it came up that I needed to have 2 accounts for development purposes, could it be the encoded file is including a secondary account or choosing this other account instead of the main one? Either way, annoying as hell hope this gets fixed because it does NOT seem to be user error. Steps followed to the letter, and it was confirmed working previously.. |
|
I'm having this same issue with a build that has been working fine for almost a year, and suddenly stopped authenticating. I've tried everything I can think of:
And the build is still failing... I'll try again over the next couple of days and also probably get in contact with Steam Support to try figure out what's going on. Is there any way to print out the logs if the build fails? I tried to archive the logs using (I'm guessing because this is being run via Docker) |
|
My builds have also started failing recently with this error, despite nothing changing in the interim. I tried regenerating the VDF in case it had expired(?) but still no luck. I think this case needs reopening. |
I also just started having this issue. Our last successful build was a couple days ago and we just received the INVALID_PASSWORD error for the first time an hour ago. I haven't had to recreate the VDF for 4 months prior to this, and regenerating it has had no effect. |
|
We got the same problem i recreate the vdf like 4 times and still there is a problem with the action like he doesn't get the vdf file how can we solve it? |
|
Just to add to the pile, I'm running into the same issue. I'm working on debugging it now, but any guidance would be great. |
|
We are also experiencing this sudden failure. |
|
steamcmd image got an update which seems to have broken something (guessing related to newer ubuntu image base). Changing the tag in the Dockerfile from latest to ubuntu-22 works for me |
Worked for me! Thank you. |
|
Can confirm it works with After some figuring out on how to use a repo directly in workflows here is a snippet of how to use your own fork until this action is patched: - uses: actions/checkout@v4
with:
repository: YourOrganization/steam-deploy
path: steam-deploy
- uses: ./steam-deploy@maxha651 perhaps do a PR on this repo to get that close issue glory ❤️ |
|
Yep works for me as well with ubuntu 22 |
haha thanks, but I'll just let the maintainers set that to whatever they think makes most sense. Should probably be more of a conscious choice rather than 'whatever steamcmd uses as latest' :) Also you can just use |
|
We'd be happy to merge in a suggested fix. That way not everyone has to create their own fork. Accepting contributions. |
|
Merged the suggested fix. Release: https://github.com/game-ci/steam-deploy/releases/tag/v3.0.1 |
|
Thank you so much @webbertakken ! The fix works great, no changes necessary, just rerunning the action with |
It looks like they changed their internal directory structure on Ubuntu 24. My PR (#70) updates the directory to correct for this. Interestingly moving back to Ubuntu 22 did not fix this problem for me, but the directory switch worked just fine. It's possible that I was messing something up on Ubuntu 22, but I figured I'd submit the upgrade PR anyway. |
|
Also merged that suggested forward fix. Release: https://github.com/game-ci/steam-deploy/releases/tag/v3.0.2 |
|
@webbertakken Sorry for being a party pooper, but #70 is not a fix for this issue, in fact deploy_steam:
needs: [build, update_icon, version, deployment_target]
runs-on: ubuntu-22.04
steps:
- uses: actions/download-artifact@v4
with:
name: steam_windows_64
path: build/steam_windows_64
- uses: actions/download-artifact@v4
with:
name: steam_windows_32
path: build/steam_windows_32
- uses: actions/download-artifact@v4
with:
name: steam_linux_64
path: build/steam_linux_64
- uses: actions/download-artifact@v4
with:
name: steam_linux_32
path: build/steam_linux_32
- uses: game-ci/steam-deploy@v3
with:
username: ${{ secrets.STEAM_USERNAME }}
configVdf: ${{ secrets.STEAM_CONFIG_VDF}}
appId: ${{ secrets.STEAM_APP_ID }}
buildDescription: ${{ needs.version.outputs.version_hash }}
rootPath: build
depot1Path: steam_windows_64
depot2Path: steam_windows_32
depot3Path: steam_linux_64
depot4Path: steam_linux_32
releaseBranch: ${{ needs.deployment_target.outputs.steam_branch }}it fails with So unless there is something weird/non-standard in how we use the job, it seems #70 is a regression on this issue :( |
|
@TheOrioli no party pooping taken. Thank you for reporting that the issue was reintroduced. I went ahead and reverted #70 in #71. Release: https://github.com/game-ci/steam-deploy/releases/tag/v3.0.3 We need the next person who moves the image to latest to pin it to an actual version and properly test the fix as provided to the public, rather than a specific workflow. Cheers all! |
|
I started experiencing this issue again. Used that as opportunity to upgrade all the actions used in my workflow file, still experienced the "invalid password" error. Had to regenerate the vdf file three times before the error went away and the workflow succeeded. If anyone else comes across this, I've had to do this process of regenerating the vdf file at least 3 times multiple times now. It expires at irregular intervals and regenerating the file never works the first time. |
Not sure if it is related, but in our experience, we cannot run multiple instances of this action concurrently. For example, if we have 2 builds that are being uploaded at the same time with the same credentials, the actions will fail. We have since then linearized our deployments into a queue to eliminate concurrency and that helped with the issue. |
Bug description
I was having some issues authenticating with Steam Guard with v1 of this action, so I recently upgraded to v3 (I was told doing so might fix the issue). That issue is gone now, but now in the "Test login" step, I get this error:
From what I understand, we no longer have to pass the STEAM_PASSWORD secret, so what would cause this error?
I've consistently gotten this error each time I run the workflow, resulting in the job failing and the build not making it to Steam.
Additional details
The text was updated successfully, but these errors were encountered: