Alebbo 0 Posted November 17, 2020 Share Posted November 17, 2020 (edited) Hello people, i have emby running on a docker container on my raspberry pi 4 for quite some time now. I like it a lot. Yesterday I subscribed to emby premiere in order to be able to stream to my phone, when i am away from home. However i was unable to get it to work. I will provide as much information as i can... I should also mention that i am running a nextcloud container as well, which is working well. here is my container config: i added the 8920 port yesterday. My emby network settings are as follows: here i find it weird that only http protocol is displayed, but nothing about https, even though i set the "required for all remote connections". so i tried to inspect the network activity. The network interfaces are routable: The 8920 port is being listened to: Where i call the domain sub.mydomain.com:8920 i get an "ERR_CONNECTION_REFUSED", so i look at tcpdump and see this: it does look normal, doesn't it? My iptables shows: The emby server log is attached. As far as i can tell (according to timestamps), nothing is getting logged when i try to open the url. I hope somebody can help with this Thank you embyserver.txt Edited November 17, 2020 by Alebbo added info Link to comment Share on other sites More sharing options...
Luke 36879 Posted November 19, 2020 Share Posted November 19, 2020 I think your certificate is failing to load. Can you connect remotely with plain http on the http port? Link to comment Share on other sites More sharing options...
Alebbo 0 Posted November 19, 2020 Author Share Posted November 19, 2020 It is not possible to connect via http unfortunatley. The Browser keeps redirecting to https, even though I disables secure connections in emby This is what the browser shows after redirecting from http://sub.domain.dev:8096 to https://sub.domain.dev:8096 here are the permissions for the certificate which is located in /etc/letsencrypt/live/sub.domain.dev/ : Link to comment Share on other sites More sharing options...
Luke 36879 Posted November 19, 2020 Share Posted November 19, 2020 Try restarting the server after doing that. If it's still happening then you must have something else causing the redirect. Link to comment Share on other sites More sharing options...
Alebbo 0 Posted November 19, 2020 Author Share Posted November 19, 2020 yeah, it is still happening... do you mean something else on the server side of things? or my browser? i tried 4 different browsers, deleted dns cache in my OS, disabled https redirects in firefox and chrome. Nothing works. So could be something in the emby server config? Is there something there i could look into? As mentioned i have a nextcloud container running with apache, but that only listens to ports 80, 443 and 4443. Thanks for the support so far Luke Link to comment Share on other sites More sharing options...
Luke 36879 Posted November 19, 2020 Share Posted November 19, 2020 If you have a reverse proxy it could be there. Link to comment Share on other sites More sharing options...
Alebbo 0 Posted November 19, 2020 Author Share Posted November 19, 2020 is the connection over http needed in order to get https to work? i dont really care about the http... Link to comment Share on other sites More sharing options...
Luke 36879 Posted November 19, 2020 Share Posted November 19, 2020 It's a useful test to help narrow down general connectivity problems vs problems with your certificate. Link to comment Share on other sites More sharing options...
Alebbo 0 Posted November 19, 2020 Author Share Posted November 19, 2020 are there other tests that one can do since this one does not want to work Link to comment Share on other sites More sharing options...
Luke 36879 Posted November 20, 2020 Share Posted November 20, 2020 I would suggest checking out our connection troubleshooter: https://support.emby.media/support/solutions/articles/44001849007-connectivity Please try the steps listed there and let us know which ones succeed and which ones do not. Thanks ! Link to comment Share on other sites More sharing options...
Alebbo 0 Posted November 20, 2020 Author Share Posted November 20, 2020 i got the http thing to work by changing the network in docker from bridge to host! Now i can visit emby remotley with myip:8096 The current problem is that Emby is not listening to port 8920, only 8096 is working. I set the ports in the Emby settings... Link to comment Share on other sites More sharing options...
Solution Q-Droid 609 Posted November 20, 2020 Solution Share Posted November 20, 2020 (edited) Ownership and permissions show user emby can't open the cert file. Also path to cert looks different. Edited November 20, 2020 by Q-Droid Link to comment Share on other sites More sharing options...
Alebbo 0 Posted November 20, 2020 Author Share Posted November 20, 2020 This was it. I changed the permissions from root to the emby user and now everything is fine. Would you recommend protecting the p12 file with a password? I plan to keep the file in it's current location only... Thank you both for your help Link to comment Share on other sites More sharing options...
Q-Droid 609 Posted November 21, 2020 Share Posted November 21, 2020 Yes, as good practice you should have a password on the p12 and Emby has a field for this. 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