Closed itsallinyourhead closed 1 year ago
Moin Moin.
Please get started here https://github.com/holtwick/briefing/blob/master/docs/installation/README.md
There are some services like STUN and the signaling via Websocket, that might need special configurations. You may also use those of Briefing in the beginning and start using your own step by step then.
UPD sounds like the actual WebRTC connection. Taht should usually not go to the server, except for TURN. See docs for details.
It works correctly with nginx now. Looks similar to your domain. If anyone is interested:
server { listen [::]:443 http2 ssl; listen 443 http2 ssl; server_name briefing.example.com; ssl_certificate ../certs/chained.pem; ssl_certificate_key ../certs/private.pem; ssl_stapling_file ../certs/stapling.pem; location ~^/(favicon\.ico|robots\.txt|serviceWorker\.js)$ { try_files /$uri =444; } location ~^/(css|js|pics)/ { try_files /$uri =444; } location ~^/([a-z]+\-[a-z]+\-[0-9]+|)$ { access_log logs/briefing.example.com https; error_log logs/error; expires 0; try_files /$uri /index.html =444; } location /zerva-websocket { proxy_http_version 1.1; proxy_pass http://LOCAL_IP_ADDRESS:8080; proxy_set_header Connection "upgrade"; proxy_set_header Host $http_host; proxy_set_header Upgrade $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } root /usr/local/briefing/www; }
git clone https://github.com/holtwick/briefing.git cd briefing npm install npm run build npm start
Grüß Gott.
After adding
to nginx configuration file and running
briefing.example.com is reachable with a browser and looks similar to https://brie.fi/ng. But briefing.example.com generates more than 70 requests without user interaction while https://brie.fi/ng only generates 8 requests. Also briefing.example.com repeatedly tries to to reach briefing.example.com:24678 (which permamently fails) while https://brie.fi/ng does not try reach port 24678.
Port 24678 is listening only for IPv6, not IPv4.
What have I done wrong?