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

New Setup on Hetzner VM: client is not using websocket protocol #300

Closed ralfi closed 1 year ago

ralfi commented 1 year ago

Hi,

based on my complete working install on my home server i try to setup a new install via Hetzner VM. Same Debian install, same Docker, same Apache Version and Reverse Proxy setup

But at the hetzner this error appears

image

Apache proxy and wstunnel modules are enabled. How can i debug further?

yesBad commented 1 year ago

This could have a bit of help (mostly the 3 commands (probably?)) https://stackoverflow.com/a/27534443/16519490

I didn't know people still use Apache for whatever reason....

ralfi commented 1 year ago

Oh, its historic ;-) you know. BTW i will change this to Nginx and try again.

yesBad commented 1 year ago

Before you even ask, here's working NGINX config for neko: https://ili.cx/t/nekonginx

m1k1o commented 1 year ago

Here is default config for apache: https://neko.m1k1o.net/#/getting-started/reverse-proxy?id=apache

yesBad commented 1 year ago

Here is default config for apache: neko.m1k1o.net/#/getting-started/reverse-proxy?id=apache

Forgot these existed 👍

ralfi commented 1 year ago

Everything works now (with apache) after changing SHM_SIZE related to VM RAM size, checking UDP traffic works and do NOT exposing UDP traffic via docker-compose.yaml because it's not needed, all checks with firefox:latest image.