https plackback in ios safari

[acnp77 61]

Hi

I want to use https for away from home playback. I do not use emby connect. I have forwarded the port 8920 (tcp) and I use the default self-signed cert. (I did not do anything, assume this is setup)

I can connect to the dashboard from outside my network using my external ip. but as soon as i want to play a movie I get a plackback error. Same with music.

 

Does ios safari use a external player? and do I have to import an api key into the ext. player ?

 

If yes, HOW???

 

CHEERS

 

EDIT:

I found this in the logs:

"PublicHttpsPort":8920,"HttpServerPortNumber":8096,"HttpsPortNumber":8920,"EnableHttps":false,"CertificatePath":"",

Edited November 9, 2016 by acnp77

[tigrao 18]

I had the same problem until I started using a trusted SSL certificate.  I believe a trusted SSL cert is the only way to achieve https playback in iOS.

[acnp77 61]

I had the same problem until I started using a trusted SSL certificate.  I believe a trusted SSL cert is the only way to achieve https playback in iOS.

thanks for sharing I will try this... but not my favorite approach.

[acnp77 61]

@@Luke

do I really need a trusted cert in ios? if yes- why?

I have quite a few servers running and my own domainname. All other services run on self-signed certs (also no problems on ios clients) as there is no logical need for a trusted one. (Only myself and family use it).

Ios can accept self-signed certs in general.

 

please help. I love ur product but if I can not get secure "away from home" access with ios clients I simply can not use it.

I checked other posts and wiki, but no answers to this problem

 

cheers

 

EDIT:

I have setup an openvpn-server (routed, not bridged). For myself on my ios devices I use emby with the openvpn client. works very nicely. But this is not for other users.

Edited November 9, 2016 by acnp77

[acnp77 61]

I installed a "let's encrypt" certificate. Not 100% sure how, but I actually got it installed and running on debain 8

Now IOS Clients work very well.

[tigrao 18]

I used a lets encrypt certificate too.  It's been working great for me.

[acnp77 61]

what I do not understand is: I stream from outside my network (https, ios safari) and in emby-server-dashboard it says "direct playing". ???

How can it "direct play" when the network resources (my movie file) are not accessible from outside the network?

[tigrao 18]

I think in that case Emby becomes basically a proxy server. It just reads the file and transfers the data via http(s) packets. It isn't doing any transcoding, just packetizing the data and sending it to the client.

[Happy2Play 8326]

If the browser supports the codecs, the container and have the upload speed, then yes you could get direct play outside your network.

[acnp77 61]

I think in that case Emby becomes basically a proxy server. It just reads the file and transfers the data via http(s) packets. It isn't doing any transcoding, just packetizing the data and sending it to the client.

 

Yes, that is the case. Even if no transcoding or demuxing is required the stream needs go through MB-Server which will create the https-stream. And that makes sense, as the network share with the media-files is not (or at least should not be) accessible from outside the network. But this is not called "Direct play". "Direct play" means that the client can access the server-resources directly.

 

It's all good. The only problem is that MB-Server shows "Direct playing" when this is obviously not possible to be "Direct playing".

 

Cheers

[acnp77 61]

If the browser supports the codecs, the container and have the upload speed, then yes you could get direct play outside your network.

My network-shares are not accessible from outside the network- so no, it could not be "Direct playing".

 

[Happy2Play 8326]

You would need to look at the log to see how the file is being delivered.

[ebr 14947]

My network-shares are not accessible from outside the network- so no, it could not be "Direct playing".

 

 

Yeah, as soon as the competition is that accurate in its definitions, we will go back to that as well.  Since we all just made up these terms in the first place, I guess there is wiggle room in what they actually mean.

[Luke 37167]

I installed a "let's encrypt" certificate. Not 100% sure how, but I actually got it installed and running on debain 8

Now IOS Clients work very well.

 

Including the app or just the browser?

[acnp77 61]

Including the app or just the browser?

 Just the browser. I can test the app too if this helps.

[Luke 37167]

Yea please try it out, thanks.

[acnp77 61]

Yea please try it out, thanks.

Just installed the app under ios 10.1.1. The app displays posters correctly too. Seems all good. Only problem was in ios 9.x.x. in browser.

 

EDIT:

Sorry got somthing mixed-up here... You wanted to know about the app streaming in ios with let's encrypt cert...

 

I just tried it and it works fine after a short test.

Seems the "let's encrypt" certificate works with emby in safari-browser and emby app. I could stream a movie over the internet with https in both safari and app.

Edited November 11, 2016 by acnp77

[Luke 37167]

In terms of https, the issue is that we are using WkWebView and Apple does not currently provide an API to override the rejection of self-signed certs. There is an open ticket about it in the Webkit issue tracker so unfortunately we just have to wait.

[acnp77 61]

In terms of https, the issue is that we are using WkWebView and Apple does not currently provide an API to override the rejection of self-signed certs. There is an open ticket about it in the Webkit issue tracker so unfortunately we just have to wait.

Thanky for sharing Fortunatly the "let's encrypt" certificate works for emby (on both safari and app) and is very easy to setup.