Hello gentlemen,
My name is kleber and I’m in Brazil.
I installed open fire 4.5.3 on my development server ( windows 10 ) and I am studying this application.
I installed the Openfire Meetings plugin and did several tests that worked well (no problems).
I migrated to openfire-pade-v1-0-0-candidate-release (offocus.jar, ofmeet.jar, pade.jar) and I noticed that this version has several interesting functions (I’m still testing it).
However, I noticed that after installing the opefire-pad I lost access to my system with
secure communication (https with self-signed certificate).
Note - this problem does not happen with Openfire Meetings.
One fact I realized is that I have secure access to openfire functions:
- https://my_domain:9091 (administration console)
- https://my_domain:7443 / jsxc / (web client)
- https://my_domain:7443 / ofmeet / (video conference)
Does anyone know how to solve this?
Note - I am operating in non-secure mode (http://my_domain)
Thank you for your attention.
Note - this text was translated by google.
You cannot access your webcam or microphone with any browser without using https unless your domain is localhost. I suggest you get a free certicate from letsencrypt for your openfire server
Hi Dele Olajide,
I appreciate your kindness in replying.
I solved this problem by changing port 443 for a secure connection to 3443 on apache2.
The system was normal (now I have access) but I worked on the effect (it is not a cause solution).
It is likely that openfire-pade-v1-0-0 is blocking port 443.
A hug.
Note - this text was translated by google.
Hello gentlemen,
It looks like I solved the problem.
In the administrator panel go to Meeting > Networking > Media traffic over TCP
On-screen comments :
For efficiency reasons, routing media traffic over UDP is often preferred.
Jitsi Videobridge can, however, also accept and route media traffic over TCP.
Typically, the point of using TCP instead of UDP is to simulate HTTP traffic in a
number of environments where it is the only allowed form of communication.
If enabled, TCP addresses will automatically be returned as additional ICE candidates via COLIBRI.
Mark Enabled Jitsi Videobridge can accept and route RTP traffic over TCP.
On-screen comments :
Configures the port number to be used by the TCP harvester.
If this property is not set (and the TCP harvester is enabled),
jitsi-videobridge will first try to bind on port 443, and if this fails, it will try port 4443 instead.
If the property is set, it will only try to bind to the specified port, with no fallback.
Port number: 4443 TCP ( mark 4443 door here )
In this case, port 443 is released.
Thank you for your attention.
Note - this text was translated by google.
1 Like