restxp.blogg.se

1. #Access emby server directly from chromecast upgrade
2. #Access emby server directly from chromecast android

I did have a block like that in my configuration, however instead of "/socket" I was using "/embywebsocket" which must have been from an older configuration.

#Access emby server directly from chromecast android

I just successfully tested chromecast with my server and an android phone, and it works correctly. This is because your nginx config is missing the /socket block.

#Access emby server directly from chromecast upgrade

Please let me know what you would like me to gather on 10.5.5 and also on 10.6 after an upgrade to help you diagnose. I don't believe that JF should have to require any http communication when working in a RP setting, but it is clear from the network settings that the RP settings have been removed and I see no other configuration that might control this. I have seen errors like this in multiple places with 10.6, including when trying to get Pushbullet plugin installed and working. I believe that this is a problem, since JF is trying to access my site over http even though I am accessing it over https. However it appears I get messages like when I run in console:Įrror processing request: Unable to find the specified file. While I have reverted to 10.5.5 since you may require working logs as well I don't have complete 10.6 logs of the issue. I can choose the cast receiver, but when I try to press play on the media absolutely nothing happens (it's as if I can't even click the play button). As soon as the upgrade to 10.6 I am unable to cast. These are the only boxes I have filled in and this configuration works properly for all casting in 10.5.5. I have attached the relevant Network settings from my 10.5.5 server. Īll SSL certs are on the NGINX server, and installing them locally on JF doesn't sound like a solution. This simply means all my clients must be instructed to point directly to I access my server both internally and externally over. The only reason it has any effect for me, is I am unable to redirect requests that might hit to since no will ever even hit my proxy. I don't see this as a complication however for clients since most RP proxy users are looking to block all unsecured traffic anyway. The only non-standard thing about my setup is that my ISP blocks port 80, so I am unable to get any http traffic. I run NGINX as RP in what I would consider a mostly standard configuration.

I have/had a working configuration with 10.5.5 using JF to cast to my Chromecast devices, whether those were located internal to my network, or whether it was remote from the JF to another local Chromecast device (i.e. System (please complete the following information):