We had set up a JITSI server on our AWS account on an ECS service with an open-source container image.
There are 5 containers running (web, prosody, jicofo, jibril, jvb). image version: stable-7439
We want to integrate a calendar service in Jitsi; I follow this step. issue (we can not sign in google calender)
- change ENABLE_CALENDAR to true in the web container.
- change GOOGLE_API_APP_CLIENT_ID to our google API client id.
- restart all containers.
- so we can show the following changes in config.js
// Calendar service integration.
config.enableCalendarIntegration = true;
config.googleApiApplicationClientID = <out_client_id>;
// Invitation service.
now we can see the calendar icon in our hosted server.
But when we click on sign in, nothing happens; we cannot log in to Google.
When we clicked on the Sign with Google button, as shown in the above image, the browser returned a status code of 200.
Help: Can anyone suggest why nothing happens when we click on the “sign with Google” tab?
What steps do we have to follow?
Yes I have followed this step.
When setting it there is a domain/url the enter is that valid and the domain where your deployment is?
Yes, it’s valid domain.
Our domain is hosted on godaddy and our server is deployed on AWS on ECS cluster.
No, what do you have in the dashboard when setting up the Google api id, is it the correct domain?
Our main domain is xyz.com and our server is running on jitsi.xyz.com,
There is required to put domain while creating Google api id , so i entered https://jitsi.xyz.com
So according to you what is valid domain?
Does jitsi.xyz.com not valid domain?
That … Hum not sure what is going on.
I read all articles and documents and apply above changes but nothing happen when i click on Google sign.
Does there is need to install additional software in container?
Can you provide any suggestions that I have to follow…
No errors in the js console?
In js console there is error like below.
Not a valid origin for the client: https://jitsi.xyz.com has not been registered for client ID <our_client_id>.
Our server is running on : jitsi.xyz.com
then what is valid origin in client id?
I am using docker jitsi meet GitHub repo: release stable-7439. As mentioned in repo.
Then what do I have to update?
I was doing configuration change in JITSI MEET by env file…
I’m using the latest deb stable/jitsi-meet_8138 on Ubuntu 22.04.01 and the problem hasn’t been fixed yet.
Having the same proble. have you guys have any progress? i get an error
details:You have created a new client application that uses libraries for user authentication or authorization that will soon be deprecated. New clients must use the new libraries instead; existing clients must also migrate before these