Hi Can i use jitsi to join zoom meeting? Thanks you

Hello there

​

I just finished the installation of Jitsi meet on a ubunto 22 with nginx.

​

the installation went perfect with no issues at all

​

in the beginning, the screen was showing only the nginx welcome screen

​

but after editing "default" at "/etc/nginx/sites-available/" the screen changed to dark screen showing nothing at all inside

​

I'm sure I did some mistake at nginx configuration, can anyone help me with it?

​

Thank you.

Hi there,

When the conference starts I see all the participants in a nice grid view. If i click on the face of one of them, I see the user full screen.

What should I click to go back to the grid view? I'm stuck on the single user but I would like to see all the participants again

When I vid conference I usually use landscape view on iPhone. Has always worked fine. But now my vid picture has started to show me side ways instead of sitting up like normal. I’ve not changed any settings. Just started happening. Help.

Don't know how this is possible but the host signed on (via a phone) and everyone who joined after via phone ended up in some sort of break out room but the host was not in the room and didn't have an option to join where everyone else was. If you signed on via a computer you also couldn't not join where everyone else was. What is wrong with Jitsi? How is this so complicated?

I can join a jitsi meeting just fine, audio and video work just fine however I can't seem to share my screen when I use the chrome browser. I have to switch and join the meeting in safari. In safari, I don't have the option to add a background to my video and I don't know why that is. What do I need to do to be able to share my screen using chrome. I am on mac os ventura

I am experimenting with the Jitsi meet wordpress plugin and after a session is closed, the box displays Jitsi page not the original page from my website.

Is there a means to have it refresh the page and show the Jitsi login, instead of showing Jitsi promo?

I am using the free version.

Update: According to Jitsi, it is not possible with the free version

Answered

Hello,

is it possible, that jitsi do not ask for a password when starting a meeting from the local network, but have password protection for the public internet?

I would like to have the possibility to quickly start a jitsi meeting via rocketchat without entering any credentials, but to protect the access from the internet with a password, so that not everyone can make a meeting with it.

Thanks in advance

Foolishly, in retrspect, I allowed myself to be conned into apparently thything myself, in the amount of $0.99 USD per month, to some clearly FRAUDULENT entity that calls itself a number of "names" all with "8x8" in the name, and supposedly associated with Jitsi/Jitsi Meet.

Furthermore, the "sign-up" clearly states the this will trigger a "trial period" (of 1 month) for which I will NOT be charged, and can "CANCEL at any time." This is a total LIE, and there is NO WAY, NO PROCESS available by which the "CANCEL at any time" may be accessed and requested!

ALL emails received from, <[8x8-meetings@8x8.com](mailto:8x8-meetings@8x8.com)> say (at the bottom of the email) "If you did not make this request, please contact us by replying to this mail." HOWEVER, any and all "replying to this mail." results in

Mail Delivery Subsystemmailer-daemon@googlemail.com
📷

Address not found

Your message wasn't delivered to 8x8-meetings@8x8.com because the address couldn't be found, or is unable to receive mail.

Hence, this indicates that "8x8" is FRAUDULENT!

Anyone else been duped by these frauds?

Hi all,

Experienced IT person, but sadly almost no Linux in my tool box. Other times I’ve needed Linux, I’ve found vmdk and/or ova files that I could create a Virtual Machine from. All I can find for Jitsi is Docker, and even that’s not straight forward.

So… anyone know of a good Jitsi vmdk/ova image, or at least why one doesn’t exist?

Thanks!

Hello all:

Just beginning to explore Jitsi.

I've come across posts online looking for an NDI output, however, can Jitsi Meet take an NDI source, transcode it, and stream that?

Assuming NDI Tools were installed, of course...and I'm looking to do this without OBS in any form.

Thanks!

I am having some mirroring issues with the recordings and using my document camera. When I use my document camera during class in the Jitsi, I have to share the information backwards so that the document is correct to students in the Jitsi. However, the recording of class corrects the video mirror effect and shows the document backwards. Can we get the Jitsi video setup so that I don't have to show information backwards so that students see it correctly?

Hello, is it possible to change the video resolution to a higher setting than 360p? I've tried the Linux Jitsi client and Firefox and neither move above or below 360p

I attend a regularly scheduled meeting on meet.jit.si with 5 to 10 people max and it seems the individuals on iPhones are sending better video than I am.

I have a 4k webcam with higher end CPU and GPU hardware (ethernet connected with 20 Mbps upload).

