Premby 0 Posted April 5, 2019 Share Posted April 5, 2019 Hello everyone, I want to reach my emby server through https://my_website.test. Emby is hosted on a dedicated server running ubuntu 18.04 no gui. The server is reachable through his public ip (a.b.c.d). Emby I installed emby headlessly and changed the ports: local http port: 8080 local https port: 4442 public http port: 8992 public https port: 8993 I also added some users and test media files. -> I can reach emby only with the local http port and the public ip/ domain name (a.b.c.d:8080 or my_website.test:8080). When I change the local http port to 80, emby can still only be reached through the port 8080. nginx I installed nginx and followed the instructions of one of the posts here in the forum. SSL First I used Letsencrypt and Certbot to get my SSL certificate, but it seemed it didn't work properly, so I got the SSL certificate through Cloudflare and added the PKCS#12 file to emby aswell as my external domain name (my_webiste.test) -> I added the SSL paths to the nginx config, but still no connection through https. All mentioned ports are unlocked on ufw firewall, aswell as nginx. I hope someone can help me with this mess I created :9... I attached the nginx config file from the /etc/nginx/sites-enabled path. nginx config.txt Link to comment Share on other sites More sharing options...
sargenthp 29 Posted April 5, 2019 Share Posted April 5, 2019 For now let's forget about public access. Are you able to reach these ports on the local network? Or is it just port 8080? Sent from my PH-1 using Tapatalk Link to comment Share on other sites More sharing options...
Premby 0 Posted April 5, 2019 Author Share Posted April 5, 2019 I opened the cli on the server and used links2 to open http://0.0.0.0:8080 and i got access to emby. But i don't know how to check the local network of the server if it isn't part of mine... Link to comment Share on other sites More sharing options...
Premby 0 Posted April 8, 2019 Author Share Posted April 8, 2019 I reached locally on the machine through http://0.0.0.0:8080 and https://0.0.0.0:4442, but with https the site still tell me the connection is insecure. Link to comment Share on other sites More sharing options...
ax3l 7 Posted April 8, 2019 Share Posted April 8, 2019 when trying HTTPS are you hitting by IP or hostname? You probably need to hit it by name on HTTPS Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted April 8, 2019 Share Posted April 8, 2019 ^^ HTTPS matches domain name, not IP. Link to comment Share on other sites More sharing options...
Premby 0 Posted April 9, 2019 Author Share Posted April 9, 2019 Ah ok, so it is normal to get an https error if i use the https://0.0.0.0:4442 to reach emby. If I try https://my_website.test:4442 or even https://my_website.test:8992, I get "The connection has timed out" on the machine emby is installed on. Can anyone tell me how i can reach my goal mentioned far above? Link to comment Share on other sites More sharing options...
Luke 37248 Posted April 9, 2019 Share Posted April 9, 2019 For https you'll need some kind of domain name. Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted April 9, 2019 Share Posted April 9, 2019 what do your server access logs say when you try to connect? Are you even hitting the server? Are your cloudflare settings correct? Link to comment Share on other sites More sharing options...
Premby 0 Posted April 10, 2019 Author Share Posted April 10, 2019 For https you'll need some kind of domain name. I already bought a domain and linked it to my server ip. I got the https certifacte from cloudflare. what do your server access logs say when you try to connect? Are you even hitting the server? Are your cloudflare settings correct? How can I check my "server access logs"? Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted April 10, 2019 Share Posted April 10, 2019 well, nginx has a log you can check, as does your server. google around, there are plenty of tutorials. Link to comment Share on other sites More sharing options...
BAlGaInTl 279 Posted April 10, 2019 Share Posted April 10, 2019 Definitely need to check logs. How did you create the certificate file for Emby from the Cloudflare certificates and keys? Link to comment Share on other sites More sharing options...
germanicus 3 Posted April 10, 2019 Share Posted April 10, 2019 I vaguely remember having issues using cloudflare for DNS with my own SSL certificate. If I remember correctly cloudflare defaults to using it's shared SSL certificate which creates issues. I believe if you mess with the SSL settings for your domain on cloudflare, try switching to different modes, that might make the difference. Link to comment Share on other sites More sharing options...
BAlGaInTl 279 Posted April 10, 2019 Share Posted April 10, 2019 I vaguely remember having issues using cloudflare for DNS with my own SSL certificate. If I remember correctly cloudflare defaults to using it's shared SSL certificate which creates issues. I believe if you mess with the SSL settings for your domain on cloudflare, try switching to different modes, that might make the difference. If you use Cloudflare, there is no reason no to use their certs... they will generate a 15 year cert for you. Alot better than having to update every 90 days. Link to comment Share on other sites More sharing options...
Premby 0 Posted April 13, 2019 Author Share Posted April 13, 2019 Thank you for all your help, I removed nginx and it suddenly worked fine... 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