Open apodosis opened 3 years ago
Hi,
Do you see any errors in the server logs? I suspect that it doesn't get connected to mongodb.
I'm not certain what logs you're referring to. Is there a specific place that the server writes logs to?
When I run npm start inside the server folder I get the following
I can confirm that the containers seem to be working
On looking into this a bit more I see the .env template has the DB under mongodb listed as "test" whereas the docker compose file as the INITDB listed as "nettu-meeting".
I wasn't sure if this was a concern so I changed it to nettu-meeting in the .env file and repeated the install process. I verified inside the mongo container that the db was created under the nettu-meeting name and has four collections viz., accounts, canvas, chats and meetings.
Unfortunately, I'm still getting the same error.
Thanks for all the details.
I was thinking about the node.js
server logs, which you start when you type npm run start
. From your screenshot it looks like it start up fine, but if that are all the logs from the server then I suspect it doesn`t get the requests from the frontend.
Please check if you have configured your frontend react app to point to the correct server url.
if that is configured correctly, please check what error logs your network tab in the browser gives you.
I've pointed every possible localhost
mention to my IP address.
The logs on the server side do show requests coming from the frontend, visible in the picture below(I've greyed out my IP address)
Here is the error I'm getting in the console on the browser.
The network tab shows no errors
It seems like the mediasoup-client
library doesn't like your device. Here is a link to the error thrown.
What OS are you running?
hi same issue im using ubuntu 16.04 server client mac os 11.4 chrome 91.0.4472.114 and safari 14.1.1(16611.2.7.1.4)
Your browser is not supported [deviceInfo:"Objectbrowser: e {_ua: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) Ap…L, like Gecko) Chrome/91.0.4472.114 Safari/537.36", parsedResult: {…}}flag: "chrome"name: "chrome"os: "macos"platform: "desktop"version: "91.0.4472.114"__proto__: constructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()__defineGetter__: ƒ __defineGetter__()__defineSetter__: ƒ __defineSetter__()__lookupGetter__: ƒ __lookupGetter__()__lookupSetter__: ƒ __lookupSetter__()get __proto__: ƒ __proto__()set __proto__: ƒ __proto__()"] (anonymous) @ EntryPage.tsx:142
Hi,
I've followed your instructions but I'm running it on a remote server to test. I added my remote IP to the .env variable. I haven't had issues with the installation but the frontend compiles with some eslint warnings and the meeting URL shows a Browser not supported message across Chrome, Edge and Firefox
Chrome (Version 91.0.4472.106) Firefox (Version 89.0.1) Edge (Version 91.0.864.54)
Is there anything else that needs to be done when hosting on an instance that I may have missed?
Here are the eslint warnings if thats of any use.
Thanks for all the help in advance.