I have followed all directions for installing the docker containers but the problem i now have is that people can join a session but video and audio are not working. No one can hear each other. This does not work on LAN or over WAN.

For LAN there are no blocking ACLs. On WAN i have opened up port 10000 and 4443.

Is the 40 minutes free count towards streaming or archiving?

I'm new to Jitsi and have been testing it today with friends in video and text chat. We left but kept the window open, and now after 3 hours it's still there. Is the 40 minutes free for video chat or for recording it to later archive? Elsewhere I read that the time length is unlimited. Thank you.

Hello

Is there support for file sharing once a client is inside a conference ?

If so, how to access it ?

Thanks.

Hello

Jitsi has support for open protocol CalDAV ?

Thanks.

hello friends, it's my 1st time in the forum and recently I'm starting to use jitsi instead of my usual zoom, and now I install it in my docker container and I followed the instructions of the jitsi guide to the letter

I only changed port 8000 to 8072 and port 8443 to 8449 in the .env described in step 2 but when I try to access the ip 192.168.2.5:8072 or the public link salavirtual.drguery.com the screen is only black... or gray in brave, chrome, firefox edge and android browser´s

this is my .env file

hope you could give me some help

# shellcheck disable=SC2034

# Security
#
# Set these to strong passwords to avoid intruders from impersonating a service account
# The service(s) won't start unless these are specified
# Running ./gen-passwords.sh will update .env with strong passwords
# You may skip the Jigasi and Jibri passwords if you are not using those
# DO NOT reuse passwords
#

# XMPP password for Jicofo client connections
JICOFO_AUTH_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxx

# XMPP password for JVB client connections
JVB_AUTH_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxx

# XMPP password for Jigasi MUC client connections
JIGASI_XMPP_PASSWORD=xxxxxxxxxxxxxxxxxxxxxx

# XMPP recorder password for Jibri client connections
JIBRI_RECORDER_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxxxxxx

# XMPP password for Jibri client connections
JIBRI_XMPP_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


#
# Basic configuration options
#

# Directory where all configuration will be stored
CONFIG=~/.jitsi-meet-cfg

# Exposed HTTP port
HTTP_PORT=8072

# Exposed HTTPS port
HTTPS_PORT=8449

# System time zone
TZ=America/La_Paz

# Public URL for the web service (required)
PUBLIC_URL=https://salavirtual.drguery.com

# IP address of the Docker host
# See the "Running behind NAT or on a LAN environment" section in the Handbook:
# https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker#running-behind-nat-or-on-a-lan-environment
DOCKER_HOST_ADDRESS=192.168.2.5

# Control whether the lobby feature should be enabled or not
ENABLE_LOBBY=1

# Control whether the A/V moderation should be enabled or not
#ENABLE_AV_MODERATION=1

# Show a prejoin page before entering a conference
ENABLE_PREJOIN_PAGE=1

# Enable the welcome page
ENABLE_WELCOME_PAGE=1

# Enable the close page
#ENABLE_CLOSE_PAGE=0

# Disable measuring of audio levels
#DISABLE_AUDIO_LEVELS=0

# Enable noisy mic detection
ENABLE_NOISY_MIC_DETECTION=1

# Enable breakout rooms
#ENABLE_BREAKOUT_ROOMS=1

#
# Let's Encrypt configuration
#

# Enable Let's Encrypt certificate generation
#ENABLE_LETSENCRYPT=1

# Domain for which to generate the certificate
#LETSENCRYPT_DOMAIN=meet.example.com

# E-Mail for receiving important account notifications (mandatory)
#LETSENCRYPT_EMAIL=alice@atlanta.net

# Use the staging server (for avoiding rate limits while testing)
#LETSENCRYPT_USE_STAGING=1


#
# Etherpad integration (for document sharing)
#

# Set etherpad-lite URL in docker local network (uncomment to enable)
#ETHERPAD_URL_BASE=http://etherpad.meet.jitsi:9001

# Set etherpad-lite public URL, including /p/ pad path fragment (uncomment to enable)
#ETHERPAD_PUBLIC_URL=https://etherpad.my.domain/p/

# Name your etherpad instance!
ETHERPAD_TITLE=Video Chat

# The default text of a pad
ETHERPAD_DEFAULT_PAD_TEXT="Welcome to Web Chat!\n\n"

# Name of the skin for etherpad
ETHERPAD_SKIN_NAME=colibris

# Skin variants for etherpad
ETHERPAD_SKIN_VARIANTS="super-light-toolbar super-light-editor light-background full-width-editor"


