Jigasi doesn't work - certificates #88
Comments
|
Hi @saschafoerster, |
|
I checked out the "dev" version via git. Here are the results from the logs (it still doesn't work as it should): From Jigasi: The last line keeps repeating. JVB_1 Jicovo: |
|
Did you re-cteate containers after made pull from dev? like |
|
I have the same problem
|
|
I just realised that even though I did Waiting for the images to be built now... |
I tried this and --force-recreate, but it didn't work, but it didn't work because docker-compose.yml is pointing at the DockerFiles on Docker Hub, created 2 months ago, not to the DockerFiles in the repo. |
|
OK, so here are the things that I did to get outbound calling to work:
After that, I was able to enter a conference, log in as the host, and add my phone number (I used international format without the TODO:
|
Those values are already there: https://github.com/jitsi/docker-jitsi-meet/blob/dev/env.example#L140 are you suere you checked the right branch?
You don't need to do this. You can build the images locally by just running
You shouldn't need to do this. Have you uncommented these options? https://github.com/jitsi/docker-jitsi-meet/blob/dev/env.example#L199 |
Oops. I was initially using the
Thanks! I didn't know I could do that.
Sorry, I should have clearer: the register command above was to create an account that I could use to log in as a moderator on the web UI (I set The Thanks so much for the fast reply and clarification of what I did wrong :) |
Ah gotcha. You're correct, those lines will create an account for jigasi to use. |
|
It looks your issue was the same as mine. If you were trying to run the |
|
I'm going to tentatively close this, please holler if we need to reopen. |
|
Outbound calls are working for me now, just there is no sound, but this seems like a new topic. Thanks for your help! |
hi,I'm trying to use jitsi for my demo,I have the same problem above.I follow the steps above.prosody run well,Problems in the log disappear.Other modules still have problems, the log is as follows jvb jigasi
I noticed that the configuration directory permissions were inconsistent,Does it matter?
I'm new to jitsi,Your help is badly needed,thanks a lot |
Your permissions look the same as mine. On my system (for which outbound calling works), all the directories within ~/.jitsi-meet-config are owned by root, except for It's worth running |
I'm using a mirror built from the latest dev branch,The image should be up to date.Does your jigasi log also show generic errors? |
|
Yes, I still see generic errors, but they don't seem to be causing any problem. jvb: jigasi: |
Hi How do I run the built images with docker compose after "make"? I am trying to run the dev branch thanks |
What could I do, if my server (Synology) doesn't support "make" in terminal? |
|
You can just look at the makefile and run the commands by hand. |
|
Does anybody know where is conferenceMapper located for docker? How to enable it? |
I am running docker-jitsi-meet with the jigasi extension on a Synology.
Everything works, but Jigasi. I can see the +-sign and type in a number, but no call is made, instead an error message appears.
I can't use Let's Encrypt on the Synology in the container, because everything has to be forwarded by a nginx proxy, which causes the let's encrypt certificate creation to fail.
The proxy itself knows already the certificate and encrypts on the frontend. I proxy this traffic back to the probably selfsigned jitsi-port 8443 in docker.
When I read the docker logs for jigasi, I found 4 error messages:
I followed the last one and looked into the logs of prosody:
Some help would be greatly appreciated.
The text was updated successfully, but these errors were encountered: