[GH-ISSUE #182] Two moonlight clients open the same WolfSteam container. #120

New issue

Closed

opened 2026-10-15 12:56:41 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 12:56:41 +00:00

Owner

Originally created by @mikewalshchicago on GitHub (Mar 9, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/182

I have 4 android phones that all open their own WolfSteam containers:

Samsung Galaxy S23 (WolfSteam_8008644282096080745)
Motorola G Stylus 5G 2024 (WolfSteam_16877080310235585842)
Motorola G Stylus 5G 2023 (TBD, phone not available for test at the moment)
Essential PH-1 (WolfSteam_4324910375206041314 )

I tried to add a 5th phone to Wolf (Samsung Galaxy s10e) using the same method I have used for the first 4. I add the PC to moonlight by IP and validate the PIN generated on the Wolf host. The WolfSteam container starts up normally BUT curiously it is WolfSteam_8008644282096080745, or the container that was created for the Galaxy s23. If I try to start the WolfSteam on both the s10e and the s23, for a brief moment I will have both of them connected to the same session. The screen is usually black but I can hear audio and sometimes move the cursor. Eventually they will both disconnect with timeout error -1 being reported on the moonlight client.

The two Samsung Galaxy phones are the only ones that behave this way. I can have the other 3 phones connected and they do not experience any distruption from the other two phones fighting over WolfSteam_8008644282096080745. I wonder if there is something common between the hardware IDs on the two phones that may be used in generating the client certificate. It may also be possible that I restored a backup of the moonlight client from the s10e to the s23, in which case a token file that was generated and intended to be unique to the installation may have been copied.

I attached a log as well as a .toml file. The scenario played out by the log is as follows:

PC is started, docker config changed to DEBUG log level and restarted
moonlight client on s10e is started and connects successfully to WolfSteam_8008644282096080745 (which i'm positive was first created by the s23 phone)
moonlight client on s23 started and connection to WolfSteam_8008644282096080745 is attempted, screen is black, and after ~30 seconds, the stream on the s10e times out with error code -1.
I delete the PC profile on the s10e moonlight client.
I discover the PC again by IP address, and register it with Wolf using the PIN generated by the client
Attempting to connect to WolfSteam again, I see it again tries WolfSteam_8008644282096080745, disconnects the s23 session (timeout error code -1).

In the .toml file, I see there are multiple paired_clients with the value '8008644282096080745'. the client_certs (removed) appear to be the same in each

The logs repeat the following error:

[CURL] error 404 - {"message":"No such container: d6da567a53f76fd088f2529ce9ae9ef99a37a98a733fe83668d3658dd3a92a40"}

I am not sure what this container is. I did create a container called WolfShutdown, which appears to execute fine.

docker image list | grep wolfshutdown

wolfshutdown latest 050b3b23833a 3 months ago 80.1MB

I also added the heroic launcher continer from the gow repository. the other containers should be the default.

Originally created by @mikewalshchicago on GitHub (Mar 9, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/182 I have 4 android phones that all open their own WolfSteam containers: Samsung Galaxy S23 (WolfSteam_8008644282096080745) Motorola G Stylus 5G 2024 (WolfSteam_16877080310235585842) Motorola G Stylus 5G 2023 (TBD, phone not available for test at the moment) Essential PH-1 (WolfSteam_4324910375206041314 ) I tried to add a 5th phone to Wolf (Samsung Galaxy s10e) using the same method I have used for the first 4. I add the PC to moonlight by IP and validate the PIN generated on the Wolf host. The WolfSteam container starts up normally BUT curiously it is WolfSteam_8008644282096080745, or the container that was created for the Galaxy s23. If I try to start the WolfSteam on both the s10e and the s23, for a brief moment I will have both of them connected to the same session. The screen is usually black but I can hear audio and sometimes move the cursor. Eventually they will both disconnect with timeout error -1 being reported on the moonlight client. The two Samsung Galaxy phones are the only ones that behave this way. I can have the other 3 phones connected and they do not experience any distruption from the other two phones fighting over WolfSteam_8008644282096080745. I wonder if there is something common between the hardware IDs on the two phones that may be used in generating the client certificate. It may also be possible that I restored a backup of the moonlight client from the s10e to the s23, in which case a token file that was generated and intended to be unique to the installation may have been copied. I attached a log as well as a .toml file. The scenario played out by the log is as follows: 1. PC is started, docker config changed to DEBUG log level and restarted 2. moonlight client on s10e is started and connects successfully to WolfSteam_8008644282096080745 (which i'm positive was first created by the s23 phone) 3. moonlight client on s23 started and connection to WolfSteam_8008644282096080745 is attempted, screen is black, and after ~30 seconds, the stream on the s10e times out with error code -1. 4. I delete the PC profile on the s10e moonlight client. 5. I discover the PC again by IP address, and register it with Wolf using the PIN generated by the client 6. Attempting to connect to WolfSteam again, I see it again tries WolfSteam_8008644282096080745, disconnects the s23 session (timeout error code -1). In the .toml file, I see there are multiple [[paired_clients]] with the value '8008644282096080745'. the client_certs (removed) appear to be the same in each The logs repeat the following error: [CURL] error 404 - {"message":"No such container: d6da567a53f76fd088f2529ce9ae9ef99a37a98a733fe83668d3658dd3a92a40"} I am not sure what this container is. I did create a container called WolfShutdown, which appears to execute fine. # docker image list | grep wolfshutdown wolfshutdown latest 050b3b23833a 3 months ago 80.1MB I also added the heroic launcher continer from the gow repository. the other containers should be the default.

bsakaguchi closed this issue

2026-10-15 12:56:41 +00:00

bsakaguchi commented

2026-10-15 12:56:42 +00:00

Author

Owner

@mikewalshchicago commented on GitHub (Mar 9, 2025):

I deleted the data in the moonlight app settings and started clean on the s10e. After adding the Wolf host IP and authenticating with the PIN generated, a new docker container (WolfSteam_5203481669705877121) was created. My assumption is that I restored the apk from a backup on the Galaxy s23 from the s10e, so both phones had the same token file that is used to generate the client certificate for the device.

@mikewalshchicago commented on GitHub (Mar 9, 2025): I deleted the data in the moonlight app settings and started clean on the s10e. After adding the Wolf host IP and authenticating with the PIN generated, a new docker container (WolfSteam_5203481669705877121) was created. My assumption is that I restored the apk from a backup on the Galaxy s23 from the s10e, so both phones had the same token file that is used to generate the client certificate for the device.