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

Steam update fail, possibly causing clients to not connect? #41

Closed
xBeEatNUx opened this issue Oct 11, 2022 · 9 comments
Closed

Steam update fail, possibly causing clients to not connect? #41

xBeEatNUx opened this issue Oct 11, 2022 · 9 comments
Labels
bug Something isn't working indeterminate cause No cause could be found for this issue. Hopefully it is not recurring.

Comments

@xBeEatNUx
Copy link

Describe the bug
Upon pulling the image and running the docker, Steam fails to update.
This may be causing steam clients to not able to connect even though Steam is enabled.
I have all proper ports open on the docker side and network side and nothing is connected.

To Reproduce
Steps to reproduce the behavior:

  1. Pull Image.
  2. Start the container with default env vars,
  3. Check the Log and it will show Steam failing to update.

Expected behavior
Steam updates the version, fails tries again, fails and reverts to old version

Desktop (please complete the following information):

  • OS: Debian Bullseye(Proxmox)
  • Docker Version : 20.10.18

Additional context
Just not sure why this container is not passing through the ports correctly. Every other VM is working and port forwarding is working.
_zomboid-dedicated-server_logs.txt

@xBeEatNUx xBeEatNUx added the bug Something isn't working label Oct 11, 2022
@xBeEatNUx
Copy link
Author

update: I tried a few other releases for a dedicated docker server and each connected fine. So maybe it's related do the build?

@Renegade-Master
Copy link
Owner

Try again tomorrow. Tuesday is patch day for Steam.

I'll investigate if it is still present then 👍

@Renegade-Master
Copy link
Owner

Also just to clear some things up:

I have all proper ports open on the docker side and network side and nothing is connected.

This wouldn't affect Steam being able to update. Open ports allow connections in, but you can still connect to the Internet without them.

Just not sure why this container is not passing through the ports correctly

We don't know yet if there is any issue with ports. All we know is that Steam cannot connect to the Internet / Steam servers, or Steam pushed a bad Client update.


The logs indicate that everything is working. I can't see any issue from them.


What is the output of the command:

ss -l | grep -E "16261|8766"

@Renegade-Master
Copy link
Owner

Finally, I am hoping that it isn't, but it may be related to #42

@Renegade-Master
Copy link
Owner

@xBeEatNUx Is this issue still happening, or was it just a Tuesday thing?

@xBeEatNUx
Copy link
Author

Not sure I fought with it and decided to go with someone’s else’s build.

@Renegade-Master
Copy link
Owner

No worries. It doesn't seem to have happened to anyone else in the meantime, so I'll close this now.

Glad that you figured something out anyway! 👍

@Renegade-Master Renegade-Master closed this as not planned Won't fix, can't repro, duplicate, stale Oct 24, 2022
@xBeEatNUx
Copy link
Author

Not sure if people did what I did or just didn’t report it. Were you not able to try it ?

@Renegade-Master
Copy link
Owner

I tried it. It seems to be fine.

I still have to make the change to add the new UDP port, but that isn't preventing people from joining.

@Renegade-Master Renegade-Master added the indeterminate cause No cause could be found for this issue. Hopefully it is not recurring. label Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working indeterminate cause No cause could be found for this issue. Hopefully it is not recurring.
Projects
None yet
Development

No branches or pull requests

2 participants