INTERACT FORUM

Devices => Androids and other portables => Topic started by: hoyt on July 28, 2019, 10:55:46 pm

Title: JRiver for Android: SSL Support
Post by: hoyt on July 28, 2019, 10:55:46 pm
I saw this in the recent change logs, so I have to ask..

Any chance of this coming to JRemote, Gizmo and the Id?  You introduced SSL support in MC23, yet it's not propagated through your ecosystem yet.

https://yabb.jriver.com/interact/index.php/topic,110982.0.html
https://yabb.jriver.com/interact/index.php/topic,116664.msg807229.html#msg807229
https://yabb.jriver.com/interact/index.php/topic,116796.msg807663.html#msg807663
Title: Re: JRiver for Android: SSL Support
Post by: bob on July 29, 2019, 02:44:37 pm
We'll take a look at adding that to JRemote, shouldn't be too difficult.
What's not working on the Id?
Title: Re: JRiver for Android: SSL Support
Post by: hoyt on July 29, 2019, 05:54:16 pm
We'll take a look at adding that to JRemote, shouldn't be too difficult.
What's not working on the Id?

Thanks!

I haven't tried in a while, I can later tonight perhaps.  When I tried to connect my IdPi to my MC on Windows through 52200, it eventually timed out.  I actually have not tried since MC25 was pushed to it, so that's not a bad point to retest it.

Looking back at my prior post, it appears I even tried to do a secure connection to the MC "Outside Id" that wouldn't connect.

EDIT: This will need to wait until Friday.  I just turned the firewall on remotely on my MC server and killed my remote connection - oops.  It looked like just now that my IdPi connected to 52200, but I was going to block 52199 on my server again to validate this.  Should have checked what else was on that firewall.  I won't be able to get back on that network to disable the firewall until the end of the week.
Title: Re: JRiver for Android: SSL Support
Post by: bob on July 30, 2019, 09:41:32 am
Ok, thanks for testing it!
Title: Re: JRiver for Android: SSL Support
Post by: hoyt on August 03, 2019, 07:10:37 pm
Ok, thanks for testing it!

I finally got back in and everything setup in a way to test this.  I can confirm that I'm now able to connect to my server from the IdPi via 52200 with 52199 blocked on the MC server end.  So all seems well with the IdPi!