Jump to content

Emby + Domain Name?


David Martin

Recommended Posts

David Martin

Hi, I've been using Emby for a while now and i really like it, So much so I want to get a domain name for it so instead of having a DDNS address point users to my servers IP address and port I just want to have a URL instead or my IP address and port.

For example.
Current - http://dukservers.ddns.net goes to http://86.16.144.46:8096/web/index.html

Wanting - www.exampledomain.co.uk

 

How would i go about doing this?

Many thanks David

Link to comment
Share on other sites

pir8radio

If you have a static internet IP from your internet provider you can go to any register.com type site, buy your domain name and set it up to point to your internet connection/server..    If your internet ip changes (randomly picked from a pool every time you restart your net connection) you need to purchase a DYNDNS.org "vip" account or a free DYNU.com account, set it up, and they will give you a list of DNS servers to change on your domain name admin panel.. Your current no-ip.com place might offer this service too. That way XXXXX.co.uk will always follow your changing IP..   This is what I do.   Works well.

 

This is all assuming your ISP is not blocking port 80...   If they are, you can still buy a domain name but it will redirect to your existing ip:port, it will hide it from the users so they wont know... So i guess this could be a second option for you..   DYNDNS also offers this, called "webhop redirection".

 

We can help you further after you get your domain name purchased, if needed..

Edited by pir8radio
  • Like 1
Link to comment
Share on other sites

jpaytoncfd

Purchase your domain from anyone that provides DNS service. Add a cname record to your DDNS service address with a wild card so all subdomains link to the ddns address. Use a free DDNS service like duckdns.org. 

 

You can take it a step further and use my Easy Home URL's guide. Skip to the server section and add emby.YOURURL.COM to the server_name line. If you have questions feel free to comment. I am happy to help. My guide is on my blog here: http://knightcinema.com/2015/09/05/super-easy-to-remember-home-urls/

  • Like 2
Link to comment
Share on other sites

David Martin

I dont think my IP is static but it has not changed in about two years now.
Should I just buy a domain name and point it to my IP address see if it works as there are some pretty cheap ones?

 

What ports do I need to forward for it to work? I've already got the ports forwarded for Emby 8096 + 8920.

Link to comment
Share on other sites

David Martin

I should have mentioned my current server is on windows 7.

Internet connection Virgin Media 200mb/s fiber (Superhub 2 Router)

Link to comment
Share on other sites

pir8radio

I dont think my IP is static but it has not changed in about two years now.

Should I just buy a domain name and point it to my IP address see if it works as there are some pretty cheap ones?

 

What ports do I need to forward for it to work? I've already got the ports forwarded for Emby 8096 + 8920.

If you are fiber its probably static..   You can buy a domain name and put your ip in there...  if it just stops working one day you can always update the IP (A Record).  You will need to change your emby port to 80 and 443 (secure) as well as open those holes in your NAT

  • Like 1
Link to comment
Share on other sites

pir8radio

yes, then your new shiny domain name will go in the external wan address field!

  • Like 1
Link to comment
Share on other sites

pir8radio

You want to click "MANAGE DNS" and add or edit the "A" record. your ip address will go here.

 

There are a few other settings you will have to edit, but lets get you pointed at your server first.

For example you will want to create a CNAME that is WWW.yourdomainname.com and point it to yourdomainname.com     that way   http://yourdomainname.com and http://www.yourdomainname.comwill both point to your A record (ip address).

 

Don't be discouraged if you put your ip in the A record and your name doesn't bring up emby.. it sometimes takes up to 2 hours for that info to propagate DNS servers.

 

as a test you can always try to ping your domain name and see if it comes back with your ip address.

Edited by pir8radio
  • Like 1
Link to comment
Share on other sites

pir8radio

@ i see you figured out the A name..   now it looks like you just need to change your emby port to 80 instead of 8096, and open 80 in your firewall.

Edited by pir8radio
  • Like 1
Link to comment
Share on other sites

David Martin

How do i open the port in my firewall?
I've forwarded the ports as shown in the screenshot below.

568d85829dcc2_SuperHubGUI.png568d858aaa441_Advanced.png

I really appreciate all the help by the way.

Link to comment
Share on other sites

  • 4 months later...
dimmiemedia

Hi there. Nice manual!

 

I'm running a xampp webserver on port 80 is it possible to bind something in vhost?

Link to comment
Share on other sites

  • 8 months later...

This seems like a great workflow. But, I'm having some issues with my domain.

 

@@pir8radio would you have a moment to help me out?

 

I have ported my public ports to 443, and my local ports to 80

 

I then added my domain name to the External Domain in emby.

 

On my DNS setup page I have created an "A" type record with a value point to my external IP.

 

Yet my domain name doesn't connect with my computer.

  • Like 1
Link to comment
Share on other sites

pir8radio

@@chef Your ported public port shouldn't go from SSL 443 to standard HTTP 80, if i am reading that correctly..    You should have 443 and 80 ported to your emby ip with the same port numbers..    

Depending on your router you should see something like this: (replace IP with your emby LAN address)

589be7b30d56d_Screenshotfrom201702082152

 

And Emby/Advanced settings should look like what is in POST #7 above.

An alternative setup, should you want to keep the default emby ports 8096 & 8920 for your in home clients, would be to change the "Port to" ports on your router to 8096 for HTTP and 8920 for HTTPS and then set emby/Advanced settings like the picture in POST #14 above.

 

 

If your setup looks like this you may have to give some more info, like internet provider, device ahead of your router if any. 

Edited by pir8radio
  • Like 2
Link to comment
Share on other sites

Thank you muchly @ pri8radio it's working!

 

I just have to figure out why my https connection is timing out.

 

