Do you have a question that is not addressed by this FAQ? Consider posting your question on our discussion board.

Q: I cannot open the page of the hub. It just shows a blank screen or says the site does not exist
A: Make sure the url is exactly like printed in the console (including the port number i.e. 8080). Make sure to use https:// when HTTPS is enabled and http:// when its disabled.

Q: I can load the hub in the browser using localhost, but not when trying from a different computer.
A: This means accessing the website from the internet is not setup (correctly). Have a look at the hosting guide.

Q: When opening the url of the hub, there is a scary warning. Why is that?
A: This happens when using self-signed certificates. You need to click "accept the risk" to access the page. Note: Make sure to only use self-signed certificates using development/testing. If you want to deploy the hub you should not use them.

Q: The page loads, but I cannot see any session. Also other people can click the invite link, but they never connect successfully.
A: This means that no connection to the backend can be established. A few issues can cause this. First this may be caused by network issues, so try to open the page on the same computer the hub is running. If this works keep reading the answer of the next question. Second, if the backend is served separately, go to the url the backend prints to the console and also click "accept the risk". Then try to load the page of the hub again.

Q: I can connect to the backend using localhost, but not when trying from a different computer.
A: This means that WebRTC cannot establish the connection. Make sure you have entered ICE servers in the .env file. If it still doesn't work make sure to also add TURN servers, as for some network configurations STUN servers will not work.

Q: I want to test the hub out with multiple computers in the same local network, but I cannot access the page.
A: Make sure to change the host in backend/config.json to your local ip address. If you serve the frontend separately, then also change the REACT_APP_BACKEND in frontend/.env.

Q: The hub cannot access my camera, even though all privacy settings are correct.
A: This can be caused by not using HTTPS. Make sure you enable it in backend/config.json (and frontend/.env)

Q: I enabled HTTPS, but now when starting the hub I get the following error: Failed to start hub. Error: Did not find ssl_cert file
A: This means that the hub cannot find the SSL certificate at the location specified in backend/.json. Either put a trusted certificate at the specified location or generate a self-signed one.