Skip to content
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

Open
apodosis opened this issue Jun 19, 2021 · 7 comments
Open

Comments

@apodosis
Copy link

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.

image

Thanks for all the help in advance.

@fmeringdal
Copy link
Owner

Hi,

Do you see any errors in the server logs? I suspect that it doesn't get connected to mongodb.

@apodosis
Copy link
Author

apodosis commented Jun 19, 2021

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

image

I can confirm that the containers seem to be working

image

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".

image

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.

@fmeringdal
Copy link
Owner

fmeringdal commented Jun 19, 2021

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.

@apodosis
Copy link
Author

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)

image

Here is the error I'm getting in the console on the browser.

image

The network tab shows no errors

image

@fmeringdal
Copy link
Owner

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?

@waterdrw
Copy link

waterdrw commented Jul 3, 2021

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)

@waterdrw
Copy link

waterdrw commented Jul 3, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants