OT: Embys Apache Server sharing port 80

[chef 3810]

Not sure if this is possible.

 

I have one SSL which is made for my domain.

 

Currently, that domain is pointed at my emby server.

 

It is important that emby is covered by my SSL and domain for development purposes (I have quite a number of projects on the go which involves my emby endpoints to be secure).

 

I have created a sweet website which I wanted to host from something like Wamp, but emby is working on port 80/443, which means pointing my domain to my ip will resolve at emby.

 

has anyone ever wrapped emby inside a website? <--Does that make sense??

 

The website I have created is a pretty neat, It showcases my DIY Arduino IoT/Smart Home builds, as well as a cool blog for all things Emby!

 

Plugins I have created, code tips and tricks, and tying all my Arduino projects, Emby Projects, Z-Wave Projects together into one giant, intertwined Smart Home.

 

But, the problem still remains that even if I host a separate Apache Server I can't redirect traffic from my domain to my IP because that spot is taken by Emby.

 

I would like to have the best of both worlds: Emby hosted for my development apps, but initially my website is what is foremost when visiting the domain.

 

I looked into Wildcard SSLs to host subdomains but it was too expensive, I also looked into Hosting options with my domain supplier, but it also is too expensive... Mostly because Apache will allow me to host everything myself.

 

I thought about perhaps creating a Channel in Emby, as a plugin, which is my website, but then people would have to login into my server to see it, and I think that the site has some really useful, and cool tips and tricks for more than my core users.

 

Anyone have any thoughts?

Edited March 16, 2017 by chef

[PrincessClevage 175]

This can be done with a Netscaler or F5 but this may be cost prohibitive.

Cheaper option might be Software VPN to the Web Host server

 

P.s I'm looking forward to dig through your recipes

Edited March 16, 2017 by PrincessClevage

[Doonga 17]

So... If I'm understanding you correctly, you have a single IP address and you want to host multiple sites on it? So for example: https://emby.yourdomain.com, https://www.yourdomain.com, https://whateverelse.yourdomain.com?

 

If that's the case, get Letsencrypt working for your certificates. They're free so that solves your certificate issue. What you're actually doing here is setting up a reverse proxy for Emby, then hosting your site on the same Apache instance. Next you set up each vhost in Apache such as below:

NameVirtualHost *:443

<VirtualHost *:443>
 ServerName emby.yourdomain.com
 DocumentRoot /var/www/site
 SSLEngine on
 SSLCertificateFile /path/to/emby_yourdomain_com.crt
 SSLCertificateKeyFile /path/to/emby_yourdomain_com.key
 SSLCertificateChainFile /path/to/CACertChain.crt
 ProxyPass "/"  "http://<Your Emby Server hostname or IP:8096>/"
 ProxyPassReverse "/"  "http://<Your Emby Server hostname or IP:8096>/"
</VirtualHost>

<VirtualHost *:443>
 ServerName www.yourdomain.com
 DocumentRoot /var/www/site2
 SSLEngine on
 SSLCertificateFile /path/to/www_yourdomain_com.crt
 SSLCertificateKeyFile /path/to/www_yourdomain_com.key
 SSLCertificateChainFile /path/to/CACertChain.crt
</VirtualHost>

The ServerName directive is the key in each block, Apache uses SNI to determine which block to direct the traffic through.

 

You'll also need to configure your DNS to send traffic to the various hostnames (emby, www, whateverelse.yourdomain.com) to your IP.

 

These are very generic so please don't expect to copy/paste and have it just work. The intent is to give you an idea of how it could work then you'll be able to design a solution that works for you.

Edited March 16, 2017 by Doonga

[chef 3810]

So... If I'm understanding you correctly, you have a single IP address and you want to host multiple sites on it? So for example: https://emby.yourdomain.com, https://www.yourdomain.com, https://whateverelse.yourdomain.com?

 

If that's the case, get Letsencrypt working for your certificates. They're free so that solves your certificate issue. What you're actually doing here is setting up a reverse proxy for Emby, then hosting your site on the same Apache instance. Next you set up each vhost in Apache such as below:

 

NameVirtualHost *:443

<VirtualHost *:443>
 ServerName emby.yourdomain.com
 DocumentRoot /var/www/site
 SSLEngine on
 SSLCertificateFile /path/to/emby_yourdomain_com.crt
 SSLCertificateKeyFile /path/to/emby_yourdomain_com.key
 SSLCertificateChainFile /path/to/CACertChain.crt
 ProxyPass "/"  "http://<Your Emby Server hostname or IP:8096>/"
 ProxyPassReverse "/"  "http://<Your Emby Server hostname or IP:8096>/"
</VirtualHost>

<VirtualHost *:443>
 ServerName www.yourdomain.com
 DocumentRoot /var/www/site2
 SSLEngine on
 SSLCertificateFile /path/to/www_yourdomain_com.crt
 SSLCertificateKeyFile /path/to/www_yourdomain_com.key
 SSLCertificateChainFile /path/to/CACertChain.crt
</VirtualHost>

The ServerName directive is the key in each block, Apache uses SNI to determine which block to direct the traffic through.

 

You'll also need to configure your DNS to send traffic to the various hostnames (emby, www, whateverelse.yourdomain.com) to your IP.

 

These are very generic so please don't expect to copy/paste and have it just work. The intent is to give you an idea of how it could work then you'll be able to design a solution that works for you.

Okay! I'll give this a go and see if I can get it working.

 

I'll try letsencrypt again and see if I can get things moving.

 

Thank you for the advice.

[Swynol 375]

i use NGINX reverse proxy for this. I have all my services behind port 443, emby,plex, sonarr, nzb, unifi, prtg.... from my router i point 443 to my NGINX server which then does the rest.

[chef 3810]

It got it working! This is awesome! There Are some emby apps I have written for my connected home which has no place here on emby, but now my blog site will explain it all. sweet!