step by step? #2
Comments
|
I couldn't find any, but it worked out pretty simple ..
Note because of Chromium's (and Chrome's) security you still need to manually install the extension or work on getting it added to the Chrome Store (which we haven't done). |
|
Thank you for that, I have never put a chrome extenstion up in the store before. I do have one question though In the manifest.json file Where we edit the url filter I use a port at the end of my url Will this match still work "externally_connectable": { I've tried some other varations and it showed errors. |
|
Try this as your match ... Not sure about the port, my initial guess would be not needed. Try it without the port, if that doesn't work then try it with the port, if that still doesn't work then get rid of the idea of using a non-standard port ;). Would probably need to be this match if you needed the port. |
|
That was the first thing I tried. I just left the office may mess around with it remotely later or just pick it up in the AM Also note: their are asterix's in their not sure but think github pulled them out "asterix://hangout.extention.net:44300/asterix" |
|
ahh .. ok yeah |
|
Basically, Whne sing the following "asterix://hangout.extention.net/asterix" I created the CRX file. I get an error saying apps. Extensions, and user scripts cannot be added from this website. So i'm at a loss for tonight. Thanks for checking back and the fast replies |
|
Drag and drop directly into chrome://extensions/ |
|
well that cleared that up.. Still have to mess with that port and try to get it to work right tomarrow. |
|
ok, Here is the error while trying to Pack. Pack Extension Error |
|
FYI it removed the asterix's again seems github comments don't like them "asterix://hangout.extention.net:44300/asterix" |
|
yeap .. try without port :44300 |
|
Ok, seems it will compile the extension without the first asterix ie.. "https://hangout.extention.net:44300/asterix" With that being said drag and drop the extension to chrome extensions install fine. Error FYI: just tried without the 44300 as well compiles but get same error when I goto the website |
|
go to https://hangout.extention.net:44300/channel .. httpS as you have in your extension |
|
Sorry that was a type O I was going to https: |
|
So the failed to install the desktop sharing extension message is because it can't find an enabled extension to install for the jitsi meet server. Which would mean that the extension either not configured correctly for the correct server, not enabled or 'something else'. |
|
not much just the name and the verison number { |
|
The server can be reached at https://hangout.lifewithtech.net:44300/ |
|
ok, so I had a play and not having much luck, changed the match and was working with reloading the unpacked extension .. even tried asterisk:hangout.lifewithtech.net:asterisk/asterisk. I think the next step is to tail the logs on the server to see if there is anything that is obviously failing. sudo -s note depending on your installation logs maybe in different locations. |
|
OK did a tail, while open I did this is the output of the tail. root@hangout:/var/log/jitsi# tail -f /var/log/nginx/error.log /var/log/jitsi/jicofo.log ==> /var/log/jitsi/jicofo.log <== |
|
@ibeardslee |
|
Error "SASL authentication DIGEST-MD5 failed: text:" means that invalid password is configured for jicofo user. |
|
@paweldomas |
|
@paweldomas |
|
Reiterate configuration(etc\prosody\prosody.cfg.lua): VirtualHost "auth.jitsi.example.com" sudo prosodyctl register focus auth.jitsi.example.com focuspassword admins = { [email protected] } Component "focus.jitsi.exmaple.com" You can see I got a bit confused and decided to go back to defaults in order to limit and evaluate the other issues I was having like port fowarding and subdomains and it has gone full circle. |
|
Hey, configuration(etc\prosody\prosody.cfg.lua): VirtualHost "auth.hangout.lifewithtech.net" sudo prosodyctl register [email protected] focuspassword admins = { [email protected] } Component "focus.hangout.lifewithtech.net" Hope this helps ! |
|
Thank you for helping out with this. I made the changes in the config When running sudo prosodyctl register [email protected] focuspassword I put in a new password, then retype password Terminal output.thomasfraley@hangout: |
|
Sorry it should be: You can also check prosodyctl help and see what are other options for adding user and modifying passwords. |
|
Ok, so here is the new tail output. ScreenSharing still not working.. Reciving the same error in chrome "Failed to install desktop sharing extension" FYI:I do have my extention in the googlechrome store as well thomasfraley@hangout:~$ sudo su ==> /var/log/jitsi/jicofo.log <== |
|
Hi @tfraley and installed the extension. But no luck |
|
Did you update config.js in Jitsi Meet with the ID of your extension? |
|
@individual-it |
|
I got ours working no problem. The last step is to place the extension ID in |
|
Thanks everyone. After reading all the above. I was able to sort my ext too. Note for newbees: Your chrome extension ID is generated when you publish your ext. Once you publish your extension. You can get the ID from the URL. Copy that and then go to /etc/jitsi/meet/{domain}-config.js and paste it
|
|
Now any tips to get Firefox Extension Published. I generated mine and when I drag the xpi to Firefox, it says 'Ext is corrupted' |
|
Thanks for this article. However I entered my id by Googles Web Store but it's still not working, the extension is not provided for installation. If I install it manually, desktop sharing works, so it seems, the ID is not recognized. However, I entered it as given and checked it multiple times. I just encountered, there seems to have been an update on the parameter name for the id, for me it's desktopSharingChromeExtId instead of chromeExtensionId as been found on google. |
|
Thanks to Boris from the dev team, here is the missing hint (BTW my used ID setting is the right one, the other parameter name is outdated): The extension in the Google Web Store needs to be assigned to a verified domain, which must be the verified site running Jitsi Meet (if it should not get indexed, a robots.txt file is required). So using this explanation http://stackoverflow.com/questions/25920728/how-to-specify-verified-site-to-a-chrome-app will finally let the extension be recommended to be installed, if missing and then allows desktop sharing functionality. Ticket can be closed again. |
for a custom site. Source: jitsi#2
…r a custom site. Source: jitsi#2
…r a custom site. Source: jitsi#2
|
Could somebody please tell me where I got it wrong? I'm pretty sure I followed all the instructions. I even restarted the server and I also cleared the cookies and cache in my browser. Thank you! |
|
Looks right to me, @Ham-Radio . I remember picking up an extension reloader while working on mine and faced with a similar situation. I also closed all the chromes. |
Any step by step docs to get this going?
The text was updated successfully, but these errors were encountered: