[GH-ISSUE #230 ] Help first time setting up Wolf #156

Author

Owner

@ABeltramo commented on GitHub (Jul 19, 2025):

On startup, Wolf tries all possible encoders to see what's available on your computer. You can easily ignore all those lines at the beginning (VAAPI is only available on AMD/Intel anyway).
The important bits for you are:

Using H264 encoder: nvcodec
Using HEVC encoder: nvcodec

which means that it correctly picked up the Nvidia encoder.
Do you have any other issue when starting a stream?

@ABeltramo commented on GitHub (Jul 19, 2025): On startup, Wolf tries all possible encoders to see what's available on your computer. You can easily ignore all those lines at the beginning (VAAPI is only available on AMD/Intel anyway). The important bits for you are: ``` Using H264 encoder: nvcodec Using HEVC encoder: nvcodec ``` which means that it correctly picked up the Nvidia encoder. Do you have any other issue when starting a stream?

bsakaguchi commented

Author

Owner

@KommanderKeen commented on GitHub (Jul 19, 2025):

Well, I also have the Unable to connect to Pulse, Access Denied.
Isn't it a problem ?

Well, I can see the computer in Moonlight but I don't think I have a Sunshine running.
I have only theses ports listening :
tcp LISTEN 0 4096 0.0.0.0:48010 0.0.0.0:* users:(("wolf",pid=1103,fd=21))
tcp LISTEN 0 4096 0.0.0.0:47984 0.0.0.0:* users:(("wolf",pid=1103,fd=43))
tcp LISTEN 0 4096 0.0.0.0:47989 0.0.0.0:* users:(("wolf",pid=1103,fd=27))

@KommanderKeen commented on GitHub (Jul 19, 2025): Well, I also have the Unable to connect to Pulse, Access Denied. Isn't it a problem ? Well, I can see the computer in Moonlight but I don't think I have a Sunshine running. I have only theses ports listening : tcp LISTEN 0 4096 0.0.0.0:48010 0.0.0.0:* users:(("wolf",pid=1103,fd=21)) tcp LISTEN 0 4096 0.0.0.0:47984 0.0.0.0:* users:(("wolf",pid=1103,fd=43)) tcp LISTEN 0 4096 0.0.0.0:47989 0.0.0.0:* users:(("wolf",pid=1103,fd=27))

bsakaguchi commented

Author

Owner

@ABeltramo commented on GitHub (Jul 19, 2025):

Wolf isn't Sunshine 😉
Ports will be open and bound when a connection starts, go on with Moonlight..

@ABeltramo commented on GitHub (Jul 19, 2025): Wolf isn't Sunshine 😉 Ports will be open and bound when a connection starts, go on with Moonlight..

bsakaguchi commented

Author

Owner

@KommanderKeen commented on GitHub (Jul 19, 2025):

My mistake, just understood that.
I pinned ok.
But when I tried firefox I got a black screen the a message about opening ports on my firewall.
I'm doing all in local. it shouldn't be question about firewalls, right ?

@KommanderKeen commented on GitHub (Jul 19, 2025): My mistake, just understood that. I pinned ok. But when I tried firefox I got a black screen the a message about opening ports on my firewall. I'm doing all in local. it shouldn't be question about firewalls, right ?

bsakaguchi commented

Author

Owner

@ABeltramo commented on GitHub (Jul 19, 2025):

If it's network related you'll see that the Firefox app is still running and you can re-connect to it from Moonlight. If it's the Firefox container failing to start instead you can post again the Wolf logs to see what's going on.
As for the ports needed you'll have to expose the followings:

# HTTPS
EXPOSE 47984/tcp
# HTTP
EXPOSE 47989/tcp
# Control
EXPOSE 47999/udp
# RTSP
EXPOSE 48010/tcp
# Video
EXPOSE 48100/udp
# Audio
EXPOSE 48200/udp

@ABeltramo commented on GitHub (Jul 19, 2025): If it's network related you'll see that the Firefox app is still running and you can re-connect to it from Moonlight. If it's the Firefox container failing to start instead you can post again the Wolf logs to see what's going on. As for the ports needed you'll have to expose the followings: ```dockerfile # HTTPS EXPOSE 47984/tcp # HTTP EXPOSE 47989/tcp # Control EXPOSE 47999/udp # RTSP EXPOSE 48010/tcp # Video EXPOSE 48100/udp # Audio EXPOSE 48200/udp ```

bsakaguchi commented

Author

Owner

@KommanderKeen commented on GitHub (Jul 19, 2025):

Ok so it is network related since I can try to re-enter it.

These expose, are like firewall rules I need to put into my router or only in the docker compose wolf ?
Sorry if the question seems stupid :S

Moreover it tells me about UDP 47998 and UDP 48000 which are not in your list

@KommanderKeen commented on GitHub (Jul 19, 2025): Ok so it is network related since I can try to re-enter it. These expose, are like firewall rules I need to put into my router or only in the docker compose wolf ? Sorry if the question seems stupid :S Moreover it tells me about UDP 47998 and UDP 48000 which are not in your list

bsakaguchi commented

Author

Owner

@ABeltramo commented on GitHub (Jul 19, 2025):

If you are connecting to it via LAN there's no need to open them in the router, in fact, we discourage users from opening this up to the web.
It might be something missing from your LXC configuration, can you share your full config file?

@ABeltramo commented on GitHub (Jul 19, 2025): If you are connecting to it via LAN there's no need to open them in the router, in fact, we discourage users from opening this up to the web. It might be something missing from your LXC configuration, can you share your full config file?

bsakaguchi commented

Author

Owner

@KommanderKeen commented on GitHub (Jul 19, 2025):

services:
  wolf:
    image: ghcr.io/games-on-whales/wolf:stable
    container_name: wolf-backend # Ajout pour une gestion plus facile
    restart: unless-stopped
    network_mode: host

    environment:
      - XDG_RUNTIME_DIR=/tmp/sockets
      - HOST_APPS_STATE_FOLDER=/etc/wolf
      # La doc officielle ne mentionne pas les variables NVIDIA ici,
      # car elles sont suppos  es   tre g  r  es par les options ci-dessous.
      # Nous les ajoutons par s  curit  , car elles ne peuvent pas nuire.
      - NVIDIA_DRIVER_CAPABILITIES=all
      - NVIDIA_VISIBLE_DEVICES=all
      - WOLF_RENDER_NODE=/dev/dri/renderD128
      - WOLF_ENCODER_NODE=/dev/dri/renderD128
      - WOLF_LOG_LEVEL=DEBUG
    
    volumes:
      # --- LA SEULE LIGNE ADAPT ^iE ---
      - /mnt/massSharedStorage1/persistence/games-on-whales/wolf/config:/etc/wolf:rw

      # Les autres volumes, exactement comme dans la doc
      - /tmp/sockets:/tmp/sockets:rw
      - /var/run/docker.sock:/var/run/docker.sock:rw
      - /dev/:/dev/:rw
      - /run/udev:/run/udev:rw
    
    # Les options de la doc que j'avais omises,    tort.
    device_cgroup_rules:
      - 'c 13:* rmw' # Acc  s aux p  riph  riques d'input

    devices:
      - /dev/dri # Direct Rendering Infrastructure (important)
      - /dev/uinput # Pour la cr  ation de p  riph  riques d'input virtuels (manettes)
      - /dev/uhid # Pour les p  riph  riques HID

    # L'option runtime: nvidia n'est pas dans la doc que vous avez post  e,
    # mais elle est devenue le standard. On la garde, car elle est plus moderne
    # et g  re mieux que la simple liste de devices.
    runtime: nvidia
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1
              capabilities: [gpu]

I just see that my LXC has firewall checked, I guess I have to open these ports as rules into this specific firewall ?

@KommanderKeen commented on GitHub (Jul 19, 2025): ```yml services: wolf: image: ghcr.io/games-on-whales/wolf:stable container_name: wolf-backend # Ajout pour une gestion plus facile restart: unless-stopped network_mode: host environment: - XDG_RUNTIME_DIR=/tmp/sockets - HOST_APPS_STATE_FOLDER=/etc/wolf # La doc officielle ne mentionne pas les variables NVIDIA ici, # car elles sont suppos es tre g r es par les options ci-dessous. # Nous les ajoutons par s curit , car elles ne peuvent pas nuire. - NVIDIA_DRIVER_CAPABILITIES=all - NVIDIA_VISIBLE_DEVICES=all - WOLF_RENDER_NODE=/dev/dri/renderD128 - WOLF_ENCODER_NODE=/dev/dri/renderD128 - WOLF_LOG_LEVEL=DEBUG volumes: # --- LA SEULE LIGNE ADAPT ^iE --- - /mnt/massSharedStorage1/persistence/games-on-whales/wolf/config:/etc/wolf:rw # Les autres volumes, exactement comme dans la doc - /tmp/sockets:/tmp/sockets:rw - /var/run/docker.sock:/var/run/docker.sock:rw - /dev/:/dev/:rw - /run/udev:/run/udev:rw # Les options de la doc que j'avais omises, tort. device_cgroup_rules: - 'c 13:* rmw' # Acc s aux p riph riques d'input devices: - /dev/dri # Direct Rendering Infrastructure (important) - /dev/uinput # Pour la cr ation de p riph riques d'input virtuels (manettes) - /dev/uhid # Pour les p riph riques HID # L'option runtime: nvidia n'est pas dans la doc que vous avez post e, # mais elle est devenue le standard. On la garde, car elle est plus moderne # et g re mieux que la simple liste de devices. runtime: nvidia deploy: resources: reservations: devices: - driver: nvidia count: 1 capabilities: [gpu] ``` I just see that my LXC has firewall checked, I guess I have to open these ports as rules into this specific firewall ?

bsakaguchi commented

Author

Owner

@ABeltramo commented on GitHub (Jul 19, 2025):

That looks like a docker-compose.yml there's only one issue with it, just change the followings:

environment:
      - HOST_APPS_STATE_FOLDER=/mnt/massSharedStorage1/persistence/games-on-whales/wolf/
volumes:
      # --- LA SEULE LIGNE ADAPT ^iE ---
      - /mnt/massSharedStorage1/persistence/games-on-whales/wolf/config:/etc/wolf/config:rw
      - /mnt/massSharedStorage1/persistence/games-on-whales/wolf/:/mnt/massSharedStorage1/persistence/games-on-whales/wolf/

(see here for an explanation).

Apart from that, that docker-compose.yml file is running inside an LXC container, right? You'll have to share the configuration for that LXC container because it might be that you haven't opened the port there..

@ABeltramo commented on GitHub (Jul 19, 2025): That looks like a `docker-compose.yml` there's only one issue with it, just change the followings: ```yaml environment: - HOST_APPS_STATE_FOLDER=/mnt/massSharedStorage1/persistence/games-on-whales/wolf/ volumes: # --- LA SEULE LIGNE ADAPT ^iE --- - /mnt/massSharedStorage1/persistence/games-on-whales/wolf/config:/etc/wolf/config:rw - /mnt/massSharedStorage1/persistence/games-on-whales/wolf/:/mnt/massSharedStorage1/persistence/games-on-whales/wolf/ ``` (see [here](https://games-on-whales.github.io/wolf/stable/user/configuration.html#_change_the_host_apps_state_folder) for an explanation). Apart from that, that `docker-compose.yml` file is running inside an LXC container, right? You'll have to share the configuration for that LXC container because it might be that you haven't opened the port there..

bsakaguchi commented

Author

Owner

@KommanderKeen commented on GitHub (Jul 19, 2025):

arch: amd64
cores: 4
dev0: /dev/nvidia0,gid=996,mode=0660,uid=999
dev1: /dev/dri/renderD128,gid=996,mode=0660,uid=999
dev2: /dev/nvidiactl,gid=996,mode=0660,uid=999
dev3: /dev/nvidia-uvm,gid=996,mode=0660,uid=999
dev4: /dev/nvidia-modeset,mode=0660
dev5: /dev/nvidia-uvm-tools,gid=996,mode=0660,uid=999
dev6: /dev/nvidia-caps/nvidia-cap1,gid=996,mode=0660,uid=999
dev7: /dev/nvidia-caps/nvidia-cap2,gid=996,mode=0660,uid=999
dev8: /dev/uinput,gid=101,mode=0660
dev9: /dev/uhid,mode=0660
features: nesting=1,keyctl=1
hostname: games-on-whales
memory: 16384
mp0: /mnt/massSharedStorage1/persistence/games-on-whales,mp=/config
net0: name=eth0,bridge=vmbr1,firewall=1,gw=192.168.1.254,hwaddr=BC:24:11:6F:90:53,ip=192.168.1.11/23,type=veth
ostype: debian
rootfs: local-lvm:vm-305-disk-0,size=360G
swap: 4096
lxc.cgroup2.devices.allow: c 195:0 rwm
lxc.cgroup2.devices.allow: c 195:255 rwm
lxc.cgroup2.devices.allow: c 511:* rwm
lxc.cgroup2.devices.allow: c 237:* rwm
lxc.cgroup2.devices.allow: c 195:254 rwm
lxc.cgroup2.devices.allow: c 10:223 rwm
lxc.cgroup2.devices.allow: c 10:239 rwm

@KommanderKeen commented on GitHub (Jul 19, 2025): ``` arch: amd64 cores: 4 dev0: /dev/nvidia0,gid=996,mode=0660,uid=999 dev1: /dev/dri/renderD128,gid=996,mode=0660,uid=999 dev2: /dev/nvidiactl,gid=996,mode=0660,uid=999 dev3: /dev/nvidia-uvm,gid=996,mode=0660,uid=999 dev4: /dev/nvidia-modeset,mode=0660 dev5: /dev/nvidia-uvm-tools,gid=996,mode=0660,uid=999 dev6: /dev/nvidia-caps/nvidia-cap1,gid=996,mode=0660,uid=999 dev7: /dev/nvidia-caps/nvidia-cap2,gid=996,mode=0660,uid=999 dev8: /dev/uinput,gid=101,mode=0660 dev9: /dev/uhid,mode=0660 features: nesting=1,keyctl=1 hostname: games-on-whales memory: 16384 mp0: /mnt/massSharedStorage1/persistence/games-on-whales,mp=/config net0: name=eth0,bridge=vmbr1,firewall=1,gw=192.168.1.254,hwaddr=BC:24:11:6F:90:53,ip=192.168.1.11/23,type=veth ostype: debian rootfs: local-lvm:vm-305-disk-0,size=360G swap: 4096 lxc.cgroup2.devices.allow: c 195:0 rwm lxc.cgroup2.devices.allow: c 195:255 rwm lxc.cgroup2.devices.allow: c 511:* rwm lxc.cgroup2.devices.allow: c 237:* rwm lxc.cgroup2.devices.allow: c 195:254 rwm lxc.cgroup2.devices.allow: c 10:223 rwm lxc.cgroup2.devices.allow: c 10:239 rwm ```

bsakaguchi commented

Author

Owner

@ABeltramo commented on GitHub (Jul 19, 2025):

I would check that firewall=1. It's highly suspicious.. 😉

@ABeltramo commented on GitHub (Jul 19, 2025): I would check that `firewall=1`. It's highly suspicious.. 😉

bsakaguchi commented

Author

Owner

@KommanderKeen commented on GitHub (Jul 19, 2025):

I would check that firewall=1. It's highly suspicious.. 😉

Disabled it, no change

@KommanderKeen commented on GitHub (Jul 19, 2025): > I would check that `firewall=1`. It's highly suspicious.. 😉 Disabled it, no change

bsakaguchi commented

Author

Owner

@KommanderKeen commented on GitHub (Jul 20, 2025):

I have a little more information,I used tcpdump and I got this :

12:33:49.355275 IP 192.168.1.11.48200 > 192.168.1.251.54209: UDP, length 88
12:33:49.356984 IP 192.168.1.251.54210 > 192.168.1.11.47999: UDP, length 46
12:33:49.356989 IP 192.168.1.251.54210 > 192.168.1.11.47999: UDP, length 12
12:33:49.357050 IP 192.168.1.11.47999 > 192.168.1.251.54210: UDP, length 10

So it seems my wolf can contact my client running Moonlight and it can answer back but when it comes to video stream it fails (47998 and 48000)

I guess it is related to the wolf logs ?

By the way I'm using driver nvidia 550.127.05 Cuda 12.4

I tried Test Ball it works

Here are the Docker wolf logs when I try to start Firefox inside wolf :

13:00:12.218565394 DEBUG | 192.168.1.251 [GET] HTTP://192.168.1.11/serverinfo
13:00:12.253882316 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/serverinfo
13:00:12.280261665 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/applist
13:00:14.485213218 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/launch
13:00:14.485403973 DEBUG | Host app state folder: /mnt/massSharedStorage1/persistence/games-on-whales/wolf/9755996566729338573/Firefox, creating paths
13:00:14.485504651 DEBUG | [STREAM_SESSION] Create wayland compositor
13:00:14.485570671 DEBUG | [STREAM_SESSION] Create virtual audio sink
13:00:14.485598039 DEBUG | [GSTREAMER] Starting video producer: waylanddisplaysrc name=wolf_wayland_source render_node=/dev/dri/renderD128 ! video/x-raw(memory:DMABuf), width=1920, height=1080, framerate=60/1 ! 
interpipesink sync=true async=false name=9755996566729338573_video max-buffers=1
13:00:14.485694551 DEBUG | [GSTREAMER] Starting audio producer: pulsesrc device="virtual_sink_9755996566729338573.monitor" server="/tmp/sockets/pulse-socket" ! audio/x-raw, channels=2, rate=48000 ! queue leaky=downstream max-size-buffers=3 ! interpipesink name="9755996566729338573_audio" sync=true async=false max-buffers=3
13:00:14.486115499 DEBUG | Setting up waylanddisplaysrc

(wolf:1): GStreamer-CRITICAL **: 14:00:14.486: Bus bus73 already has a GSource watch

thread '<unnamed>' panicked at wayland-display-core/src/utils/renderer/mod.rs:23:44:
called `Result::unwrap()` on an `Err` value: PoisonError { .. }
stack backtrace:
13:00:14.486558025 DEBUG | [PULSE] Created virtual sink: 8
   0:     0x737f300e6682 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h46a716bba2450163
   1:     0x737f30106f13 - core::fmt::write::h275e5980d7008551
   2:     0x737f300e38a3 - std::io::Write::write_fmt::h561a66a0340b6995
   3:     0x737f300e64d2 - std::sys::backtrace::BacktraceLock::print::hafb9d5969adc39a0
   4:     0x737f300e7932 - std::panicking::default_hook::{{closure}}::hae2e97a5c4b2b777
   5:     0x737f300e7735 - std::panicking::default_hook::h3db1b505cfc4eb79
   6:     0x737f300e82d2 - std::panicking::rust_panic_with_hook::h409da73ddef13937
   7:     0x737f300e807a - std::panicking::begin_panic_handler::{{closure}}::h159b61b27f96a9c2
   8:     0x737f300e6b79 - std::sys::backtrace::__rust_end_short_backtrace::h5b56844d75e766fc
   9:     0x737f300e7d0d - __rustc[4794b31dd7191200]::rust_begin_unwind
  10:     0x737f2fea1730 - core::panicking::panic_fmt::hc8737e8cca20a7c8
  11:     0x737f2fea1af6 - core::result::unwrap_failed::h727108008d9f4c9b
  12:     0x737f2ffa4d51 - waylanddisplaycore::utils::renderer::setup_renderer::h15aad7353d982a2e
  13:     0x737f2ff6ef83 - waylanddisplaycore::comp::init::hd1b286b8d70535d8
  14:     0x737f2feda823 - std::sys::backtrace::__rust_begin_short_backtrace::h43aa8bf9bb67dc83
  15:     0x737f2ff77cb3 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h5297442aeeaa6bab
  16:     0x737f300e93ab - std::sys::pal::unix::thread::Thread::new::thread_start::h1822d22fde68314f
  17:     0x737f3650bef1 - <unknown>
  18:     0x737f3659d244 - __clone

thread '<unnamed>' panicked at wayland-display-core/src/lib.rs:99:41:
called `Result::unwrap()` on an `Err` value: RecvError
stack backtrace:
   0:     0x737f300e6682 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h46a716bba2450163
   1:     0x737f30106f13 - core::fmt::write::h275e5980d7008551
   2:     0x737f300e38a3 - std::io::Write::write_fmt::h561a66a0340b6995
   3:     0x737f300e64d2 - std::sys::backtrace::BacktraceLock::print::hafb9d5969adc39a0
   4:     0x737f300e7932 - std::panicking::default_hook::{{closure}}::hae2e97a5c4b2b777
   5:     0x737f300e7735 - std::panicking::default_hook::h3db1b505cfc4eb79
   6:     0x737f300e82d2 - std::panicking::rust_panic_with_hook::h409da73ddef13937
   7:     0x737f300e807a - std::panicking::begin_panic_handler::{{closure}}::h159b61b27f96a9c2
   8:     0x737f300e6b79 - std::sys::backtrace::__rust_end_short_backtrace::h5b56844d75e766fc
   9:     0x737f300e7d0d - __rustc[4794b31dd7191200]::rust_begin_unwind
  10:     0x737f2fea1730 - core::panicking::panic_fmt::hc8737e8cca20a7c8
  11:     0x737f2fea1af6 - core::result::unwrap_failed::h727108008d9f4c9b
  12:     0x737f2fee0f95 - waylanddisplaycore::MaybeRecv<T>::get::h33a8dc3c1cb5e468
  13:     0x737f2fee151a - waylanddisplaycore::WaylandDisplay::env_vars::h53b5e6549c8cbd59
  14:     0x737f2fea79ef - <gstwaylanddisplaysrc::waylandsrc::imp::WaylandDisplaySrc as gstreamer_base::subclass::base_src::BaseSrcImpl>::start::h99f72592ffc14553
  15:     0x737f2fea92ab - gstreamer_base::subclass::base_src::base_src_start::h14fbfb9fbecc7006
  16:     0x737f3710ddea - <unknown>
  17:     0x737f3710e328 - <unknown>
  18:     0x737f36fdbe9d - <unknown>
  19:     0x737f36fdc841 - gst_pad_set_active
  20:     0x737f36fb0ec5 - <unknown>
  21:     0x737f36fc8bc4 - gst_iterator_fold
  22:     0x737f36fb3c01 - <unknown>
  23:     0x737f3710bc4d - <unknown>
  24:     0x737f2feb3d8d - gstreamer::subclass::element::element_change_state::h4a1769e7ce647991
  25:     0x737f36fb6394 - gst_element_change_state
  26:     0x737f36fb6982 - <unknown>
  27:     0x737f36f8d112 - <unknown>
  28:     0x737f36fe5eee - <unknown>
  29:     0x737f36fb6394 - gst_element_change_state
  30:     0x737f36fb63db - gst_element_change_state
  31:     0x737f36fb6982 - <unknown>
13:00:14.525136888 DEBUG | [RTSP] found session by matching payload: 248.98.9.221
13:00:14.525170198 DEBUG | [RTSP] received command OPTIONS
  32:     0x5fa0c1d943e6 - run_pipeline
                               at /wolf/src/moonlight-server/./streaming/streaming.hpp:99:24
  33:     0x5fa0c1d956cd - _ZN9streaming20start_video_producerEmRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_RKN4wolf4core15virtual_display11DisplayModeESt10shared_ptrIN5boost7promiseINS_19WaylandDisplayReadyEEEESE_IN2dp9event_busIJN5immer3boxINS9_6events15PlugDeviceEventENSM_13memory_policyINSM_21free_list_heap_policyINSM_8cpp_heapELm1024EEENSM_15refcount_policyENSM_15spinlock_policyENSM_20no_transience_policyELb0ELb1EEEEENSN_INSO_10PairSignalESX_EENSN_INSO_17UnplugDeviceEventESX_EENSN_INSO_13StreamSessionESX_EENSN_INSO_12VideoSessionESX_EENSN_INSO_12AudioSessionESX_EENSN_INSO_15IDRRequestEventESX_EENSN_INSO_16PauseStreamEventESX_EENSN_INSO_17ResumeStreamEventESX_EENSN_INSO_15StopStreamEventESX_EENSN_INSO_17RTPVideoPingEventESX_EENSN_INSO_17RTPAudioPingEventESX_EENSN_INSO_11StartRunnerESX_EEEEEE
                               at /wolf/src/moonlight-server/streaming/streaming.cpp:88:15
13:00:14.536525227 DEBUG | [RTSP] found session by matching payload: 248.98.9.221
13:00:14.536547478 DEBUG | [RTSP] received command DESCRIBE
13:00:14.558671797 DEBUG | [RTSP] found session by matching payload: 248.98.9.221
13:00:14.558696879 DEBUG | [RTSP] received command SETUP
  34:     0x5fa0c1b0875b - operator()
                               at /wolf/src/moonlight-server/wolf.cpp:222:44
  35:     0x737f368a1324 - <unknown>
  36:     0x737f3650bef1 - <unknown>
  37:     0x737f3659d244 - __clone
2025-07-20T13:00:14.560244Z  WARN waylanddisplaycore: Failed to send stop command: sending on a closed channel
18:49:00.497587987     1 0x737e4800f090 WARN                 basesrc gstbasesrc.c:3616:gst_base_src_start:<wolf_wayland_source> error: Failed to start
18:49:00.497615775     1 0x737e4800f090 WARN                 basesrc gstbasesrc.c:3984:gst_base_src_activate_push:<wolf_wayland_source> Failed to start in push mode
18:49:00.497629331     1 0x737e4800f090 WARN                GST_PADS gstpad.c:1158:gst_pad_set_active:<wolf_wayland_source:src> Failed to activate pad
18:49:00.497677557     1 0x737e4800f090 WARN                     bin gstbin.c:2816:reset_state:<wolf_wayland_source> Failed to switch back down to READY
13:00:14.569472244 DEBUG | [RTSP] found session by matching payload: 248.98.9.221
13:00:14.569494882 DEBUG | [RTSP] received command SETUP
13:00:14.591570058 DEBUG | [RTSP] found session by matching payload: 248.98.9.221
13:00:14.591591518 DEBUG | [RTSP] received command SETUP
13:00:14.613765857 DEBUG | [RTSP] found session by matching payload: 248.98.9.221
13:00:14.613789657 DEBUG | [RTSP] received command ANNOUNCE
13:00:14.613953001 DEBUG | [RTSP] Moonlight requested video format HEVC
13:00:14.613974775 DEBUG | [RTSP] Adjusted video bitrate to 31708 Kbps
13:00:14.624930255 DEBUG | [RTSP] found session by matching payload: 248.98.9.221
13:00:14.624952748 DEBUG | [RTSP] received command PLAY
13:00:14.630617830 DEBUG | [ENET] connected client: 192.168.1.251:12028
13:00:14.631493483 DEBUG | Starting video pipeline: 
interpipesrc listen-to=9755996566729338573_video is-live=true stream-sync=restart-ts max-bytes=0 max-buffers=1 leaky-type=downstream !
glupload !
glcolorconvert !
video/x-raw(memory:GLMemory),format=NV12, width=1920, height=1080, chroma-site=mpeg2, colorimetry=bt601, pixel-aspect-ratio=1/1 !
nvh265enc gop-size=-1 bitrate=31708 aud=false rc-mode=cbr zerolatency=true preset=p1 tune=ultra-low-latency multi-pass=two-pass-quarter !
h265parse !
video/x-h265, profile=main, stream-format=byte-stream !
rtpmoonlightpay_video name=moonlight_pay payload_size=1024 fec_percentage=20 min_required_fec_packets=2 !
appsink sync=false name=wolf_udp_sink

13:00:14.641355769 DEBUG | Setting up wolf_udp_sink
13:00:14.679442247 WARN  | Received MOUSE_MOVE_REL_PACKET but no mouse device is present
13:00:14.689254898 WARN  | Received MOUSE_MOVE_REL_PACKET but no mouse device is present
libEGL warning: egl: failed to create dri2 screen
2025-07-20T13:00:14.785555Z ERROR smithay::backend::egl::ffi: [EGL] 0x3001 (NOT_INITIALIZED) eglInitialize: DRI2: failed to load driver
libEGL warning: DRI2: failed to create screen
MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen
libEGL warning: DRI2: failed to create screen
2025-07-20T13:00:14.804442Z ERROR smithay::backend::egl::ffi: [EGL] 0x3001 (NOT_INITIALIZED) eglInitialize: DRI2: failed to load driver
13:00:14.932914794 DEBUG | [GSTREAMER] Forcing IDR
13:00:15.066165456 DEBUG | Starting audio pipeline: 
interpipesrc listen-to=9755996566729338573_audio is-live=true stream-sync=restart-ts max-bytes=0 max-buffers=3 block=false !
queue max-size-buffers=3 leaky=downstream ! audiorate ! audioconvert !
opusenc bitrate=96000 bitrate-type=cbr frame-size=5 bandwidth=fullband audio-type=restricted-lowdelay max-payload-size=1400 !
rtpmoonlightpay_audio name=moonlight_pay packet_duration=5 encrypt=true aes_key="51e2c797b03615dd76f5552c005dc780" aes_iv="1772640900" !
appsink name=wolf_udp_sink
13:00:15.066797566 DEBUG | Setting up wolf_udp_sink
18:49:01.676209512     1 0x737eb8001e70 WARN                 basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc11> segment format mismatched, ignore
13:00:20.390757073 WARN  | Received MOUSE_MOVE_REL_PACKET but no mouse device is present
13:00:25.285264368 DEBUG | [ENET] disconnected client: 192.168.1.251:12028
13:00:25.285310249 DEBUG | [GSTREAMER] Pausing pipeline: 9755996566729338573
13:00:25.285338212 DEBUG | [GSTREAMER] Pausing pipeline: 9755996566729338573
13:00:25.289495722 DEBUG | 192.168.1.251 [GET] HTTP://192.168.1.11/serverinfo
13:00:25.321505931 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/serverinfo
13:00:25.355173269 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/applist
13:00:28.498334290 DEBUG | 192.168.1.251 [GET] HTTP://192.168.1.11/serverinfo
13:00:28.527533637 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/serverinfo

Since I don't find how to fix this I went for the nvidia manual solution with the nvidia-driver-volume.
I now can access at least Firefox

@KommanderKeen commented on GitHub (Jul 20, 2025): I have a little more information,I used tcpdump and I got this : ``` 12:33:49.355275 IP 192.168.1.11.48200 > 192.168.1.251.54209: UDP, length 88 12:33:49.356984 IP 192.168.1.251.54210 > 192.168.1.11.47999: UDP, length 46 12:33:49.356989 IP 192.168.1.251.54210 > 192.168.1.11.47999: UDP, length 12 12:33:49.357050 IP 192.168.1.11.47999 > 192.168.1.251.54210: UDP, length 10 ``` So it seems my wolf can contact my client running Moonlight and it can answer back but when it comes to video stream it fails (47998 and 48000) I guess it is related to the wolf logs ? By the way I'm using driver nvidia 550.127.05 Cuda 12.4 I tried Test Ball it works Here are the Docker wolf logs when I try to start Firefox inside wolf : ``` 13:00:12.218565394 DEBUG | 192.168.1.251 [GET] HTTP://192.168.1.11/serverinfo 13:00:12.253882316 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/serverinfo 13:00:12.280261665 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/applist 13:00:14.485213218 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/launch 13:00:14.485403973 DEBUG | Host app state folder: /mnt/massSharedStorage1/persistence/games-on-whales/wolf/9755996566729338573/Firefox, creating paths 13:00:14.485504651 DEBUG | [STREAM_SESSION] Create wayland compositor 13:00:14.485570671 DEBUG | [STREAM_SESSION] Create virtual audio sink 13:00:14.485598039 DEBUG | [GSTREAMER] Starting video producer: waylanddisplaysrc name=wolf_wayland_source render_node=/dev/dri/renderD128 ! video/x-raw(memory:DMABuf), width=1920, height=1080, framerate=60/1 ! interpipesink sync=true async=false name=9755996566729338573_video max-buffers=1 13:00:14.485694551 DEBUG | [GSTREAMER] Starting audio producer: pulsesrc device="virtual_sink_9755996566729338573.monitor" server="/tmp/sockets/pulse-socket" ! audio/x-raw, channels=2, rate=48000 ! queue leaky=downstream max-size-buffers=3 ! interpipesink name="9755996566729338573_audio" sync=true async=false max-buffers=3 13:00:14.486115499 DEBUG | Setting up waylanddisplaysrc (wolf:1): GStreamer-CRITICAL **: 14:00:14.486: Bus bus73 already has a GSource watch thread '<unnamed>' panicked at wayland-display-core/src/utils/renderer/mod.rs:23:44: called `Result::unwrap()` on an `Err` value: PoisonError { .. } stack backtrace: 13:00:14.486558025 DEBUG | [PULSE] Created virtual sink: 8 0: 0x737f300e6682 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h46a716bba2450163 1: 0x737f30106f13 - core::fmt::write::h275e5980d7008551 2: 0x737f300e38a3 - std::io::Write::write_fmt::h561a66a0340b6995 3: 0x737f300e64d2 - std::sys::backtrace::BacktraceLock::print::hafb9d5969adc39a0 4: 0x737f300e7932 - std::panicking::default_hook::{{closure}}::hae2e97a5c4b2b777 5: 0x737f300e7735 - std::panicking::default_hook::h3db1b505cfc4eb79 6: 0x737f300e82d2 - std::panicking::rust_panic_with_hook::h409da73ddef13937 7: 0x737f300e807a - std::panicking::begin_panic_handler::{{closure}}::h159b61b27f96a9c2 8: 0x737f300e6b79 - std::sys::backtrace::__rust_end_short_backtrace::h5b56844d75e766fc 9: 0x737f300e7d0d - __rustc[4794b31dd7191200]::rust_begin_unwind 10: 0x737f2fea1730 - core::panicking::panic_fmt::hc8737e8cca20a7c8 11: 0x737f2fea1af6 - core::result::unwrap_failed::h727108008d9f4c9b 12: 0x737f2ffa4d51 - waylanddisplaycore::utils::renderer::setup_renderer::h15aad7353d982a2e 13: 0x737f2ff6ef83 - waylanddisplaycore::comp::init::hd1b286b8d70535d8 14: 0x737f2feda823 - std::sys::backtrace::__rust_begin_short_backtrace::h43aa8bf9bb67dc83 15: 0x737f2ff77cb3 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h5297442aeeaa6bab 16: 0x737f300e93ab - std::sys::pal::unix::thread::Thread::new::thread_start::h1822d22fde68314f 17: 0x737f3650bef1 - <unknown> 18: 0x737f3659d244 - __clone thread '<unnamed>' panicked at wayland-display-core/src/lib.rs:99:41: called `Result::unwrap()` on an `Err` value: RecvError stack backtrace: 0: 0x737f300e6682 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h46a716bba2450163 1: 0x737f30106f13 - core::fmt::write::h275e5980d7008551 2: 0x737f300e38a3 - std::io::Write::write_fmt::h561a66a0340b6995 3: 0x737f300e64d2 - std::sys::backtrace::BacktraceLock::print::hafb9d5969adc39a0 4: 0x737f300e7932 - std::panicking::default_hook::{{closure}}::hae2e97a5c4b2b777 5: 0x737f300e7735 - std::panicking::default_hook::h3db1b505cfc4eb79 6: 0x737f300e82d2 - std::panicking::rust_panic_with_hook::h409da73ddef13937 7: 0x737f300e807a - std::panicking::begin_panic_handler::{{closure}}::h159b61b27f96a9c2 8: 0x737f300e6b79 - std::sys::backtrace::__rust_end_short_backtrace::h5b56844d75e766fc 9: 0x737f300e7d0d - __rustc[4794b31dd7191200]::rust_begin_unwind 10: 0x737f2fea1730 - core::panicking::panic_fmt::hc8737e8cca20a7c8 11: 0x737f2fea1af6 - core::result::unwrap_failed::h727108008d9f4c9b 12: 0x737f2fee0f95 - waylanddisplaycore::MaybeRecv<T>::get::h33a8dc3c1cb5e468 13: 0x737f2fee151a - waylanddisplaycore::WaylandDisplay::env_vars::h53b5e6549c8cbd59 14: 0x737f2fea79ef - <gstwaylanddisplaysrc::waylandsrc::imp::WaylandDisplaySrc as gstreamer_base::subclass::base_src::BaseSrcImpl>::start::h99f72592ffc14553 15: 0x737f2fea92ab - gstreamer_base::subclass::base_src::base_src_start::h14fbfb9fbecc7006 16: 0x737f3710ddea - <unknown> 17: 0x737f3710e328 - <unknown> 18: 0x737f36fdbe9d - <unknown> 19: 0x737f36fdc841 - gst_pad_set_active 20: 0x737f36fb0ec5 - <unknown> 21: 0x737f36fc8bc4 - gst_iterator_fold 22: 0x737f36fb3c01 - <unknown> 23: 0x737f3710bc4d - <unknown> 24: 0x737f2feb3d8d - gstreamer::subclass::element::element_change_state::h4a1769e7ce647991 25: 0x737f36fb6394 - gst_element_change_state 26: 0x737f36fb6982 - <unknown> 27: 0x737f36f8d112 - <unknown> 28: 0x737f36fe5eee - <unknown> 29: 0x737f36fb6394 - gst_element_change_state 30: 0x737f36fb63db - gst_element_change_state 31: 0x737f36fb6982 - <unknown> 13:00:14.525136888 DEBUG | [RTSP] found session by matching payload: 248.98.9.221 13:00:14.525170198 DEBUG | [RTSP] received command OPTIONS 32: 0x5fa0c1d943e6 - run_pipeline at /wolf/src/moonlight-server/./streaming/streaming.hpp:99:24 33: 0x5fa0c1d956cd - _ZN9streaming20start_video_producerEmRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_RKN4wolf4core15virtual_display11DisplayModeESt10shared_ptrIN5boost7promiseINS_19WaylandDisplayReadyEEEESE_IN2dp9event_busIJN5immer3boxINS9_6events15PlugDeviceEventENSM_13memory_policyINSM_21free_list_heap_policyINSM_8cpp_heapELm1024EEENSM_15refcount_policyENSM_15spinlock_policyENSM_20no_transience_policyELb0ELb1EEEEENSN_INSO_10PairSignalESX_EENSN_INSO_17UnplugDeviceEventESX_EENSN_INSO_13StreamSessionESX_EENSN_INSO_12VideoSessionESX_EENSN_INSO_12AudioSessionESX_EENSN_INSO_15IDRRequestEventESX_EENSN_INSO_16PauseStreamEventESX_EENSN_INSO_17ResumeStreamEventESX_EENSN_INSO_15StopStreamEventESX_EENSN_INSO_17RTPVideoPingEventESX_EENSN_INSO_17RTPAudioPingEventESX_EENSN_INSO_11StartRunnerESX_EEEEEE at /wolf/src/moonlight-server/streaming/streaming.cpp:88:15 13:00:14.536525227 DEBUG | [RTSP] found session by matching payload: 248.98.9.221 13:00:14.536547478 DEBUG | [RTSP] received command DESCRIBE 13:00:14.558671797 DEBUG | [RTSP] found session by matching payload: 248.98.9.221 13:00:14.558696879 DEBUG | [RTSP] received command SETUP 34: 0x5fa0c1b0875b - operator() at /wolf/src/moonlight-server/wolf.cpp:222:44 35: 0x737f368a1324 - <unknown> 36: 0x737f3650bef1 - <unknown> 37: 0x737f3659d244 - __clone 2025-07-20T13:00:14.560244Z WARN waylanddisplaycore: Failed to send stop command: sending on a closed channel 18:49:00.497587987 1 0x737e4800f090 WARN basesrc gstbasesrc.c:3616:gst_base_src_start:<wolf_wayland_source> error: Failed to start 18:49:00.497615775 1 0x737e4800f090 WARN basesrc gstbasesrc.c:3984:gst_base_src_activate_push:<wolf_wayland_source> Failed to start in push mode 18:49:00.497629331 1 0x737e4800f090 WARN GST_PADS gstpad.c:1158:gst_pad_set_active:<wolf_wayland_source:src> Failed to activate pad 18:49:00.497677557 1 0x737e4800f090 WARN bin gstbin.c:2816:reset_state:<wolf_wayland_source> Failed to switch back down to READY 13:00:14.569472244 DEBUG | [RTSP] found session by matching payload: 248.98.9.221 13:00:14.569494882 DEBUG | [RTSP] received command SETUP 13:00:14.591570058 DEBUG | [RTSP] found session by matching payload: 248.98.9.221 13:00:14.591591518 DEBUG | [RTSP] received command SETUP 13:00:14.613765857 DEBUG | [RTSP] found session by matching payload: 248.98.9.221 13:00:14.613789657 DEBUG | [RTSP] received command ANNOUNCE 13:00:14.613953001 DEBUG | [RTSP] Moonlight requested video format HEVC 13:00:14.613974775 DEBUG | [RTSP] Adjusted video bitrate to 31708 Kbps 13:00:14.624930255 DEBUG | [RTSP] found session by matching payload: 248.98.9.221 13:00:14.624952748 DEBUG | [RTSP] received command PLAY 13:00:14.630617830 DEBUG | [ENET] connected client: 192.168.1.251:12028 13:00:14.631493483 DEBUG | Starting video pipeline: interpipesrc listen-to=9755996566729338573_video is-live=true stream-sync=restart-ts max-bytes=0 max-buffers=1 leaky-type=downstream ! glupload ! glcolorconvert ! video/x-raw(memory:GLMemory),format=NV12, width=1920, height=1080, chroma-site=mpeg2, colorimetry=bt601, pixel-aspect-ratio=1/1 ! nvh265enc gop-size=-1 bitrate=31708 aud=false rc-mode=cbr zerolatency=true preset=p1 tune=ultra-low-latency multi-pass=two-pass-quarter ! h265parse ! video/x-h265, profile=main, stream-format=byte-stream ! rtpmoonlightpay_video name=moonlight_pay payload_size=1024 fec_percentage=20 min_required_fec_packets=2 ! appsink sync=false name=wolf_udp_sink 13:00:14.641355769 DEBUG | Setting up wolf_udp_sink 13:00:14.679442247 WARN | Received MOUSE_MOVE_REL_PACKET but no mouse device is present 13:00:14.689254898 WARN | Received MOUSE_MOVE_REL_PACKET but no mouse device is present libEGL warning: egl: failed to create dri2 screen 2025-07-20T13:00:14.785555Z ERROR smithay::backend::egl::ffi: [EGL] 0x3001 (NOT_INITIALIZED) eglInitialize: DRI2: failed to load driver libEGL warning: DRI2: failed to create screen MESA: error: ZINK: failed to choose pdev libEGL warning: egl: failed to create dri2 screen libEGL warning: DRI2: failed to create screen 2025-07-20T13:00:14.804442Z ERROR smithay::backend::egl::ffi: [EGL] 0x3001 (NOT_INITIALIZED) eglInitialize: DRI2: failed to load driver 13:00:14.932914794 DEBUG | [GSTREAMER] Forcing IDR 13:00:15.066165456 DEBUG | Starting audio pipeline: interpipesrc listen-to=9755996566729338573_audio is-live=true stream-sync=restart-ts max-bytes=0 max-buffers=3 block=false ! queue max-size-buffers=3 leaky=downstream ! audiorate ! audioconvert ! opusenc bitrate=96000 bitrate-type=cbr frame-size=5 bandwidth=fullband audio-type=restricted-lowdelay max-payload-size=1400 ! rtpmoonlightpay_audio name=moonlight_pay packet_duration=5 encrypt=true aes_key="51e2c797b03615dd76f5552c005dc780" aes_iv="1772640900" ! appsink name=wolf_udp_sink 13:00:15.066797566 DEBUG | Setting up wolf_udp_sink 18:49:01.676209512 1 0x737eb8001e70 WARN basesrc gstbasesrc.c:4255:gst_base_src_push_segment:<interpipesrc11> segment format mismatched, ignore 13:00:20.390757073 WARN | Received MOUSE_MOVE_REL_PACKET but no mouse device is present 13:00:25.285264368 DEBUG | [ENET] disconnected client: 192.168.1.251:12028 13:00:25.285310249 DEBUG | [GSTREAMER] Pausing pipeline: 9755996566729338573 13:00:25.285338212 DEBUG | [GSTREAMER] Pausing pipeline: 9755996566729338573 13:00:25.289495722 DEBUG | 192.168.1.251 [GET] HTTP://192.168.1.11/serverinfo 13:00:25.321505931 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/serverinfo 13:00:25.355173269 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/applist 13:00:28.498334290 DEBUG | 192.168.1.251 [GET] HTTP://192.168.1.11/serverinfo 13:00:28.527533637 DEBUG | 192.168.1.251 [GET] HTTPS://192.168.1.11/serverinfo ``` Since I don't find how to fix this I went for the nvidia manual solution with the nvidia-driver-volume. I now can access at least Firefox

bsakaguchi commented

Author

Owner

@ABeltramo commented on GitHub (Jul 20, 2025):

So I guess given this you are now able to stream, only Steam is failing to run. Can you post the full logs instead of just chunks of it?

@ABeltramo commented on GitHub (Jul 20, 2025): So I guess [given this](https://github.com/games-on-whales/wolf/issues/152#issuecomment-3094575055 ) you are now able to stream, only Steam is failing to run. Can you post the full logs instead of just chunks of it?

bsakaguchi commented