You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cant get screego to work without network_mode: host #226
you are using https to access Screego.
yep with nginx proxy manager
SCREEGO_EXTERNAL_IP is set to your external IP. See Configuration
yep public ip off the vps
you are using TURN for NAT-Traversal. See NAT-Traversal. This isn’t allowed for app.screego.net, you’ve to self-host Screego
logs show: INF Start TURN/STUN addr=0.0.0.0:3478 so that looks fine to me (web ui only shows stun though I would expect it to list TURN
your browser doesn’t block WebRTC (extensions or other settings)
yep, ex: The public demo & on devices on the same network work
you have opened ports in your firewall. By default 5050, 3478 and any UDP port when using TURN.
yep
there are probs some unnecessary settings in here but this is the point where I gave up.
extra background.
I'm using nginx proxy manager as my reverse proxy.
Container is running on a vps.
Stream works with 2 devices on my home network, But not with devices on different networks.
which to me hints towards the TURN/STUN magic.
The ui shows Nat Traversal via: STUN before joining a room.
I've turned on debug logging but saw no errors.
I feel I'm missing something obvious here.
anybody any suggestions?
The ui shows Nat Traversal via: STUN before joining a room
This means you aren't using turn. You either have to provide a users file via SCREEGO_USERS_FILE and login or use a SCREEGO_AUTH_MODE=none to disable authentication.
Yes, sharing works on same device(incognito window browser) and on 2 devices (pc & phone) on same network
sidenote: dont think it matters much but my screego instance is hosted on a vps
Hmm, this looks okay'ish, the ICE responses look suspicious as the clients don't announce their ip address only some uuid.local address. There should be something like this:
2025-06-20T19:08:54+02:00 DBG WebSocket Receive event=*ws.ClientICE id=d1apb3j5ddu941gv4r90 ip=::1 payload={"sid":"d1apb9j5ddu941gv4rag","value":{"candidate":"candidate:3975234324 1 udp 1677729535 192.168.178.2 56344 typ srflx raddr 0.0.0.0 rport 0 generation 0 ufrag cOgG network-cost 999","sdpMLineIndex":0,"sdpMid":"0","usernameFragment":"cOgG"}}
^^^^ see this local ip
But TURN should work regardless. "TURN authenticated" does happen so both clients reach the TURN server. Which clients are you using and what kind of network are they using? (Mobile & wifi?)
Could you check
if it works when you specify network_mode: host in your docker-compose.yml
if there are any errors logged in the browser console on either client when the sharing fails
Open two tabs on the same client with http://app.screego.net/?room=myname&forceTurn=true (replace the domain with your server) and check if the screensharing works. This internally forces the usage of turn.
Clients I use:
My desktop (wired)
My phone (wireless)
A chromium instance on a kasm server on a remote site a few 100Km away (wired)
when using app.screego.net these 3 work perfectly
atm network_mode: host makes my Nginx not work (I'll look further into it)
But I can add that i noticed this error in the browser console off the client that should see the video feed.
Doesnt show up all the time, and the forceTurn=true setting has no influence Could not play main video DOMException: The play() request was interrupted because the media was removed from the document. https://goo.gl/LdLk22
after some extra testing i get the same log message on app.screego.net
So no behaviour changes when using forceTurn=true or not.
After messing around with making Nginx work with network_mode: host this seemed to have "fixed" the problem.
But for me that makes it more confusing on why it doesn't work with the normal network_mode.
So no behaviour changes when using forceTurn=true or not.
Have you checked this on devices that previously worked? I'd expect this would break.
I'm able to reproduce your problem when not using network_mode: host and having two browser windows open on the same device both having an url with forceTurn=true. When using the docker-compose from the server locally, it does work fine.
Without network_mode: host, docker proxies the traffic to the container traffic via a binary called docker-proxy. I'd guess this breaks something, but this requires further debugging which will take some time. In the meantime I'll add to the docs that screego may not work without network_mode: host.
Activity
jmattheis commentedon Jun 14, 2025
This means you aren't using turn. You either have to provide a users file via SCREEGO_USERS_FILE and login or use a SCREEGO_AUTH_MODE=none to disable authentication.
nware-lab commentedon Jun 14, 2025
Yep
SCREEGO_AUTH_MODE=nonewas the fix.Looking at the docs its clearly stated that that was a requirement.
My bad.
Love the software, simple and it just works! (if you can read the documentation)
nware-lab commentedon Jun 15, 2025
I'm now very confused.
I try to screenshare today and I have the same behaviour as before.
my config is
any more suggestions ?
ui now shows
Nat Traversal via: TURNthoughjmattheis commentedon Jun 16, 2025
nware-lab commentedon Jun 18, 2025
sidenote: dont think it matters much but my screego instance is hosted on a vps
jmattheis commentedon Jun 20, 2025
Hmm, this looks okay'ish, the ICE responses look suspicious as the clients don't announce their ip address only some uuid.local address. There should be something like this:
But TURN should work regardless. "TURN authenticated" does happen so both clients reach the TURN server. Which clients are you using and what kind of network are they using? (Mobile & wifi?)
Could you check
network_mode: hostin your docker-compose.ymlnware-lab commentedon Jun 22, 2025
Clients I use:
My desktop (wired)
My phone (wireless)
A chromium instance on a kasm server on a remote site a few 100Km away (wired)
when using app.screego.net these 3 work perfectly
atm
network_mode: hostmakes my Nginx not work (I'll look further into it)But I can add that i noticed this error in the browser console off the client that should see the video feed.
Doesnt show up all the time, and the
forceTurn=truesetting has no influenceCould not play main video DOMException: The play() request was interrupted because the media was removed from the document. https://goo.gl/LdLk22after some extra testing i get the same log message on app.screego.net
So no behaviour changes when using
forceTurn=trueor not.After messing around with making Nginx work with
network_mode: hostthis seemed to have "fixed" the problem.But for me that makes it more confusing on why it doesn't work with the normal network_mode.
jmattheis commentedon Jun 24, 2025
Have you checked this on devices that previously worked? I'd expect this would break.
I'm able to reproduce your problem when not using
network_mode: hostand having two browser windows open on the same device both having an url with forceTurn=true. When using the docker-compose from the server locally, it does work fine.Without network_mode: host, docker proxies the traffic to the container traffic via a binary called docker-proxy. I'd guess this breaks something, but this requires further debugging which will take some time. In the meantime I'll add to the docs that screego may not work without network_mode: host.
[-]Cant get screego to work[/-][+]Cant get screego to work without network_mode: host[/+]dongdigua commentedon May 18, 2026
forceTurn=trueis not documented? it only appears once at https://github.com/screego/server/blame/f946cee83b61d9f47c2f1c2238fb31f4042b628a/ui/src/useRoom.ts#L40jmattheis commentedon May 18, 2026
@dongdigua yes, it's a internal flag for troubleshooting / testing.
feat(deploy): host screego behind basic auth