sscheib 11 Posted February 15, 2018 Author Share Posted February 15, 2018 @@Luke I completely opened my firewall to see if that helps - no it doesnt. Any ideas? Link to comment Share on other sites More sharing options...
Luke 37009 Posted February 16, 2018 Share Posted February 16, 2018 For simplicity's sake, can you test this over http and offer comparison results? Link to comment Share on other sites More sharing options...
sscheib 11 Posted May 21, 2018 Author Share Posted May 21, 2018 Hello @@Luke, I just wanted to try out the new emby google home app and it turns out that won't work as well. When trying to select a default player (which happens when starting the app the first time) it will tell me: I could not find any Emby player available. Make sure the player you want to use is logged in with or available to your Emby account. Still: I am guessing this is something buggy on your end when using custom (valid! - LetsEncrypt) SSL certificates Have you ever tried to reproduce this error on your end? I am absolutly not willing to transfer any content over HTTP. Thank you very much. Regards, Steffen Link to comment Share on other sites More sharing options...
Luke 37009 Posted May 21, 2018 Share Posted May 21, 2018 Yes I've test remote control over https constantly and haven't seen any problems. @@pir8radio would you concur? Link to comment Share on other sites More sharing options...
pir8radio 1292 Posted May 21, 2018 Share Posted May 21, 2018 (edited) Yes I've test remote control over https constantly and haven't seen any problems. @@pir8radio would you concur? Dunno, I run https, through two reverse proxies, and remote control works for me. In this demo, my server is in a data center, the screen on the left is my office desktop, and the screen on the right is my home theater PC through teamviewer (three different locations between remote, server, and client). You can see that remote control works with FireTv (image below might take a second to load up) @@sscheib , add this to your nginx config and see if anything changes: proxy_connect_timeout 1h; proxy_send_timeout 1h; proxy_read_timeout 1h; Edited May 22, 2018 by pir8radio Link to comment Share on other sites More sharing options...
pir8radio 1292 Posted June 1, 2018 Share Posted June 1, 2018 Hello @@Luke, I just wanted to try out the new emby google home app and it turns out that won't work as well. When trying to select a default player (which happens when starting the app the first time) it will tell me: I could not find any Emby player available. Make sure the player you want to use is logged in with or available to your Emby account. Still: I am guessing this is something buggy on your end when using custom (valid! - LetsEncrypt) SSL certificates Have you ever tried to reproduce this error on your end? I am absolutly not willing to transfer any content over HTTP. Thank you very much. Regards, Steffen See this post: https://emby.media/community/index.php?/topic/59498-34110-web-socket/?p=583364 Do you still have the remote control issue when using this beta? Link to comment Share on other sites More sharing options...
sscheib 11 Posted July 26, 2018 Author Share Posted July 26, 2018 @pir8radio: I havent tried this beta, however tried the release 3.5.1.0 - is this fixing the issue as well? (@Luke) Link to comment Share on other sites More sharing options...
Luke 37009 Posted July 27, 2018 Share Posted July 27, 2018 To be fair I was never considering it an issue, rather something in your setup causing it to drop. But yes please try it. Thanks. Link to comment Share on other sites More sharing options...
sscheib 11 Posted August 1, 2018 Author Share Posted August 1, 2018 Alright, I finally found the issue (in case anybody ever has the same problem). Appearently ICMP needs to be enabled on the server for this feature to work - dropping ICMP packets via iptables will result in the function not working (besides using a Chromecast). Link to comment Share on other sites More sharing options...
Luke 37009 Posted August 1, 2018 Share Posted August 1, 2018 Thanks for the feedback. Link to comment Share on other sites More sharing options...
pir8radio 1292 Posted August 2, 2018 Share Posted August 2, 2018 (edited) Alright, I finally found the issue (in case anybody ever has the same problem). Appearently ICMP needs to be enabled on the server for this feature to work - dropping ICMP packets via iptables will result in the function not working (besides using a Chromecast). Humm I block ICMP and it works for me.. Strange. Edited August 2, 2018 by pir8radio Link to comment Share on other sites More sharing options...
sscheib 11 Posted August 2, 2018 Author Share Posted August 2, 2018 (edited) ... or it was the last version fixing this issue. Let me quickly try blocking ICMP. //EDIT Alright, seems to be the last version fixing this issue. Dropping ICMP works just fine. Edited August 2, 2018 by sscheib 1 Link to comment Share on other sites More sharing options...
pir8radio 1292 Posted August 2, 2018 Share Posted August 2, 2018 ... or it was the last version fixing this issue. Let me quickly try blocking ICMP. //EDIT Alright, seems to be the last version fixing this issue. Dropping ICMP works just fine. Cool, thanks for the update! Link to comment Share on other sites More sharing options...
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