openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Hill (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENMEETINGS-500) Unable to ssl connect to openmeetings
Date Wed, 09 Jan 2013 16:38:13 GMT

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548654#comment-13548654
] 

Brian Hill commented on OPENMEETINGS-500:
-----------------------------------------

Again, I would appreciate it if you could be more specific. 
Please respond with the URL / port you were able to use for an SSL-enabled OpenMeetings installation
(probably in the form of https://192.168.XXX.XXX:YYYY).
It is somewhat surprising that you use Openmeetings with SSL for an Intranet implementation.
But then ...
As stated in my original message, the URL containing those RTMPS/HTTPS instructions (see above)
contains several dependencies such as:
    1) It declares two JKS repositories (keystore and keystore.screen) without providing functional
distinction between them
    2) No specific URL (e.g. https://192.168.XXX.XXX:5443/openmeetings) is provided for RTMPS
/ HTTPS connection

    
                
> Unable to ssl connect to openmeetings
> -------------------------------------
>
>                 Key: OPENMEETINGS-500
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-500
>             Project: Openmeetings
>          Issue Type: Bug
>            Reporter: Brian Hill
>            Assignee: Maxim Solodovnik
>             Fix For: 2.0 Apache Incubator Release
>
>
> I've been trying to secure my installation of Openmeetings2.
> After a couple of attempts based on instructions on the Openmeetings site (http://incubator.apache.org/openmeetings/RTMPSAndHTTPS.html)
official site, I noticed the following errors:
>     a)  org.red5.server.net.rtmps.RTMPSMinaIoHandler - Exception caught SSL handshake
failed
>     b) [Red5_Scheduler_Worker-2] org.red5.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection
from 192.168.X.X #### to null with id # due to long handshake
>    Subsequently, I noticed that the instructions references version 1.9 of Openmeetings
rather than Version 2.0 (which is what I installed). Specifically, this bug which is listed
in openmeetings' changelog (for version 2 that I installed) :
>       [OPENMEETINGS-234] - Video and Screen sharing not working with HTTPS and RTMPS
- Java Application starts but doesnt connect - java trace logs shows "[WARN] [NioProcessor-2]
org.red5.server.net.rtmps.RTMPSMinaIoHandler - Exception caught Keystore or password are null"
>    Some question is:
>     * Is there a way to secure openmeetings 2.0 or should I unsinstall this version and
install 1.9 instead to achieve this  goal?
>     * Is the right RTMPS URL to connect as follows:   https://my_om_server.com:5443/
   ?
>       If not, please advise.
>       Thanks.
>     Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message