totalhavoc 13 Posted November 14, 2015 Posted November 14, 2015 I can not get the new app to connect to my server using SSL. I type "https://my.server.com" and port 8920 and I get an error about a connection failure. http on port 8096 works but I don't want to send login info unencrypted when outside of my network which is when I would want to use an ios device. Any ideas?
fc7 123 Posted November 14, 2015 Posted November 14, 2015 If you are using a selfsigned certificate on your server you must install it also on your iOS device so it will trust it. That is the first thing. However it's still possible that even after doing that it may not work since I'm not sure how mature is the iOS app ssl client implementation right now but to make you iOS device trust your server certificate is mandatory to avoid other issues like playback over ssl. Sent from my iPad using Tapatalk
fc7 123 Posted November 14, 2015 Posted November 14, 2015 I just tested it and SSL works fine from the iOS app but your device MUST trust your server certificate plus your server certificate common name or any alternative names MUST match the hostname that you are using in your connection config. So using your example the certificate CN must be "my.server.com" if it doesn't or this hostname is not included in any of the alternative names of your server certificate the the SSL handshake will fail. This is not related to the app at all but to how ssl works. Bottom line SSL is supported in the iOS app and it works fine but you just need to understand ssl requirements and how it works since it may not work for you out of the box. PS: I'm not using Emby self-signed certificate but a certificate issued by a CA that all my iOS devices trust. Using Emby self-signed certificate can be more problematic. When I find some time I will dig into it and try to come up with some configuration steps. Sent from my iPad using Tapatalk 2
Luke 42077 Posted November 14, 2015 Posted November 14, 2015 I just tested it and SSL works fine from the iOS app but your device MUST trust your server certificate plus your server certificate common name or any alternative names MUST match the hostname that you are using in your connection config. So using your example the certificate CN must be "my.server.com" if it doesn't or this hostname is not included in any of the alternative names of your server certificate the the SSL handshake will fail. This is not related to the app at all but to how ssl works. Bottom line SSL is supported in the iOS app and it works fine but you just need to understand ssl requirements and how it works since it may not work for you out of the box. PS: I'm not using Emby self-signed certificate but a certificate issued by a CA that all my iOS devices trust. Using Emby self-signed certificate can be more problematic. When I find some time I will dig into it and try to come up with some configuration steps. Sent from my iPad using Tapatalk Let me know because I'm going to be working on a wiki for the app. Thanks.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now