[GH-ISSUE #237] Undocumented Ports for App Container Streaming #161

New issue

Closed

opened 2026-10-15 12:57:28 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-15 12:57:28 +00:00

Owner

Originally created by @MNarath1 on GitHub (Aug 10, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/237

When attempting to stream a container Moonlight will show a blackscreen and after closing showing an error complaining about 2 additional ports not shown in the Documentation for wolf:
47998/udp
48000/udp

without these ports any App stream except for the ball test will fail if you have your firewall active and didn't whitelist all the documented ports + those two

Originally created by @MNarath1 on GitHub (Aug 10, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/237 When attempting to stream a container Moonlight will show a blackscreen and after closing showing an error complaining about 2 additional ports not shown in the Documentation for wolf: 47998/udp 48000/udp without these ports any App stream except for the ball test will fail if you have your firewall active and didn't whitelist all the documented ports + those two

bsakaguchi

2026-10-15 12:57:28 +00:00

closed this issue
added the
cannot reproduce
label

bsakaguchi commented

2026-10-15 12:57:29 +00:00

Author

Owner

@ABeltramo commented on GitHub (Aug 11, 2025):

When attempting to stream a container Moonlight will show a blackscreen and after closing showing an error complaining about 2 additional ports

The ports shown in the Moonlight error message are just the defaults. It'll show that message regardless of what Wolf is actually using when there's an issue whilst attempting to establish a connection.

I have just quickly tested the latest wolf:stable with the following:

-p 47984:47984/tcp 
-p 47989:47989/tcp
-p 47999:47999/udp 
-p 48010:48010/tcp 
-p 48100:48100/udp 
-p 48200:48200/udp

and I can correctly stream both from Android and OSX.
Can you confirm the exact docker run/compose.yml file that you use to run Wolf and which Moonlight client is failing to connect? Also make sure that you are using the latest:

docker pull ghcr.io/games-on-whales/wolf:stable

@ABeltramo commented on GitHub (Aug 11, 2025): > When attempting to stream a container Moonlight will show a blackscreen and after closing showing an error complaining about 2 additional ports The ports shown in the Moonlight error message are just the defaults. It'll show that message regardless of what Wolf is actually using when there's an issue whilst attempting to establish a connection. I have just quickly tested the latest `wolf:stable` with the following: ``` -p 47984:47984/tcp -p 47989:47989/tcp -p 47999:47999/udp -p 48010:48010/tcp -p 48100:48100/udp -p 48200:48200/udp ``` and I can correctly stream both from Android and OSX. Can you confirm the exact `docker run`/`compose.yml` file that you use to run Wolf and which Moonlight client is failing to connect? Also make sure that you are using the latest: ``` docker pull ghcr.io/games-on-whales/wolf:stable ```

bsakaguchi commented

2026-10-15 12:57:29 +00:00

Author

Owner

@MNarath1 commented on GitHub (Aug 12, 2025):

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    environment:
      - XDG_RUNTIME_DIR=/tmp/sockets
      - HOST_APPS_STATE_FOLDER=/etc/wolf
    volumes:
      - /etc/wolf/:/etc/wolf
      - /tmp/sockets:/tmp/sockets:rw
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/:/dev/:rw
      - /run/udev:/run/udev:rw
#    ports:
#      - "47984:47984/tcp"
#      - "47989:47989/tcp"
#      - "47999:47999/udp"
#      - "48010:48010/tcp"
#      - "48100:48100/udp"
#      - "48200:48200/udp"
    network_mode: host
    device_cgroup_rules:
      - 'c 13:* rmw'
    devices:
      - /dev/dri
      - /dev/uinput
      - /dev/uhid
    restart: unless-stopped

in this case i put it into host mode and whitelisted all the ports shown above + the two in my issue in the firewall before all containers would fail to stream besides the ball test which i don't think even spawns its own container
with not stream i mean it would start with a blackscreen and then fail after a short wile showing the mentioned error message

The Client failing to connect is the linux client specifically the flatpak version.

@MNarath1 commented on GitHub (Aug 12, 2025): ``` version: "3" services: wolf: image: ghcr.io/games-on-whales/wolf:stable environment: - XDG_RUNTIME_DIR=/tmp/sockets - HOST_APPS_STATE_FOLDER=/etc/wolf volumes: - /etc/wolf/:/etc/wolf - /tmp/sockets:/tmp/sockets:rw - /var/run/docker.sock:/var/run/docker.sock:rw - /dev/:/dev/:rw - /run/udev:/run/udev:rw # ports: # - "47984:47984/tcp" # - "47989:47989/tcp" # - "47999:47999/udp" # - "48010:48010/tcp" # - "48100:48100/udp" # - "48200:48200/udp" network_mode: host device_cgroup_rules: - 'c 13:* rmw' devices: - /dev/dri - /dev/uinput - /dev/uhid restart: unless-stopped ``` in this case i put it into host mode and whitelisted all the ports shown above + the two in my issue in the firewall before all containers would fail to stream besides the ball test which i don't think even spawns its own container with not stream i mean it would start with a blackscreen and then fail after a short wile showing the mentioned error message The Client failing to connect is the linux client specifically the flatpak version.

bsakaguchi commented

2026-10-15 12:57:30 +00:00

Author

Owner

@MNarath1 commented on GitHub (Aug 12, 2025):

the host OS is fedora 42 KDE

@MNarath1 commented on GitHub (Aug 12, 2025): the host OS is fedora 42 KDE

bsakaguchi commented

2026-10-15 12:57:30 +00:00

Author

Owner

@ABeltramo commented on GitHub (Aug 12, 2025):

all containers would fail to stream besides the ball test which i don't think even spawns its own container

That is a different issue, if test ball works then all the ports required are open and working. There's no network difference between that audio/video stream and a fully running app. Please post the full Wolf logs, you most likely have issues starting apps that are unrelated to the network.

@ABeltramo commented on GitHub (Aug 12, 2025): > all containers would fail to stream besides the ball test which i don't think even spawns its own container That is a different issue, if test ball works then all the ports required are open and working. There's no network difference between that audio/video stream and a fully running app. Please post the full Wolf logs, you most likely have issues starting apps that are unrelated to the network.