Re: Media server connection is failed, will try to re-connect
According HTTPD config: everything looks great Locations like `` was required by Flash version and can now be dropped Such config require `$OM_HOME/conf/server.xml` modification, but I'm sure you did it You can send me private email, and I'll try to check if your server works for me On Tue, 28 Mar 2023 at 22:01, Maxim Solodovnik wrote: > > On Tue, 28 Mar 2023 at 21:32, Thomas Scholzen wrote: > > > > Hi Maxim, > > > > the size of the backup was ~ 4 GB. When the upgrade failed, > > Was there anything suspicious in the logs? > > > I reinstalled OM 7.0.0. When having problems, I also reinstalled coturn & > > docker (plus km). When all failed I asked you ;-). The (re) installation > > was done on the same server on which OM 6.0.0 was running before. > > > > can you check if https://demo-openmeetings.apache.org/openmeetings > works for you? > > My coturn config looks like follows: > > fingerprint > lt-cred-mech > use-auth-secret > static-auth-secret=*** > realm=demo-openmeetings.apache.org > stale-nonce=0 > proc-user=nobody > proc-group=nogroup > > > OM config > ## Kurento ## > kurento.ws.url=ws://127.0.0.1:/kurento > kurento.turn.url=PUBLIC_IP:3478 > kurento.turn.user=demo-user > kurento.turn.secret=*** > kurento.turn.mode=rest > > > > Please ensure "PUBLIC_IP:3478" is available to the world (connections > happens via UDP by default) > > > Kind regards > > Thomas > > > > > > Am 28.03.2023 15:52, schrieb Maxim Solodovnik: > > > > > > > > from mobile (sorry for typos ;) > > > > > > On Tue, Mar 28, 2023, 20:33 Thomas Scholzen wrote: > > > > Hi Maxim, > > > > thanks for the fast response. I used the command line for migration, and it > > did not work (restoreing backup just hangs forever). > > > > > > Sounds like the error of backup create/restore tool :( > > I would like to have it 100% bulletproof > > > > What is the size of your backup? > > Do you have anything suspicious in the logs? > > > > > > But no problem there, I should clean up the installation anyway ;-). > > > > My server is not a VM but bare metall. So I have to live with the > > interference of other services. > > > > As you suggested, I will try kurento without docker and see how it goes. > > > > > > So you have re-installed om+kms+coturn at your server? (I would update om > > only ...) > > Or set up new server? > > > > > > > > Thanks for you kind help > > Thomas > > > > > > Am 28.03.2023 11:27, schrieb Maxim Solodovnik: > > > > Hello Thomas, > > > > On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen wrote: > > > > > > Hi Maxim, > > > > I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too > > much stuff in the backup) > > > > > > I believe you can use command line admin in such case > > https://openmeetings.apache.org/CommandLineAdmin.html > > > > I went for a fresh installation. I installed OM 7.0.0, kurento via docker > > and coturn. However, I get "Media server connection for user XXX is > > failed, will try to re-connect" every 2 to 15 seconds, depending on the > > client and location. When the internet is routed via VPN to the server that > > runs OM, there are no problems. OS Ubuntu 20.04 > > > > > > I would say you have installed too much ... > > Is it fresh new VM? > > Can you run OM7 at the VM/server you already have for OM6? > > > > I've just have checked the changes > > And I would say your migration should be flawless (no real changes in > > KMS/Coturn integration) > > > > Maybe you can try to run OM7 nearby OM6? > > - different port > > OR > > - stop one -> start another? > > > > So I suspect an issue with the turnserver. With OM 6.0.0 this setup went > > fine, so there is probably some kind of misconfiguration. > > > > > > This can be both TURN server issues and network misconfiguration at > > new VM/server > > > > > > "$ docker logs kms" gives me: > > > > "KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:609:WebRtcEndpointImpl: > > TURN server not found in config; remember that NAT traversal requires STUN > > or TURN" > > > > > > This is more or less expected > > I never had enough time to set up TURN inside KMS :( > > And everything seems to work at demo server > > > > > > In /etc/turnserver.conf I have: > > use-auth-secret > > static-auth-secret=7xxx > > realm=testexample.de > > stale-nonce=0 > > log-file=/var/log/turnserver/turnserver.log > > syslog > > > > In webapps/openmeetings/WEB-INF/classes/openmeetings.properties I have: > > > >kurento.ws.url=ws://127.0.0.1:/kurento > >kurento.turn.url=xxx.yyy.zzz.aaa:3478 > >kurento.turn.user= > >kurento.turn.secret=7xxx > >kurento.turn.mode=rest > > > > Because I run also other services on this server SSL is done via port 4443 > > with a proxy to localhost:5080/openmeetings (see attached apache2 virtual > > host config). This makes it a bit complicated, but it was working
Re: Media server connection is failed, will try to re-connect
On Tue, 28 Mar 2023 at 21:32, Thomas Scholzen wrote: > > Hi Maxim, > > the size of the backup was ~ 4 GB. When the upgrade failed, Was there anything suspicious in the logs? > I reinstalled OM 7.0.0. When having problems, I also reinstalled coturn & > docker (plus km). When all failed I asked you ;-). The (re) installation was > done on the same server on which OM 6.0.0 was running before. > can you check if https://demo-openmeetings.apache.org/openmeetings works for you? My coturn config looks like follows: fingerprint lt-cred-mech use-auth-secret static-auth-secret=*** realm=demo-openmeetings.apache.org stale-nonce=0 proc-user=nobody proc-group=nogroup OM config ## Kurento ## kurento.ws.url=ws://127.0.0.1:/kurento kurento.turn.url=PUBLIC_IP:3478 kurento.turn.user=demo-user kurento.turn.secret=*** kurento.turn.mode=rest Please ensure "PUBLIC_IP:3478" is available to the world (connections happens via UDP by default) > Kind regards > Thomas > > > Am 28.03.2023 15:52, schrieb Maxim Solodovnik: > > > > from mobile (sorry for typos ;) > > > On Tue, Mar 28, 2023, 20:33 Thomas Scholzen wrote: > > Hi Maxim, > > thanks for the fast response. I used the command line for migration, and it > did not work (restoreing backup just hangs forever). > > > Sounds like the error of backup create/restore tool :( > I would like to have it 100% bulletproof > > What is the size of your backup? > Do you have anything suspicious in the logs? > > > But no problem there, I should clean up the installation anyway ;-). > > My server is not a VM but bare metall. So I have to live with the > interference of other services. > > As you suggested, I will try kurento without docker and see how it goes. > > > So you have re-installed om+kms+coturn at your server? (I would update om > only ...) > Or set up new server? > > > > Thanks for you kind help > Thomas > > > Am 28.03.2023 11:27, schrieb Maxim Solodovnik: > > Hello Thomas, > > On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen wrote: > > > Hi Maxim, > > I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too > much stuff in the backup) > > > I believe you can use command line admin in such case > https://openmeetings.apache.org/CommandLineAdmin.html > > I went for a fresh installation. I installed OM 7.0.0, kurento via docker and > coturn. However, I get "Media server connection for user XXX is failed, will > try to re-connect" every 2 to 15 seconds, depending on the client and > location. When the internet is routed via VPN to the server that runs OM, > there are no problems. OS Ubuntu 20.04 > > > I would say you have installed too much ... > Is it fresh new VM? > Can you run OM7 at the VM/server you already have for OM6? > > I've just have checked the changes > And I would say your migration should be flawless (no real changes in > KMS/Coturn integration) > > Maybe you can try to run OM7 nearby OM6? > - different port > OR > - stop one -> start another? > > So I suspect an issue with the turnserver. With OM 6.0.0 this setup went > fine, so there is probably some kind of misconfiguration. > > > This can be both TURN server issues and network misconfiguration at > new VM/server > > > "$ docker logs kms" gives me: > > "KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:609:WebRtcEndpointImpl: > TURN server not found in config; remember that NAT traversal requires STUN or > TURN" > > > This is more or less expected > I never had enough time to set up TURN inside KMS :( > And everything seems to work at demo server > > > In /etc/turnserver.conf I have: > use-auth-secret > static-auth-secret=7xxx > realm=testexample.de > stale-nonce=0 > log-file=/var/log/turnserver/turnserver.log > syslog > > In webapps/openmeetings/WEB-INF/classes/openmeetings.properties I have: > >kurento.ws.url=ws://127.0.0.1:/kurento >kurento.turn.url=xxx.yyy.zzz.aaa:3478 >kurento.turn.user= >kurento.turn.secret=7xxx >kurento.turn.mode=rest > > Because I run also other services on this server SSL is done via port 4443 > with a proxy to localhost:5080/openmeetings (see attached apache2 virtual > host config). This makes it a bit complicated, but it was working flawless > with OM 6.0.0 > > I Would appreciate if you could give me a hint how to debug this. > > > BTW "kurento via docker" might be not necessary in your case > KMS7 was released and it natively supports Ubuntu 20 :) > > > Best regards > Thomas > > > -- Best regards, Maxim
Re: Media server connection is failed, will try to re-connect
Hi Maxim, the size of the backup was ~ 4 GB. When the upgrade failed, I reinstalled OM 7.0.0. When having problems, I also reinstalled coturn & docker (plus km). When all failed I asked you ;-). The (re) installation was done on the same server on which OM 6.0.0 was running before. Kind regards Thomas Am 28.03.2023 15:52, schrieb Maxim Solodovnik: from mobile (sorry for typos ;) On Tue, Mar 28, 2023, 20:33 Thomas Scholzen wrote: Hi Maxim, thanks for the fast response. I used the command line for migration, and it did not work (restoreing backup just hangs forever). Sounds like the error of backup create/restore tool :( I would like to have it 100% bulletproof What is the size of your backup? Do you have anything suspicious in the logs? But no problem there, I should clean up the installation anyway ;-). My server is not a VM but bare metall. So I have to live with the interference of other services. As you suggested, I will try kurento without docker and see how it goes. So you have re-installed om+kms+coturn at your server? (I would update om only ...) Or set up new server? Thanks for you kind help Thomas Am 28.03.2023 11:27, schrieb Maxim Solodovnik: Hello Thomas, On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen wrote: Hi Maxim, I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too much stuff in the backup) I believe you can use command line admin in such case https://openmeetings.apache.org/CommandLineAdmin.html I went for a fresh installation. I installed OM 7.0.0, kurento via docker and coturn. However, I get "Media server connection for user XXX is failed, will try to re-connect" every 2 to 15 seconds, depending on the client and location. When the internet is routed via VPN to the server that runs OM, there are no problems. OS Ubuntu 20.04 I would say you have installed too much ... Is it fresh new VM? Can you run OM7 at the VM/server you already have for OM6? I've just have checked the changes And I would say your migration should be flawless (no real changes in KMS/Coturn integration) Maybe you can try to run OM7 nearby OM6? - different port OR - stop one -> start another? So I suspect an issue with the turnserver. With OM 6.0.0 this setup went fine, so there is probably some kind of misconfiguration. This can be both TURN server issues and network misconfiguration at new VM/server "$ docker logs kms" gives me: "KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:609:WebRtcEndpointImpl: TURN server not found in config; remember that NAT traversal requires STUN or TURN" This is more or less expected I never had enough time to set up TURN inside KMS :( And everything seems to work at demo server In /etc/turnserver.conf I have: use-auth-secret static-auth-secret=7xxx realm=testexample.de [1] stale-nonce=0 log-file=/var/log/turnserver/turnserver.log syslog In webapps/openmeetings/WEB-INF/classes/openmeetings.properties I have: kurento.ws.url=ws://127.0.0.1:/kurento [2] kurento.turn.url=xxx.yyy.zzz.aaa:3478 kurento.turn.user= kurento.turn.secret=7xxx kurento.turn.mode=rest Because I run also other services on this server SSL is done via port 4443 with a proxy to localhost:5080/openmeetings (see attached apache2 virtual host config). This makes it a bit complicated, but it was working flawless with OM 6.0.0 I Would appreciate if you could give me a hint how to debug this. BTW "kurento via docker" might be not necessary in your case KMS7 was released and it natively supports Ubuntu 20 :) Best regards Thomas Links: -- [1] http://testexample.de [2] http://127.0.0.1:/kurento
CVE-2023-28326: Apache OpenMeetings: allows user impersonation
Severity: critical Description: Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.0.0 Description: Attacker can elevate their privileges in any room This issue is being tracked as OPENMEETINGS-2739 Credit: Dennis Zimmt (reporter) References: https://openmeetings.apache.org/ https://www.cve.org/CVERecord?id=CVE-2023-28326 https://issues.apache.org/jira/browse/OPENMEETINGS-2739
CVE-2023-28326: Apache OpenMeetings: allows user impersonation
Severity: critical Description: Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.0.0 before 7.0.0 Description: Attacker can elevate their privileges in any room This issue is being tracked as OPENMEETINGS-2739 Credit: Dennis Zimmt (reporter) References: https://openmeetings.apache.org/ https://www.cve.org/CVERecord?id=CVE-2023-28326 https://issues.apache.org/jira/browse/OPENMEETINGS-2739
Re: Media server connection is failed, will try to re-connect
from mobile (sorry for typos ;) On Tue, Mar 28, 2023, 20:33 Thomas Scholzen wrote: > Hi Maxim, > > thanks for the fast response. I used the command line for migration, and > it did not work (restoreing backup just hangs forever). > Sounds like the error of backup create/restore tool :( I would like to have it 100% bulletproof What is the size of your backup? Do you have anything suspicious in the logs? But no problem there, I should clean up the installation anyway ;-). > > My server is not a VM but bare metall. So I have to live with the > interference of other services. > > As you suggested, I will try kurento without docker and see how it goes. > So you have re-installed om+kms+coturn at your server? (I would update om only ...) Or set up new server? Thanks for you kind help > Thomas > > > Am 28.03.2023 11:27, schrieb Maxim Solodovnik: > > Hello Thomas, > > On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen > wrote: > > > Hi Maxim, > > I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too > much stuff in the backup) > > > I believe you can use command line admin in such case > https://openmeetings.apache.org/CommandLineAdmin.html > > I went for a fresh installation. I installed OM 7.0.0, kurento via docker > and coturn. However, I get “Media server connection for user XXX is > failed, will try to re-connect” every 2 to 15 seconds, depending on the > client and location. When the internet is routed via VPN to the server that > runs OM, there are no problems. OS Ubuntu 20.04 > > > I would say you have installed too much ... > Is it fresh new VM? > Can you run OM7 at the VM/server you already have for OM6? > > I've just have checked the changes > And I would say your migration should be flawless (no real changes in > KMS/Coturn integration) > > Maybe you can try to run OM7 nearby OM6? > - different port > OR > - stop one -> start another? > > So I suspect an issue with the turnserver. With OM 6.0.0 this setup went > fine, so there is probably some kind of misconfiguration. > > > This can be both TURN server issues and network misconfiguration at > new VM/server > > > “$ docker logs kms” gives me: > > “KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:609:WebRtcEndpointImpl: > TURN server not found in config; remember that NAT traversal requires STUN > or TURN” > > > This is more or less expected > I never had enough time to set up TURN inside KMS :( > And everything seems to work at demo server > > > In /etc/turnserver.conf I have: > use-auth-secret > static-auth-secret=7xxx > realm=testexample.de > stale-nonce=0 > log-file=/var/log/turnserver/turnserver.log > syslog > > In webapps/openmeetings/WEB-INF/classes/openmeetings.properties I have: > >kurento.ws.url=ws://127.0.0.1:/kurento >kurento.turn.url=xxx.yyy.zzz.aaa:3478 >kurento.turn.user= >kurento.turn.secret=7xxx >kurento.turn.mode=rest > > Because I run also other services on this server SSL is done via port 4443 > with a proxy to localhost:5080/openmeetings (see attached apache2 virtual > host config). This makes it a bit complicated, but it was working flawless > with OM 6.0.0 > > I Would appreciate if you could give me a hint how to debug this. > > > BTW "kurento via docker" might be not necessary in your case > KMS7 was released and it natively supports Ubuntu 20 :) > > > Best regards > Thomas > > > >
Re: Media server connection is failed, will try to re-connect
Hi Maxim, thanks for the fast response. I used the command line for migration, and it did not work (restoreing backup just hangs forever). But no problem there, I should clean up the installation anyway ;-). My server is not a VM but bare metall. So I have to live with the interference of other services. As you suggested, I will try kurento without docker and see how it goes. Thanks for you kind help Thomas Am 28.03.2023 11:27, schrieb Maxim Solodovnik: Hello Thomas, On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen wrote: Hi Maxim, I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too much stuff in the backup) I believe you can use command line admin in such case https://openmeetings.apache.org/CommandLineAdmin.html I went for a fresh installation. I installed OM 7.0.0, kurento via docker and coturn. However, I get "Media server connection for user XXX is failed, will try to re-connect" every 2 to 15 seconds, depending on the client and location. When the internet is routed via VPN to the server that runs OM, there are no problems. OS Ubuntu 20.04 I would say you have installed too much ... Is it fresh new VM? Can you run OM7 at the VM/server you already have for OM6? I've just have checked the changes And I would say your migration should be flawless (no real changes in KMS/Coturn integration) Maybe you can try to run OM7 nearby OM6? - different port OR - stop one -> start another? So I suspect an issue with the turnserver. With OM 6.0.0 this setup went fine, so there is probably some kind of misconfiguration. This can be both TURN server issues and network misconfiguration at new VM/server "$ docker logs kms" gives me: "KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:609:WebRtcEndpointImpl: TURN server not found in config; remember that NAT traversal requires STUN or TURN" This is more or less expected I never had enough time to set up TURN inside KMS :( And everything seems to work at demo server In /etc/turnserver.conf I have: use-auth-secret static-auth-secret=7xxx realm=testexample.de stale-nonce=0 log-file=/var/log/turnserver/turnserver.log syslog In webapps/openmeetings/WEB-INF/classes/openmeetings.properties I have: kurento.ws.url=ws://127.0.0.1:/kurento kurento.turn.url=xxx.yyy.zzz.aaa:3478 kurento.turn.user= kurento.turn.secret=7xxx kurento.turn.mode=rest Because I run also other services on this server SSL is done via port 4443 with a proxy to localhost:5080/openmeetings (see attached apache2 virtual host config). This makes it a bit complicated, but it was working flawless with OM 6.0.0 I Would appreciate if you could give me a hint how to debug this. BTW "kurento via docker" might be not necessary in your case KMS7 was released and it natively supports Ubuntu 20 :) Best regards Thomas
Re: Media server connection is failed, will try to re-connect
Hello Thomas, On Tue, 28 Mar 2023 at 15:41, Thomas Scholzen wrote: > > Hi Maxim, > > I just migrated from OM 6.00 to 7.00. After the upgrade did not work (too > much stuff in the backup) I believe you can use command line admin in such case https://openmeetings.apache.org/CommandLineAdmin.html > I went for a fresh installation. I installed OM 7.0.0, kurento via docker and > coturn. However, I get “Media server connection for user XXX is failed, will > try to re-connect” every 2 to 15 seconds, depending on the client and > location. When the internet is routed via VPN to the server that runs OM, > there are no problems. OS Ubuntu 20.04 I would say you have installed too much ... Is it fresh new VM? Can you run OM7 at the VM/server you already have for OM6? I've just have checked the changes And I would say your migration should be flawless (no real changes in KMS/Coturn integration) Maybe you can try to run OM7 nearby OM6? - different port OR - stop one -> start another? > So I suspect an issue with the turnserver. With OM 6.0.0 this setup went > fine, so there is probably some kind of misconfiguration. This can be both TURN server issues and network misconfiguration at new VM/server > > “$ docker logs kms” gives me: > > “KurentoWebRtcEndpointImpl WebRtcEndpointImpl.cpp:609:WebRtcEndpointImpl: > TURN server not found in config; remember that NAT traversal requires STUN or > TURN” This is more or less expected I never had enough time to set up TURN inside KMS :( And everything seems to work at demo server > > In /etc/turnserver.conf I have: > use-auth-secret > static-auth-secret=7xxx > realm=testexample.de > stale-nonce=0 > log-file=/var/log/turnserver/turnserver.log > syslog > > In webapps/openmeetings/WEB-INF/classes/openmeetings.properties I have: > >kurento.ws.url=ws://127.0.0.1:/kurento >kurento.turn.url=xxx.yyy.zzz.aaa:3478 >kurento.turn.user= >kurento.turn.secret=7xxx >kurento.turn.mode=rest > > Because I run also other services on this server SSL is done via port 4443 > with a proxy to localhost:5080/openmeetings (see attached apache2 virtual > host config). This makes it a bit complicated, but it was working flawless > with OM 6.0.0 > > I Would appreciate if you could give me a hint how to debug this. BTW "kurento via docker" might be not necessary in your case KMS7 was released and it natively supports Ubuntu 20 :) > > Best regards > Thomas -- Best regards, Maxim
Media server connection is failed, will try to re-connect
Hi Maxim,
I just migrated from OM 6.00 to 7.00. After the upgrade did not work
(too much stuff in the backup) I went for a fresh installation. I
installed OM 7.0.0, kurento via docker and coturn. However, I get "Media
server connection for user XXX is failed, will try to re-connect" every
2 to 15 seconds, depending on the client and location. When the internet
is routed via VPN to the server that runs OM, there are no problems. OS
Ubuntu 20.04
So I suspect an issue with the turnserver. With OM 6.0.0 this setup went
fine, so there is probably some kind of misconfiguration.
"$ docker logs kms" gives me:
"KurentoWebRtcEndpointImpl
WebRtcEndpointImpl.cpp:609:WebRtcEndpointImpl: TURN server not found in
config; remember that NAT traversal requires STUN or TURN"
In /etc/turnserver.conf I have:
use-auth-secret
static-auth-secret=7xxx
realm=testexample.de
stale-nonce=0
log-file=/var/log/turnserver/turnserver.log
syslog
In webapps/openmeetings/WEB-INF/classes/openmeetings.properties I have:
kurento.ws.url=ws://127.0.0.1:/kurento
kurento.turn.url=xxx.yyy.zzz.aaa:3478
kurento.turn.user=
kurento.turn.secret=7xxx
kurento.turn.mode=rest
Because I run also other services on this server SSL is done via port
4443 with a proxy to localhost:5080/openmeetings (see attached apache2
virtual host config). This makes it a bit complicated, but it was
working flawless with OM 6.0.0
I Would appreciate if you could give me a hint how to debug this.
Best regards
Thomas# NameVirtualHost *:4443
ServerName openmeetings.testexample.de
ServerAdmin r...@testexample.de
### OpenMeetings###
## Custom fragment
RewriteEngine On
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://localhost:5080/$1 [P,L]
RedirectMatch ^/$ https://openmeetings.testexample.de/openmeetings
ProxyPreserveHost On
ProxyRequests Off
SSLEngine on
SSLProtocol -all +TLSv1.2 +TLSv1.3
SSLCipherSuite
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
SSLHonorCipherOrder on
ErrorLog /var/log/apache2/error.log
SSLCertificateFile /etc/letsencrypt/testexample.de/fullchain.cer
SSLCertificateKeyFile
/etc/letsencrypt/testexample.de/testexample.de.key
Require all granted
ProxyPass http://localhost:5080/openmeetings
ProxyPassReverse http://localhost:5080/openmeetings
RewriteEngine On
RewriteRule ^/(.*) http://localhost:5080/$1 [P]
Require all granted
ProxyPass http://localhost:5080/open
ProxyPassReverse http://localhost:5080/open
Require all granted
ProxyPass http://localhost:5080/send
ProxyPassReverse http://localhost:5080/send
Require all granted
ProxyPass http://localhost:5080/idle
ProxyPassReverse http://localhost:5080/idle
Require all granted
ProxyPass http://localhost:5080/close
ProxyPassReverse http://localhost:5080/close
