-
Notifications
You must be signed in to change notification settings - Fork 301
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
Browser is not supported message coming across Chrome, Firefox and Edge #17
Comments
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 if that is configured correctly, please check what error logs your network tab in the browser gives you. |
It seems like the |
hi same issue |
|
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.
The text was updated successfully, but these errors were encountered: