Jump to content


Photo
* * * * * 1 votes

Chromecast problem


  • Please log in to reply
49 replies to this topic

#41 Sp3kt3r OFFLINE  

Sp3kt3r

    Advanced Member

  • Alpha Testers
  • 146 posts
  • Local time: 01:09 AM
  • LocationCanada

Posted 28 February 2019 - 07:21 PM

 

Try this: https://stackoverflo...0445432/1972101

 

On linux/mac commands should be the same, but just be openssl ...whatever... instead of C:\Openssl\bin\openssl.exe

Once you've got the cert, you'll need to put it onto the server OR a network path that you can access via emby.


EDIT:

The last comment on that stackoverflow claims it's doable in two steps.. haven't tested.
 

openssl req -x509 -sha256 -nodes -days 3650 -newkey rsa:4096 -keyout mykey.key -out mypem.pem

openssl pkcs12 -export -out myp12.p12 -inkey mykey.key -in mypem.pem

 

I had the same issue and just found this thread... and Thx ! this was easy and its work...

 

Just need to install the openSSL from http://slproweb.com/...n32OpenSSL.html , I used the version  Win64 OpenSSL v1.1.1b Light

Once installed, I used the 2 step provided from stackoverflow and it works.

 

UPDATE: I spoke to fast, the custom SSL works fine, I can see my chromecast but I can't play anything, when I click the PLAY button it doesn't do anything.

I rebooted my emby server and chromecast.

 

I will continue investigation and look at the log.


Edited by Sp3kt3r, 01 March 2019 - 02:27 PM.


#42 Netbug OFFLINE  

Netbug

    Advanced Member

  • Members
  • 233 posts
  • Local time: 01:09 AM

Posted 01 March 2019 - 05:38 PM

I've mentioned it earlier, but for me cert generation is built into my router, so I'm not sure how much help I can provide.. I'll see if I can track down some linkage.

Within emby, when managing the server -- on the 'Expert > Advanced' settings form, you must tick the box to enable remote connections so that you can provide your custom self-signed cert. 

5c783a6f7c511_ScreenShot20190228at14519P

5c783a8d60e98_ScreenShot20190228at14600P

I think it'll also require that you populate the "External Domain" field, but if you're not going to actually forward external traffic to the emby server, what you put there isn't entirely important as far as I can figure.

Once you've done that, you simply access your server via the https port, 8920 by default... so for me, I hit: https://emby:8920/web/index.html

This is extremely helpful. Thank you.

 

I'm stuck at what is probably a simple point though; where do I place the file on my server? I grew up in a windows environment, so I can't figure out which directory I need to put the certificate in.



#43 willvincent OFFLINE  

willvincent

    Member

  • Members
  • 17 posts
  • Local time: 12:09 AM

Posted 01 March 2019 - 07:32 PM

This is extremely helpful. Thank you.

 

I'm stuck at what is probably a simple point though; where do I place the file on my server? I grew up in a windows environment, so I can't figure out which directory I need to put the certificate in.

Anywhere really.. emby provides a file picker in the ui so that you can navigate to and select the file.. so anywhere accessible is sufficient.

Easiest would be in your home directory `/home/your_user_name`



#44 Netbug OFFLINE  

Netbug

    Advanced Member

  • Members
  • 233 posts
  • Local time: 01:09 AM

Posted 02 March 2019 - 11:08 AM

Anywhere really.. emby provides a file picker in the ui so that you can navigate to and select the file.. so anywhere accessible is sufficient.

Easiest would be in your home directory `/home/your_user_name`

 

Got it. I can access it now, and Chromecast shows up, but for some reason, it won't actually cast. No error, just won't cast. Seems to be the same issue that Sp3ct3r is having.



#45 willvincent OFFLINE  

willvincent

    Member

  • Members
  • 17 posts
  • Local time: 12:09 AM

Posted 02 March 2019 - 06:36 PM

Hmm... so the only significant difference I can think of is that for my cert I first made a custom signing cert for my internal network, and signed with that. Could be that makes a difference.

All of that too was through my OPNsense router, but here's info about doing it manually: https://deliciousbra...ps-development/

 

As much of a hassle as all of this is, the better solution might be to get a device other than a chromecast that is less particular about how you can use it. There have to be other options that are easier to work with


Edited by willvincent, 02 March 2019 - 06:38 PM.


#46 Netbug OFFLINE  

Netbug

    Advanced Member

  • Members
  • 233 posts
  • Local time: 01:09 AM

Posted 03 March 2019 - 08:37 AM

Hmm... so the only significant difference I can think of is that for my cert I first made a custom signing cert for my internal network, and signed with that. Could be that makes a difference.

All of that too was through my OPNsense router, but here's info about doing it manually: https://deliciousbra...ps-development/

 

As much of a hassle as all of this is, the better solution might be to get a device other than a chromecast that is less particular about how you can use it. There have to be other options that are easier to work with

 

You're right. This is getting mighty difficult. I'm thinking I might just use it from the devices like my iPad and Android as they seem to continue to function. Might be worth looking in to down the road though.



#47 denkuy OFFLINE  

denkuy

    Newbie

  • Members
  • 2 posts
  • Local time: 06:09 AM

Posted 14 March 2019 - 02:54 PM

I'm currently setting the "unsafely-treat-insecure-origin-as-secure" flag in chrome so that I can use my chromecast with a local server without https

 

- go to chrome://flags/#unsafely-treat-insecure-origin-as-secure

- enable unsafely-treat-insecure-origin-as-secure

- add http://<EMBY_SERVER_IP>:8096

- restart browser


Edited by denkuy, 14 March 2019 - 02:55 PM.


#48 z3ndra OFFLINE  

z3ndra

    Advanced Member

  • Members
  • 90 posts
  • Local time: 07:09 AM

Posted 14 March 2019 - 04:38 PM

finally it's so easy to create a certificate for Emby, I can make a tuto on ubuntu if you want



#49 z3ndra OFFLINE  

z3ndra

    Advanced Member

  • Members
  • 90 posts
  • Local time: 07:09 AM

Posted 14 March 2019 - 05:28 PM

Tutorial make emby to https

I make that under Ubuntu and with a fix ip, but if you have a dynamic ip, get a dds (dynamic domain name) make sure  that you are root on your server, with this command : sudo -i

  1. it is imperative that you obtain a domain name
  2. redirect your domain name to your server, for that go to the dns parameter and create a record and enter the IP address of your server.

3 ) make sure that there is not a single iptables rule that concerns port 80, which is very important for lets encrypt get certified to your domain name. Verify with : iptables -L -t nat --line-number

  1. Install  open ssl on your server with the command : apt-get install openssl
  2. Install let’s encrypt a free certificate for that, place you in the root folder with : cd /root/

And install let’s encrypt with :

git clone https://github.com/l...ypt/letsencrypt

install git if install if this is not the case with : apt-get git

  1. Place you in the let’s encrypt folder with : cd letsencrypt
  2. Generate your certificate with : ./letsencrypt-auto --server https://acme-v01.api...t.org/directory certonly
  3. choose the choice 1, enter your mail address and accept conditions and enter your domain name and valid
  4. go to the folder : cd /  /etc/letsencrypt/live/mydomainname.xx/ (replace mydomainname.xx to your domain name of course)
  5. (There you will find 3 files : cert.pem  chain.pem  fullchain.pem  privkey.pem
  6. Convert this files to pfx for compatible with emby with : openssl pkcs12 -export -out mydomain.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem -password pass:
  7. move this file to the opt / emby-server / ssl folder
  8. in emby : enter your domain name, selec your certificate and choose “required for all connections” in secure connection mode
  9. redirect your ports 443 and 80 with : iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 8920
  10. and  : iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8096
  11. restart your server


#50 willvincent OFFLINE  

willvincent

    Member

  • Members
  • 17 posts
  • Local time: 12:09 AM

Posted 14 March 2019 - 10:24 PM

I'm currently setting the "unsafely-treat-insecure-origin-as-secure" flag in chrome so that I can use my chromecast with a local server without https

 

- go to chrome://flags/#unsafely-treat-insecure-origin-as-secure

- enable unsafely-treat-insecure-origin-as-secure

- add http://<EMBY_SERVER_IP>:8096

- restart browser

 

Seems nice and easy, but doesn't work for me. Thus all the hoop jumping.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users