Jump to content

emby not listeing on port 8920


Marco3G
Go to solution Solved by Lessaj,

Recommended Posts

Marco3G

Hi everyone

I'm trying to make my emby reachable from the web. I get error 502 Bad Gateway currently, which is no wonder:

 

Quote

user@emby:~$ sudo ss -tulpn | grep LISTEN
tcp   LISTEN 0      4096         0.0.0.0:35939      0.0.0.0:*    users:(("rpc.statd",pid=946,fd=9))
tcp   LISTEN 0      64           0.0.0.0:41897      0.0.0.0:*
tcp   LISTEN 0      4096         0.0.0.0:111        0.0.0.0:*    users:(("rpcbind",pid=754,fd=4),("systemd",pid=1,fd=47))
tcp   LISTEN 0      4096   127.0.0.53%lo:53         0.0.0.0:*    users:(("systemd-resolve",pid=809,fd=14))
tcp   LISTEN 0      128          0.0.0.0:22         0.0.0.0:*    users:(("sshd",pid=888,fd=3))
tcp   LISTEN 0      512                *:8096             *:*    users:(("EmbyServer",pid=161350,fd=208))
tcp   LISTEN 0      4096            [::]:58881         [::]:*    users:(("rpc.statd",pid=946,fd=11))
tcp   LISTEN 0      4096            [::]:111           [::]:*    users:(("rpcbind",pid=754,fd=6),("systemd",pid=1,fd=49))
tcp   LISTEN 0      128             [::]:22            [::]:*    users:(("sshd",pid=888,fd=4))
tcp   LISTEN 0      64              [::]:39709         [::]:*

It does not listen on 8920.

Under network settings, I have set the domain name, allow remote conenctions and I've tried both Requires for all remote connections and Handled by reverse proxy for Secure connection mode

 

There is just no listener on 8920. Do I need to give emby a self signed certificate? NGINX already has a LetsEncrypt cert for the subdomain I want to use.

embyserver(5).txt

Edited by Marco3G
Link to comment
Share on other sites

Marco3G

I just found another thread where Luke says the reverse proxy should forward to the http port. That works. So never mind :D

Link to comment
Share on other sites

1 hour ago, Marco3G said:

I just found another thread where Luke says the reverse proxy should forward to the http port. That works. So never mind :D

HI, a reverse proxy is not required but it can help. 

Are you all set now?

Quote

There is just no listener on 8920. Do I need to give emby a self signed certificate? NGINX already has a LetsEncrypt cert for the subdomain I want to use.

Yes you need to setup https before you can use it.

Link to comment
Share on other sites

Marco3G

How is a reverse proxy not required? I mean sure, I could forward the ports and manually create a LetsEncrypt certificate to feed Emby but then I'd either have to enter the port  every single time and keep it in mind or forward 443 and then I couldn't use any other service on 443.

I've been looking around but so far I haven't found a proper guide on how to do that. I'm assuming I could use a sef-signed certificate for Emby on my internal network and use https like that. Would I have to manually generate that with openssl?

Link to comment
Share on other sites

Exactly, you just have to port forward.

Link to comment
Share on other sites

Quote

I've been looking around but so far I haven't found a proper guide on how to do that. I'm assuming I could use a sef-signed certificate for Emby on my internal network and use https like that. Would I have to manually generate that with openssl?

Just keep in mind that not all devices accept self-signed certs, so you may get connection errors. But try it and see how it goes for you.

Link to comment
Share on other sites

Marco3G

It would only be when connecting to the internal dmz domain name instead of going through the internet. I can live with that. However what I cannot live with is PKCS#12. I have no idea how that works and every guide so far fell flat on my system.

Link to comment
Share on other sites

  • Solution
Lessaj

You should be able to create a PKCS#12 (or pfx) as long as you have the key and certificate. I should probably refresh my self signed certificate because I did this 6 years ago but something like this should work.

openssl pkcs12 -export -out domain.name.pfx -inkey domain.name.key -in domain.name.crt

 

  • Thanks 1
Link to comment
Share on other sites

Marco3G

I had to try three times and it finally worked. Couldn't tell you what I did wrong the first two times.

 

I can connect to https internally and I just changed the setup for the reverse proxy. It works now. Thanks everyone.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Marco3G

Well, now I'm off to throw the VM away again and reinstall. I tried to activate hardware transcoding and now it's an NVIDIA trash heap and I forgot to take a snapshot.

 

*sigh*

I HATE, absolutely hate OSS, especially when you need proprietary drivers. I'm so tired.

Link to comment
Share on other sites

Lessaj

What are you stuck on? Trying to install the nvidia driver? I've done this in my VM, I pass through the GPU to it.

EDIT: Just saw your other topic, don't reply here!

Edited by Lessaj
Link to comment
Share on other sites

Marco3G

Well, from what I can tell, the driver is installed. nvidia-smi shows the GPU, EMBY shows me transcoding options under advanced... it just won't touch the GPU with a ten foot pole and one CPU core smacks to 100% and stays there in htop.

 

I have no idea whether it's installed correctly. How to check that is documented nowhere.

Link to comment
Share on other sites

Hi, what makes you think it won't touch the gpu? Can we please look at an example? Thanks.

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...