Troubleshooting & help
Use the Connection Test utility to troubleshoot connection problems. Inside the meeting room, choose Help > Troubleshooting to run the test. For more information on connection problems, see Troubleshoot connectivity | Adobe Connect.
Yes. You have several options for controlling who can join your meeting. From inside your Adobe Connect meeting room, choose Meeting > Manage Access and Entry, and then choose one of the options from the submenu. You can also manage meeting participants from Adobe Connect Central.
You can update your credit card and other billing information from your Manage Subscription page. Go to the Adobe Connect online store, and then enter your order number and order password to access your account.
In Adobe Connect Central, choose Administration > Service Plan > Change Service Plan > Cancel Your Plan. You can also cancel your subscription from the Adobe Connect online store. Simply enter your order number and order password to access your account. Get more information about managing your Adobe Connect account in the Adobe Connect FAQ.
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))
This error message displays when Podman isn't installed properly, or the user has logged in using the root user (sudo su). Follow the steps below:
- Remove Podman, sudo yum remove podman-remote.
- Log out of the current user and log in again.
- Run, ./external/install.sh.
Note: Do not change the user to root ("sudo su" or any other related command) or use sudo while running the script.
The media server needs 1 :1 NAT, which means any traffic egress and ingress for the media server for the internet needs to use the public IP. The media server auto-discovers its public IP to use the STUN protocol, once you have configured 1:1 NAT for the media server on your router or firewall. Please go to the admin interface of the WebRTC gateway and make sure that the mediaver can detect its public IP address.
Media Server is not reachable from Clients even after 1:1 NAT working fine
The WebRTC Client uses ICE and tries to establish an audio-video stream with the media server in the order below:
UDP in port range 35000 to 65535
TCP over port 3478
TLS over port 443
C12 WebRTC based Client will try all options (TCP and UDP) , before it switches to TLS over port 443
Connect 12 is by default designed with the assumption that CPS and WebRTC and New Connect Cluster (aka NCC) are in the same VLAN/VPC or broadcast domain. In case you've them in different networks, ensure that you've proper layer three routing between CPS and NCC/WebRTC to have network connectivity in both directions.
To check the network connectivity between CPS and NCC, use CURL and Telnet.
CPS and NCC connectivity work over HTTPS only.
The error below appears in the FMGW container logs. The second Redis instance is set to run as a replica.
ERROR [FM.LiveSwitch.Signalling.Server.IdleThread][-] 2022-07-21T12:46:29.439Z Unexpected error in idle thread.
StackExchange.Redis.RedisServerException: READONLY You can't write against a read only replica.
Open the configuration file corresponding to the Redis service and modify the value of the attribute "slave-read-only" to “no”.