Dietpi + Emby. Updating Emby and enabling SSL

[Crake]

Thanks a lot Mate, done and working perfectly

[aldopi]

Hi,

I was looking for a way to access to my Emby server from outside using https.
I found this thread and this one viewtopic.php?f=11&t=7758&start=40.
I wanted first to find a way with HAproxy then I said to myself "why trying this way when there's possibly an other way with lighttpd ?".
Since I've installed nextcloud, I understood that it's using vhost for that.
In /etc/lighttpd/conf-available/ there's a file called: 10-proxy.conf

I've added those lines:

Code: Select all

$HTTP["url"] =~ "^/emby" {
    proxy.server = ( "" => ( ( "host" => "127.0.0.1", "port" => "8096" ) ) )
    proxy.header = ( "upgrade" => "enable" )
}

I can access to my Emby server now from https://mydomain.fr/emby.

I hope that this solution will help someone else.
I need to say I'm new in DietPi world, I have tiny knowledge in Linux.
So, it may not be the most secure way of doing, well, if someone has something to say to improve it, I will be ok!

[Joulinar]

that's pretty fine and much easier than HAproxy. Enabling the configuration is usually done by creating a sym link from conf-enabled to conf-available. However, moving 10-proxy.conf to conf-enabled is working same way.

[aldopi]

My bad I forgot to say that I did

Code: Select all

sudo ln -s ../conf-available/10-proxy.conf /etc/lighttpd/conf-enabled/

and restarted the lighttpd service.

[MichaIng]

Alternative: lighty-enable-mod proxy

[Joulinar]

personally I'm still more in favour of Nginx as revers proxy. On lighttpd I'm always struggling how to do it

[trigrhappy]

I don't disagree..... but it sure would be nice if emby automatically imported the necessary certificate format from letsencrypt, or letsencrypt exported the necessary format for emby. Either way would be convenient.

I blame emby for being difficult (since I expect better from paid software).

[Joulinar]

well from security point of view, creating a revers proxy might be better option anyway. This way you could reduce number of ports you would need to open towards internet

[trigrhappy]

I just wanted to say that I recently needed to rebuild my server, and I went with your method for encrypting.

It works beautifully. In fact, with your permission, I'd like to edit my original post with this as the primary method (with credit where it's due, of course)....since it is far simpler.

Hi,

I was looking for a way to access to my Emby server from outside using https.
I found this thread and this one viewtopic.php?f=11&t=7758&start=40.
I wanted first to find a way with HAproxy then I said to myself "why trying this way when there's possibly an other way with lighttpd ?".
Since I've installed nextcloud, I understood that it's using vhost for that.
In /etc/lighttpd/conf-available/ there's a file called: 10-proxy.conf

I've added those lines:

Code: Select all

$HTTP["url"] =~ "^/emby" {
    proxy.server = ( "" => ( ( "host" => "127.0.0.1", "port" => "8096" ) ) )
    proxy.header = ( "upgrade" => "enable" )
}

I can access to my Emby server now from https://mydomain.fr/emby.

I hope that this solution will help someone else.
I need to say I'm new in DietPi world, I have tiny knowledge in Linux.
So, it may not be the most secure way of doing, well, if someone has something to say to improve it, I will be ok!