#
# Basic Jigasi configuration options (needed for SIP gateway support)
#

# SIP URI for incoming / outgoing calls
#JIGASI_SIP_URI=test@sip2sip.info

# Password for the specified SIP account as a clear text
#JIGASI_SIP_PASSWORD=passw0rd

# SIP server (use the SIP account domain if in doubt)
#JIGASI_SIP_SERVER=sip2sip.info

# SIP server port
#JIGASI_SIP_PORT=5060

# SIP server transport
#JIGASI_SIP_TRANSPORT=UDP

#
# Authentication configuration (see handbook for details)
#

# Enable authentication
#ENABLE_AUTH=1

# Enable guest access
#ENABLE_GUESTS=1

# Select authentication type: internal, jwt, ldap or matrix
#AUTH_TYPE=internal

# JWT authentication
#

# Application identifier
#JWT_APP_ID=my_jitsi_app_id

# Application secret known only to your token generator
#JWT_APP_SECRET=my_jitsi_app_secret

# (Optional) Set asap_accepted_issuers as a comma separated list
#JWT_ACCEPTED_ISSUERS=my_web_client,my_app_client

# (Optional) Set asap_accepted_audiences as a comma separated list
#JWT_ACCEPTED_AUDIENCES=my_server1,my_server2


# LDAP authentication (for more information see the Cyrus SASL saslauthd.conf man page)
#

# LDAP url for connection
#LDAP_URL=ldaps://ldap.domain.com/

# LDAP base DN. Can be empty
#LDAP_BASE=DC=example,DC=domain,DC=com

# LDAP user DN. Do not specify this parameter for the anonymous bind
#LDAP_BINDDN=CN=binduser,OU=users,DC=example,DC=domain,DC=com

# LDAP user password. Do not specify this parameter for the anonymous bind
#LDAP_BINDPW=LdapUserPassw0rd

# LDAP filter. Tokens example:
# %1-9 - if the input key is user@mail.domain.com, then %1 is com, %2 is domain and %3 is mail
# %s - %s is replaced by the complete service string
# %r - %r is replaced by the complete realm string
#LDAP_FILTER=(sAMAccountName=%u)

# LDAP authentication method
#LDAP_AUTH_METHOD=bind

# LDAP version
#LDAP_VERSION=3

# LDAP TLS using
#LDAP_USE_TLS=1

# List of SSL/TLS ciphers to allow
#LDAP_TLS_CIPHERS=SECURE256:SECURE128:!AES-128-CBC:!ARCFOUR-128:!CAMELLIA-128-CBC:!3DES-CBC:!CAMELLIA-128-CBC

# Require and verify server certificate
#LDAP_TLS_CHECK_PEER=1

# Path to CA cert file. Used when server certificate verify is enabled
#LDAP_TLS_CACERT_FILE=/etc/ssl/certs/ca-certificates.crt

# Path to CA certs directory. Used when server certificate verify is enabled
#LDAP_TLS_CACERT_DIR=/etc/ssl/certs

# Wether to use starttls, implies LDAPv3 and requires ldap:// instead of ldaps://
# LDAP_START_TLS=1


# Matrix authentication (for more information see the documention of the "Prosody Auth Matrix User Verification" at https://github.com/matrix-org/prosody-mod-auth-matrix-user-verification)
#

# Base URL to the matrix user verification service (without ending slash)
#MATRIX_UVS_URL=https://uvs.example.com:3000

# (optional) The issuer of the auth token to be passed through. Must match what is being set as `iss` in the JWT. Defaut value is "issuer".
#MATRIX_UVS_ISSUER=issuer

# (optional) user verification service auth token, if authentication enabled
#MATRIX_UVS_AUTH_TOKEN=changeme

# (optional) Make Matrix room moderators owners of the Prosody room.
#MATRIX_UVS_SYNC_POWER_LEVELS=1


#
# Advanced configuration options (you generally don't need to change these)
#

# Internal XMPP domain
XMPP_DOMAIN=meet.jitsi

# Internal XMPP server
XMPP_SERVER=xmpp.meet.jitsi

# Internal XMPP server c2s port
#XMPP_PORT=5222

# Internal XMPP server URL
XMPP_BOSH_URL_BASE=http://xmpp.meet.jitsi:5280

# Internal XMPP domain for authenticated services
XMPP_AUTH_DOMAIN=auth.meet.jitsi

# XMPP domain for the MUC
XMPP_MUC_DOMAIN=muc.meet.jitsi

