-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
any chance for windows? #8
Comments
That's odd, can you check in your browser console if navigator.getUserMedia was available? The MDN docs was recommend to use this, except it wouldn't exist if the firefox browser was too old. And also, you need to use https protocol if you're not testing with localhost domain or |
well the error was from the browser console, what other info would you need? i tested it also on linux, and there it works fine - thats why i mention windows on the title. i am quite new to npm, how can i start the server with https? |
You could use Nginx's proxy_pass while using your domain SSL or Apache's reverse proxy. If you only using NodeJS for your server, you can use https module or combine it with express. If you're using Serberries you will need to modify the server example var https = require("https");
var config = {
key: fs.readFileSync(/* private key path */),
cert: fs.readFileSync(/* fullchain path */)
};
// var myserver = new Serberries(...);
myserver.server = https.createServer(config, myserver.onRequest);
// This located on the bottom of server example
myserver.start(443); |
hi,
running the server on my linux machine,
accessing the example/streamingtest server on my windows machine on the same network,
but getting
after clicking on presenter. (using Firefox btw)
Any idea?
The text was updated successfully, but these errors were encountered: