I'll try to reproduce this
please ping me if I will be too silent :)

On Thu, Apr 2, 2015 at 9:50 PM, FJ <[email protected]> wrote:

> Maxim, yes.  I see 2 trusted cert key and 1 private key.
>
> On Thu, Apr 2, 2015 at 2:07 AM, Maxim Solodovnik <[email protected]>
> wrote:
>
>> can you list the keys using new password?
>> keytool -keystore keystore.jks --list
>>
>> On Wed, Apr 1, 2015 at 12:24 AM, FJ <[email protected]> wrote:
>>
>>> Maxim, when I change the pw from the command: keytool -keypasswd  -alias
>>> red5 -keystore keystore.jks and i put new password in the red5.properties,
>>> I can no longer connect
>>>
>>> # RTMPS Key and Trust store parameters
>>> rtmps.keystorepass=123456
>>> rtmps.keystorefile=conf/keystore.jks
>>> rtmps.truststorepass=123456
>>> rtmps.truststorefile=conf/keystore.jks
>>>
>>> On Tue, Mar 31, 2015 at 10:58 AM, Maxim Solodovnik <[email protected]
>>> > wrote:
>>>
>>>> nope, it also hardcoded
>>>>
>>>> On Tue, Mar 31, 2015 at 11:56 PM, FJ <[email protected]> wrote:
>>>>
>>>>> Ok.. I will do that. Does the keystore.screen file need to be anywhere
>>>>> in any of the configuration file?
>>>>>
>>>>> On Tue, Mar 31, 2015 at 10:41 AM, Maxim Solodovnik <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> real url might be not a big deal
>>>>>> password need to be changed
>>>>>>
>>>>>> On Tue, Mar 31, 2015 at 11:38 PM, FJ <[email protected]> wrote:
>>>>>>
>>>>>>> Oh no Maxim, I just mask out the real url and keystore password.
>>>>>>>
>>>>>>> On Tue, Mar 31, 2015 at 9:45 AM, Maxim Solodovnik <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> somehow connection URL is bad:
>>>>>>>> rtmp://om.sample.com:7443/openmeetings/2
>>>>>>>> should be
>>>>>>>> *rtmps*://om.sample.com:7443/openmeetings/2
>>>>>>>> seems to be configuration issue :(((
>>>>>>>>
>>>>>>>> to file JIRA issue
>>>>>>>> 1) go to: https://issues.apache.org/jira/browse/OPENMEETINGS
>>>>>>>> 2) login/create account
>>>>>>>> 3) select "Create" button and create new issue
>>>>>>>> Thanks in advance :)
>>>>>>>>
>>>>>>>> On Tue, Mar 31, 2015 at 10:39 PM, FJ <[email protected]> wrote:
>>>>>>>>
>>>>>>>>> Sure, I have never done one before.  Can direct to where?
>>>>>>>>>
>>>>>>>>> In the meantime, you see any clues from the log why it doesn't
>>>>>>>>> share when I click on start share?
>>>>>>>>>
>>>>>>>>> On Tue, Mar 31, 2015 at 9:29 AM, Maxim Solodovnik <
>>>>>>>>> [email protected]> wrote:
>>>>>>>>>
>>>>>>>>>> My bad,
>>>>>>>>>>
>>>>>>>>>> The password should be the same
>>>>>>>>>> could you please file JIRA issue, I'll fix it and will update
>>>>>>>>>> documentation
>>>>>>>>>> sorry
>>>>>>>>>>
>>>>>>>>>> On Tue, Mar 31, 2015 at 9:37 PM, FJ <[email protected]>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Here it is Maxim.  Also in the log, I notice it uses my keystore
>>>>>>>>>>> password and not the keystore.screen password you mentioned in the 
>>>>>>>>>>> prior
>>>>>>>>>>> emails.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Mar 31, 2015 at 6:14 AM, Maxim Solodovnik <
>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> can you check screenshare.log file? (usually in HOME folder of
>>>>>>>>>>>> the client running screensharing app)
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Mar 31, 2015 at 12:54 PM, FJ <[email protected]>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Maxim.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I rebuild my OM from scratch so I can document the work
>>>>>>>>>>>>> instruction.  I get this error below when I try to screen share.  
>>>>>>>>>>>>> Can you
>>>>>>>>>>>>> help?  I click on start sharing and does not do anything,  This 
>>>>>>>>>>>>> is in
>>>>>>>>>>>>> RTMPS/HTTPS configuration.  I renamed my keystore.jks to 
>>>>>>>>>>>>> keystore.screen
>>>>>>>>>>>>> with another password.
>>>>>>>>>>>>>
>>>>>>>>>>>>> ERROR 03-30 23:51:13.980 158 o.r.s.s.ServiceInvoker
>>>>>>>>>>>>> [ThreadPoolTaskExecutor-1] - Method setId with parameters [41] 
>>>>>>>>>>>>> not found in
>>>>>>>>>>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare@9b1432
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thank you in advance.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Mar 24, 2015 at 8:20 PM, Maxim Solodovnik <
>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> you can google it :))
>>>>>>>>>>>>>> http://stackoverflow.com/questions/2889238/keystore-change-passwords
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Mar 25, 2015 at 9:12 AM, FJ <[email protected]>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Maxim, I the followed the exact WI(work instruction) on the
>>>>>>>>>>>>>>> on the link. My keystore file is keystore.jks.  So want to do a 
>>>>>>>>>>>>>>> "cp
>>>>>>>>>>>>>>> keystore.jks keystore.screen"  How do the I change the password 
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>> keystore.screen?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Mar 24, 2015 at 8:06 PM, Maxim Solodovnik <
>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> please follow this instruction:
>>>>>>>>>>>>>>>> http://openmeetings.apache.org/RTMPSAndHTTPS.html
>>>>>>>>>>>>>>>> for testing you can just copy red5/conf/keystore to
>>>>>>>>>>>>>>>> red5/conf/keystore.screen, but in this case you will send 
>>>>>>>>>>>>>>>> password
>>>>>>>>>>>>>>>> unencrypted, so for production I would recommend to change 
>>>>>>>>>>>>>>>> password for
>>>>>>>>>>>>>>>> this keystore or to create separate keystore
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Mar 25, 2015 at 9:00 AM, FJ <[email protected]>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> You are correct Maxim.  I don't have the file you
>>>>>>>>>>>>>>>>> mentioned.  Do I need that and where would I get it?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Mar 24, 2015 at 7:48 PM, Maxim Solodovnik <
>>>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> It seems you are using secure version (RTMPS)
>>>>>>>>>>>>>>>>>> do you have red5/conf/keystore.screen file in your
>>>>>>>>>>>>>>>>>> system?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Wed, Mar 25, 2015 at 7:24 AM, FJ <
>>>>>>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I can't seem to get Screen Share to work. It pops up
>>>>>>>>>>>>>>>>>>> asking to run and when I clean it does it things 
>>>>>>>>>>>>>>>>>>> downloading, verifying and
>>>>>>>>>>>>>>>>>>> nothing after that.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Below is the "ERROR" shown in the "screensharing" file
>>>>>>>>>>>>>>>>>>> that it saved on the desktop.  Is the a particular java 
>>>>>>>>>>>>>>>>>>> version the client
>>>>>>>>>>>>>>>>>>> side that works best with OM3.0.4?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Any advice would be great.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thank you all in advance.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> ERROR 03-24 18:17:04.160 176 o.a.o.s.w.CoreScreenShare
>>>>>>>>>>>>>>>>>>> [javawsApplicationMain] -
>>>>>>>>>>>>>>>>>>> org.apache.commons.codec.DecoderException: Odd number of
>>>>>>>>>>>>>>>>>>> characters.
>>>>>>>>>>>>>>>>>>>     at
>>>>>>>>>>>>>>>>>>> org.apache.commons.codec.binary.Hex.decodeHex(Hex.java:82)
>>>>>>>>>>>>>>>>>>> ~[commons-codec-1.9.jar:na]
>>>>>>>>>>>>>>>>>>>     at
>>>>>>>>>>>>>>>>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare.<init>(CoreScreenShare.java:155)
>>>>>>>>>>>>>>>>>>> [openmeetings-screenshare-3.0.4-RELEASE.jar:na]
>>>>>>>>>>>>>>>>>>>     at
>>>>>>>>>>>>>>>>>>> org.apache.openmeetings.screen.webstart.CoreScreenShare.main(CoreScreenShare.java:181)
>>>>>>>>>>>>>>>>>>> [openmeetings-screenshare-3.0.4-RELEASE.jar:na]
>>>>>>>>>>>>>>>>>>>     at
>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>>>>>>>>>>>>>>>>>>> ~[na:1.8.0_40]
>>>>>>>>>>>>>>>>>>>     at
>>>>>>>>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
>>>>>>>>>>>>>>>>>>> ~[na:1.8.0_40]
>>>>>>>>>>>>>>>>>>>     at
>>>>>>>>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown 
>>>>>>>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>>>>>>> ~[na:1.8.0_40]
>>>>>>>>>>>>>>>>>>>     at java.lang.reflect.Method.invoke(Unknown Source)
>>>>>>>>>>>>>>>>>>> ~[na:1.8.0_40]
>>>>>>>>>>>>>>>>>>>     at
>>>>>>>>>>>>>>>>>>> com.sun.javaws.Launcher.executeApplication(Unknown Source) 
>>>>>>>>>>>>>>>>>>> [na:na]
>>>>>>>>>>>>>>>>>>>     at com.sun.javaws.Launcher.executeMainClass(Unknown
>>>>>>>>>>>>>>>>>>> Source) [na:na]
>>>>>>>>>>>>>>>>>>>     at com.sun.javaws.Launcher.doLaunchApp(Unknown
>>>>>>>>>>>>>>>>>>> Source) [na:na]
>>>>>>>>>>>>>>>>>>>     at com.sun.javaws.Launcher.run(Unknown Source)
>>>>>>>>>>>>>>>>>>> [na:na]
>>>>>>>>>>>>>>>>>>>     at java.lang.Thread.run(Unknown Source) [na:1.8.0_40]
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> WBR
>>>>>>>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> WBR
>>>>>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> WBR
>>>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> WBR
>>>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> WBR
>>>>>>>>>> Maxim aka solomax
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> WBR
>>>>>>>> Maxim aka solomax
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> WBR
>>>>>> Maxim aka solomax
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> WBR
>>>> Maxim aka solomax
>>>>
>>>
>>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>


-- 
WBR
Maxim aka solomax

Reply via email to