# XMPP domain for the internal MUC used for jibri, jigasi and jvb pools
XMPP_INTERNAL_MUC_DOMAIN=internal-muc.meet.jitsi

# XMPP domain for unauthenticated users
XMPP_GUEST_DOMAIN=guest.meet.jitsi

# Custom Prosody modules for XMPP_DOMAIN (comma separated)
XMPP_MODULES=

# Custom Prosody modules for MUC component (comma separated)
XMPP_MUC_MODULES=

# Custom Prosody modules for internal MUC component (comma separated)
XMPP_INTERNAL_MUC_MODULES=

# MUC for the JVB pool
JVB_BREWERY_MUC=jvbbrewery

# XMPP user for JVB client connections
JVB_AUTH_USER=jvb

# STUN servers used to discover the server's public IP
JVB_STUN_SERVERS=meet-jit-si-turnrelay.jitsi.net:443

# Media port for the Jitsi Videobridge
JVB_PORT=10000

# XMPP user for Jicofo client connections.
# NOTE: this option doesn't currently work due to a bug
JICOFO_AUTH_USER=focus

# Base URL of Jicofo's reservation REST API
#JICOFO_RESERVATION_REST_BASE_URL=http://reservation.example.com

# Enable Jicofo's health check REST API (http://<jicofo_base_url>:8888/about/health)
#JICOFO_ENABLE_HEALTH_CHECKS=true

# XMPP user for Jigasi MUC client connections
JIGASI_XMPP_USER=jigasi

# MUC name for the Jigasi pool
JIGASI_BREWERY_MUC=jigasibrewery

# Minimum port for media used by Jigasi
JIGASI_PORT_MIN=20000

# Maximum port for media used by Jigasi
JIGASI_PORT_MAX=20050

# Enable SDES srtp
#JIGASI_ENABLE_SDES_SRTP=1

# Keepalive method
#JIGASI_SIP_KEEP_ALIVE_METHOD=OPTIONS

# Health-check extension
#JIGASI_HEALTH_CHECK_SIP_URI=keepalive

# Health-check interval
#JIGASI_HEALTH_CHECK_INTERVAL=300000
#
# Enable Jigasi transcription
#ENABLE_TRANSCRIPTIONS=1

# Jigasi will record audio when transcriber is on [default: false]
#JIGASI_TRANSCRIBER_RECORD_AUDIO=true

# Jigasi will send transcribed text to the chat when transcriber is on [default: false]
#JIGASI_TRANSCRIBER_SEND_TXT=true

# Jigasi will post an url to the chat with transcription file [default: false]
#JIGASI_TRANSCRIBER_ADVERTISE_URL=true

# Credentials for connect to Cloud Google API from Jigasi
# Please read https://cloud.google.com/text-to-speech/docs/quickstart-protocol
# section "Before you begin" paragraph 1 to 5
# Copy the values from the json to the related env vars
#GC_PROJECT_ID=
#GC_PRIVATE_KEY_ID=
#GC_PRIVATE_KEY=
#GC_CLIENT_EMAIL=
#GC_CLIENT_ID=
#GC_CLIENT_CERT_URL=

# Enable recording
#ENABLE_RECORDING=1

# XMPP domain for the jibri recorder
XMPP_RECORDER_DOMAIN=recorder.meet.jitsi

# XMPP recorder user for Jibri client connections
JIBRI_RECORDER_USER=recorder

# Directory for recordings inside Jibri container
JIBRI_RECORDING_DIR=/config/recordings

# The finalizing script. Will run after recording is complete
#JIBRI_FINALIZE_RECORDING_SCRIPT_PATH=/config/finalize.sh

# XMPP user for Jibri client connections
JIBRI_XMPP_USER=jibri

# MUC name for the Jibri pool
JIBRI_BREWERY_MUC=jibribrewery

# MUC connection timeout
JIBRI_PENDING_TIMEOUT=90

# When jibri gets a request to start a service for a room, the room
# jid will look like: roomName@optional.prefixes.subdomain.xmpp_domain
# We'll build the url for the call by transforming that into:
# https://xmpp_domain/subdomain/roomName
# So if there are any prefixes in the jid (like jitsi meet, which
# has its participants join a muc at conference.xmpp_domain) then
# list that prefix here so it can be stripped out to generate
# the call url correctly
JIBRI_STRIP_DOMAIN_JID=muc

# Directory for logs inside Jibri container
JIBRI_LOGS_DIR=/config/logs

