Connection failed in webrtc

[zeyugao]

I have no idea what's wrong. I can connect to webrtc but not the vnc

Run with command (from ReadMe):

docker run --gpus 1 -it -e TZ=UTC -e SIZEW=1920 -e SIZEH=1080 -e REFRESH=60 -e DPI=96 -e CDEPTH=24 -e VIDEO_PORT=DFP -e PASSWD=mypasswd -e WEBRTC_ENCODER=nvh264enc -e BASIC_AUTH_PASSWORD=mypasswd -p 127.0.0.1:8080:8080 ghcr.io/ehfd/nvidia-glx-desktop:latest

GPU is v100
Here are the logs
Some ERRORs are in entrypoint.log but I cannot determine which one is critical

entrypoint-stdout---supervisor-bgokahf1.log
supervisord.log
Xorg.0.log
selkies-gstreamer-stdout---supervisor-8u_8ckmh.log

[ehfd]

Use --net=host in docker run or uncomment network_mode: 'host' in Docker-Compose!!!

Use hostNetwork: true or a TURN server for Kubernetes!!!

[zeyugao]

I wait for a while and retry. Here are the logs.
It seems that selkies-gstreamer's log is not empty.
The process list is in ps.txt

selkies-gstreamer-stdout---supervisor-5cd_gmr9.log
supervisord.log
entrypoint-stdout---supervisor-bt8d_pdm.log
ps.txt

And two errors in web console for webrtc. I am using ssh port forwarding -N -L 18080:127.0.0.1:8080

[ehfd]

Sorry for the late reply. It seems that your selkies-gstreamer-stdout---supervisor-8u_8ckmh.log is empty other than confirmation that the X server started. The rest are okay. I would have given you prompt assistance if selkies-gstreamer-stdout---supervisor-8u_8ckmh.log had an error log, but since there is nothing in that log file, I would have to determine that selkies-gstreamer hadn't started at all. Could you reproduce everything after waiting sufficiently everything inside the container to start and use htop to check which processes are started and which are not?

This is a case where you have to read Using a TURN Server, since I think you are sshing to a remote server with NAT. Please either use a public TURN instance or your own coTURN server for relaying the stream. Since selkies-gstreamer uses WebRTC, there is no workaround for this until WebTransport is a recognized standard for all web browsers.

[ehfd]

One more further note, this issue has a workaround by adding --net=host to the docker run command. For Kubernetes, add hostNetwork: true to the pod spec yaml file. This documentation will be updated to the README.md file with other updates.

[ehfd]

One more further note, this issue has a workaround by adding --net=host to the docker run command. For Kubernetes, add hostNetwork: true to the pod spec yaml file. This documentation will be updated to the README.md file with other updates.

Documentation added in commit aac2c25.

[ehfd]

More documentation added to Using a TURN Server.