I must have ports all messed up. but the http connection is working nicely.

Edited by chef
  • Like 2
Link to comment
Share on other sites

pir8radio

it should let you put an A name in https://www.godaddy.com/help/change-an-a-record-19239

 

However forwarding should still function for the web gui and it is not.  You still dont have the correct ports open on your firewall.    80 and 443 are not working.  @@chef Take your above photos down and PM me if you have any other info.. Your server is kind of open lol     

 

What will work for testing is changing that forwarding IP to http from https and adding :8920 to the end.. That will work with your current port that is open.  We will need to look at your router/firewall settings. 

Link to comment
Share on other sites

Swynol

@@pir8radio

 

i could do with some advice. I currently have a domain name and a DDNS from Namecheap. I have it setup:-

 

My DDNS service is update.mydomain.net which when my IP changes it updates it to namecheap.

 

I then have subdomains pointing to different services i run. so for emby its https://emby.mydomain.net which has a URL redirect on it to https://update.mydomain.net:8920 this works fine however i would prefer to see https://emby.mydomain.net in the address bar rather than the update.my.... So i added a CNAME which points emby to my DDNS https://update.mydomain.net and then forwarded the external ports 443 to internal port 8920. works fine. 

 

However i have other services running so if i changed them to the external port of 443 how would they know where to go. so for example. i have https://sonarr.mydomain.net which has a URL redirect to https://update.mydomain.net:PORT if i created a CNAME for sonarr to point to https://update.mydomain.net it will use the same external port as emby. it wont let my specify a port in a cname record. 

 

any better way to set this up?

Link to comment
Share on other sites

pir8radio

@@pir8radio

 

i could do with some advice. I currently have a domain name and a DDNS from Namecheap. I have it setup:-

 

My DDNS service is update.mydomain.net which when my IP changes it updates it to namecheap.

 

I then have subdomains pointing to different services i run. so for emby its https://emby.mydomain.net which has a URL redirect on it to https://update.mydomain.net:8920 this works fine however i would prefer to see https://emby.mydomain.net in the address bar rather than the update.my.... So i added a CNAME which points emby to my DDNS https://update.mydomain.net and then forwarded the external ports 443 to internal port 8920. works fine. 

 

However i have other services running so if i changed them to the external port of 443 how would they know where to go. so for example. i have https://sonarr.mydomain.net which has a URL redirect to https://update.mydomain.net:PORT if i created a CNAME for sonarr to point to https://update.mydomain.net it will use the same external port as emby. it wont let my specify a port in a cname record. 

 

any better way to set this up?

 

So wait... you have one of those weird  myname.dyndns.org domain names that you do not own..  Then you own mydomain.com   You have your mydomain.com pointing to myname.dyndns.org?  so when i go to mydomain.com my browser will show myname.dyndns.org:PORT/blah/blah.      You can't really loose the redirects unless you install ngnix as a reverse proxy...   Its not hard we can work through it if you like..  That will allow you to run all of these goofy servers with different ports all on port 80 and/or 443 so your https://sonarr.mydomain.com will come into nginx on regular ssl port 443 and nginx will direct it to your internal IP:PORT same for all of the other things you are running...    

 

Then the next step would be to get rid of the myname.dyndns.org address by using something like the free http://DYNU.com to dynamically update your mydomain.com directly.  It works just like your dynamic ip service but updates the A records on your owned domain name.  If that all makes sense.  

Edited by pir8radio
Link to comment
Share on other sites

Swynol

ye i have been looking at nginx. getting a bit lost with the config.

 

ye i have a dynamic dns i use namecheap which also has all my dns features. so my router has an option to update my IP using a A+ dns record. so my record is update.mydomain.net. then i have url redirects so i use sonarr.mydomain.net which forwards to update.mydomain.net:port. it works, and works with my SSL cert.

 

want i would like is having it say sonarr.mydomain.net in the address bar rather than update.mydomain.net:port and i would like to do as you say, only have the one port open to the internet rather than all the ones i currently have.

 

so i have installed ngnix for windows. so now i create a CNAME for emby to point to update.mydomain.net (my dynamic dns). then setup the nginx config to point emby.mydomin.net to my internal server ip and internal port number.

Link to comment
Share on other sites

pir8radio

http://nginx-win.ecsds.eu/ is the good version..  free.. 

 

Yes, what you said above is correct..   There are all kinds of ways to setup a reverse proxy..   But lets start here so you can get one of your servers running through nginx and play around with it.

the below config is a starter config for emby/nginx you can remove a some stuff for a basic backend server, like a reporting server or something.

Here is most of my config https://emby.media/community/index.php?/topic/42317-reverse-proxy-vs-hostname-forwarding/?p=413614 if you want to reference some of the Pre-Server settings.

server {
    listen [::]:80;
    listen 80;
    listen [::]:443 ssl;
    listen 443 ssl;
    server_name emby.domain.net; # Base domain name the client entered emby.yourdomain.com

        #path to your SSL files, nginx must now handle all of the SSL, not each individual server
        #to your backend is regular HTTP its assumed safe, its on your local network or the same PC as nginx
        ssl_session_timeout 30m;
        ssl_protocols TLSv1.2 TLSv1.1 TLSv1;
	ssl_certificate      ssl/_pub.pem;
	ssl_certificate_key  ssl/_pvt.pem;
        ssl_session_cache shared:SSL:10m;

     location / {
        proxy_pass http://127.0.0.1:8080;  # Local emby ip and non SSL port

	proxy_hide_header X-Powered-By;
	proxy_set_header Range $http_range;
	proxy_set_header If-Range $http_if_range;
	proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        #Next three lines allow websockets
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}
Edited by pir8radio
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...