[jira] [Created] (OPENMEETINGS-1364) proxy connection problem

["Bruno Rubio (JIRA)" <ji...@apache.org>]

Bruno Rubio created OPENMEETINGS-1364:
-----------------------------------------

             Summary: proxy connection problem
                 Key: OPENMEETINGS-1364
                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1364
             Project: Openmeetings
          Issue Type: Bug
          Components: Cluster
         Environment: CentOS 7, OpenMeetings 3.0.7, clustering mode, rtmpT, proxy
            Reporter: Bruno Rubio
            Assignee: Maxim Solodovnik


First of all, I'm using build #190+ from here: https://builds.apache.org/job/Openmeetings%203.1.x/

I have a clustered OpenMeetings installation (only one node is active for testing) in an intranet forcing the rtmpT connection (port 5080) closing port 1935 at iptables

I need the connection pass through an apache proxy to protect OpenMeetings server.

HTTP connection passes through the proxy without any problem but when I enter one room, connection goes direct between client and server (without passing through the proxy)

I set the config.xml file like this:

<rtmphostlocal>video1t</rtmphostlocal>

<httphostlocal>video1h</httphostlocal>

"video1t" and "video1h" point to the proxy's ip

Proxy server configuration: 

<VirtualHost video1h:5080>
	ServerName video1h
	ServerAlias video1h

	ProxyPreserveHost On
	ProxyPass /openmeetings http://192.168.96.222:5080/openmeetings
	ProxyPassReverse /openmeetings http://192.168.96.222:5080/openmeetings
</VirtualHost>

<VirtualHost video1t:5080>
	ServerName video1t
	ServerAlias video1t

	ProxyPreserveHost On
	ProxyPass /openmeetings http://192.168.96.222:5080/openmeetings
	ProxyPassReverse /openmeetings http://192.168.96.222:5080/openmeetings
</VirtualHost>

"192.168.96.222" is the Openmeetings server's IP

Am I missing something on configuration parameters?

Someone did something like this?

Is there a "howto" explaining the steps for configuring openmeetings through a proxy?

Thanks in advance,



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)