search

Johni0702 / mumble-web

An HTML5 Mumble client
679 stars 151 forks source link

Can a docker image or something be made? #4

Open tdrone993 opened 7 years ago

tdrone993 commented 7 years ago

root@tango:~# websockify --cert=/etc/letsencrypt/keys/cert.pem --key=/etc/letsencrypt/keys/key.pem --ssl-only --ssl-target --web=/usr/local/lib/node_modules/mumble-web/dist 443 127.0.0.1:64738` root@tango:~# yields nothing. 14.04.05 x64

tdrone993 commented 7 years ago

went the nginx route following your config with my site also websockify --ssl-target 64737 myip:64738 [12:11:01 PM] Connecting to server ip [12:11:01 PM] Connection error: [object Event] address my mumble server port 443 "blank" user

Johni0702 commented 7 years ago

There's little point in creating a docker image as there are already plenty images for websockify.

Your description of what you were doing / what happened is incomprehensible. Your first command seems to be correct. As for the connection error, have a look into the JS console of your browsers, it should contain more information.

SISheogorath commented 7 years ago

I currently provide one based on fork of this repository: https://hub.docker.com/r/sheogorath/mumble-web/

Dockefile

And also provide it with a murmur and web socket https://github.com/SISheogorath/infrastructure/blob/29b0aaca86592e3dfefa47de4309d6f6a7d545f8/roles/mumble/templates/docker-compose.yml

Notice: Right now it only works when you NOT use Traefik in front because I have to figure out how to use web sockets with Traefik. Use and reverse proxy like Nginx instead.

gettyhub commented 6 years ago

Web sockify complains about there not being a self.pem file in the build(?) directory? I make a self made ssl certificate with openssl and it then complains about an ssl error. This is related to the object Event (Event not being told what the error is). Then I connect to a public Mumble server, get one try at the voice and then the whole connection dies within mumble-web.
It doesn't seem to want to connect to local private IPs, but will tempormentally connect to public servers. Maybe it's a problem with my local ssl certificate.
Other problems exist with less supported browsers: Cannot initialize user media. Microphone will not work: NotSupportedError: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).

chasgames commented 6 years ago

Great! :)

cdauth commented 6 years ago

I’m working on a docker image for mumble-web that has websockify included, running under the same address: rankenstein/mumble-web