#Jitsi meet custom ui code#

I'm no pro, but here's how I'm doing updates. As soon as I removed the extension ID from the config.js file and restarted the container I'm back to a working setup. There's no way that I could find to tell Chrome to force allow an unpublished extension. I was experimenting with making my own Jitsi Chrome extension and stopped when it required to publish to the store.

#Jitsi meet custom ui code#

js : 1868 ) DevTools failed to load SourceMap : Could not load content for chrome - extension : //hdokiejnpimakedhajhdlcegeplioahd/sourcemaps/onloadwff.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME js : 22 Uncaught TypeError : Cannot read property 'defaultLanguage' of undefinedĪt Object. js : 18 Uncaught TypeError : Cannot read property 'tokenAuthUrl' of undefinedĪt Object. html loaded : 510.44999999976426 ( index ): 298 Uncaught ReferenceError : kecohalednmcpjceagiapnnpmdnpbagc is not definedĪt ( index ): 298 Logger. Any clues? Heres the javascript console log: I've tried restarting the stack but no changes. After a server restart when I now try to access the Jitsi web UI I get a dark gray blank page. I got video calls working from multiple devices just fine. I followed the guide and got everything working perfectly. Nginx: host not found in upstream 'meet.jitsi' in /config/nginx/proxy-confs/:17 ssl' directive in /config/nginx/proxy-confs/:3 Edited Apby adambeck7 Nginx: no 'ssl_certificate' is defined for the 'listen. ssl' directive in /config/nginx/proxy-confs/:3

Letting the cron script handle the renewal attempts overnight (2:08am). The cert does not expire within the next day. Sub-domains processed are: -d server.domain -d nextcloud.domain -d climadb.domain -d meet.domain -d jitsi.domainĬertificate exists parameters unchanged starting nginx If I add it, it appears to load correctly but none of my subdomains work. Thanks for this! It seems I'm having an issue w/ the jitsi conf file you provided. Somewhat defeats the purpose if I can't join meetings from my local network. env, I tried updating the STUN server to a google one as my friend did, I tried updating the sip-communicator.properties as per this link, and so far nothing has worked to allow me to join a meeting with more than 2 people from my local network. I tried updating the DOCKER_HOST_ADDRESS to my WAN IP in. I've done some googling and troubleshooting with a friend and we haven't been able to resolve the issue. Checks failed but the remote end was able to reach us.', and a few others. I've checked my jvb docker logs and there's a lot of errors about 'INFO: ICE state is FAILED', 'INFO: Suspicious ICE connectivity failure. If I connect from outside of my local network, I can join the meeting. As soon as a third user connects, video and audio stop for me, but the rest of the users in the meeting are still able to chat.

I am however having issues with meetings with more than 2 users when I'm connected from my LAN. This is awesome and I'm super glad you got around to creating this video for everyone.