search

m1k1o / neko

A self hosted virtual browser that runs in docker and uses WebRTC.
https://neko.m1k1o.net/
Apache License 2.0
5.95k stars 449 forks source link

Using reverse proxy #330

Closed robertowilliamsep closed 3 months ago

robertowilliamsep commented 10 months ago

Hi Everyone,

I'm testing Neko behind a reverse proxy setup. While I can access the login, I'm encountering issues with TURN/COTURN functionality and have failed to connect. Does anyone have comprehensive guides or tutorials that could help with this issue? Is there a limitation?

Thanks, Roberto

m1k1o commented 9 months ago

There is not much in docs about this, but if you would be open to share your findings/problems with us, we could help you and based on our findings create docs page for further users.

ralfi commented 9 months ago

ksnip_20230913-132711

This is my apache reverse proxy config part and this

ksnip_20230913-132702

is the part of my docker-compose yaml for Neko.

I only use provider based virtual machines (Hetzner, ...) as TURN Server. Based on my experience, using Neko is only meaningful with GPU-supported hardware, as stated in the Nvidia guide part of Neko.

BTW Neko works only with plain user=mycoturn:mycoturnsecret authentication, not with lt-cred-mech in your turnserver.conf nor other athenticate mech'.

robertowilliams commented 9 months ago

There is not much in docs about this, but if you would be open to share your findings/problems with us, we could help you and based on our findings create docs page for further users.

Thanks.

m1k1o commented 3 months ago

Added coturn deployment example to docs: https://neko.m1k1o.net/#/getting-started/?id=networking