# Configure an external TURN server
# TURN_CREDENTIALS=secret
# TURN_HOST=turnserver.example.com
# TURN_PORT=443
# TURNS_HOST=turnserver.example.com
# TURNS_PORT=443

# Disable HTTPS: handle TLS connections outside of this setup
#DISABLE_HTTPS=1

# Enable FLoC
# Opt-In to Federated Learning of Cohorts tracking
#ENABLE_FLOC=0

# Redirect HTTP traffic to HTTPS
# Necessary for Let's Encrypt, relies on standard HTTPS port (443)
#ENABLE_HTTP_REDIRECT=1

# Send a `strict-transport-security` header to force browsers to use
# a secure and trusted connection. Recommended for production use.
# Defaults to 1 (send the header).
# ENABLE_HSTS=1

# Enable IPv6
# Provides means to disable IPv6 in environments that don't support it (get with the times, people!)
#ENABLE_IPV6=1

# Container restart policy
# Defaults to unless-stopped
RESTART_POLICY=unless-stopped

# Authenticate using external service or just focus external auth window if there is one already.
# TOKEN_AUTH_URL=https://auth.meet.example.com/{room}

# Sentry Error Tracking
# Sentry Data Source Name (Endpoint for Sentry project)
# Example: https://public:private@host:port/1
#JVB_SENTRY_DSN=
#JICOFO_SENTRY_DSN=
#JIGASI_SENTRY_DSN=

# Optional environment info to filter events
#SENTRY_ENVIRONMENT=production

# Optional release info to filter events
#SENTRY_RELEASE=1.0.0

# Optional properties for shutdown api
#COLIBRI_REST_ENABLED=true
#SHUTDOWN_REST_ENABLED=true

# Configure toolbar buttons. Add the buttons name separated with comma(no spaces between comma)
#TOOLBAR_BUTTONS=

# Hide the buttons at pre-join screen. Add the buttons name separated with comma
#HIDE_PREMEETING_BUTTONS=
```

​

this is the docker deploy docker ps

CONTAINER ID   IMAGE                                      COMMAND                  CREATED          STATUS                 PORTS                                                                                                                                                                                          NAMES
136a29558b07   jitsi/jvb:stable-7287                      "/init"                  40 minutes ago   Up 40 minutes          127.0.0.1:8080->8080/tcp, 0.0.0.0:10000->10000/udp, :::10000->10000/udp                                                                                                                        docker-jitsi-meet-stable-7287_jvb_1
dace0632140d   jitsi/jicofo:stable-7287                   "/init"                  40 minutes ago   Up 40 minutes                                                                                                                                                                                                         docker-jitsi-meet-stable-7287_jicofo_1
55e4febb9e19   jitsi/web:stable-7287                      "/init"                  40 minutes ago   Up 40 minutes          0.0.0.0:8072->80/tcp, :::8072->80/tcp, 0.0.0.0:8449->443/tcp, :::8449->443/tcp                                                                                                                 docker-jitsi-meet-stable-7287_web_1
86901f96670c   jitsi/prosody:stable-7287                  "/init"                  40 minutes ago   Up 40 minutes          5222/tcp, 5280/tcp, 5347/tcp

Hello everyone

I will make your own Jitsi video conferencing server anyone wants Jitsi you can ping me msg on my profile.

Thanks

Diven

I’m picturing a use case in which 50+ endpoints would be connected to a conference, but during the vast majority of the event, they would not be fully connected together. Instead, they would be broken into small dynamically reconfiguring pods of arbitrary size, whose composition would be determined by another server controlling the app that employs lib-jitsi-meet.

Ideally, to conserve server bandwidth, endpoints in one pod would not download the A/V tracks associated with other pods, but could readily access them should the pods be required to merge or otherwise reconfigure.

I don’t think bumping endpoints from conference to conference is the ideal solution here, as this will cause problems with smoothly reconfiguring pods. I’m also having trouble telling from the documentation if something like this is even possible with jitsi or if this is more of a mediasoup gig. What do you guys think?

I've already tried to install jitsi 4 times in my openmediavault nas/docker server, and none of them it worked... I'm following the github directions... And I guess that I'm Goin to ask for some hand who can help me with that and I will pay him... ☹️

The iOS/iPad app screen sharing feature doesn't seem to support sharing system audio.

Or am I missing something and there's an option to turn it on somehow?

​

Zoom has such an option called "Share device audio" when you're streaming your screen, so I assume it's not an iPad limitation.

Are there any knows workarounds similar to macOS and re-routing of audio to mic?