Difficulty accessing server

[pir8radio 1292]

Why?

 

And would it make a difference given that I'm turning NGINX off when trying to access directly? You're saying to change the port in emby to match the NGINX port when turning NGINX off anyway, so I'm ending up in the same place.

 

Like luke said,  its kind of like having two people in one room (your PC) both of those peoples names are James (port), then you opening the door (firewall) to that room and saying "Hey James come here!"  How do you expect the correct James to come to you?     Same thing happens when you have two applications listening on the same port, you can't expect the correct one to respond. 

 

Thats why I was suggesting you put one James in a room at a time..     Have EITHER nginx OR emby listening on the 443 & 80.

Edited February 1, 2020 by pir8radio

[crusher11 851]

So what should I enter in the emby network settings then?

[pir8radio 1292]

like luke said, default emby settings..      You only want to change the "local" ports to 80 & 443 if you have shut down your nginx server..  so that emby now listens on these ports.  

 

So your normal config should be   Nginx listens on 80 & 443, nginx proxy_pass to 8096,  emby network set as shown below.    

Then if you want to troubles shoot bypassing nginx, you would shut down nginx, and change the emby Local ports to 80 & 443, restart emby.    that should allow you to connect directly to emby without changing your firewall or anything else.

then to put nginx back in the middle, you would set your emby Local ports back to what is shown below, restart emby, then start nginx again.

 

Edited February 1, 2020 by pir8radio

[crusher11 851]

My local ports aren't 80 and 443, my public ports are 80 and 443.

 

My current settings are as follows:

Local http port: 8096

Local https port: 8920

Public http port: 80

Public https port: 443

 

I think we're having a misunderstanding about whether we're referring to the private or public ports.

 

To get NGINX out of the way, do you mean I need to kill it and change my local http port to match the public one?

[pir8radio 1292]

My local ports aren't 80 and 443, my public ports are 80 and 443.

 

My current settings are as follows:

Local http port: 8096

Local https port: 8920

Public http port: 80

Public https port: 443

 

I think we're having a misunderstanding about whether we're referring to the private or public ports.

 

To get NGINX out of the way, do you mean I need to kill it and change my local http port to match the public one?

 

 

its not private or public...     Local port is the port emby is listening on weather you are accessing emby from in your network, or out over the web.    The public port settings are just used to tell some clients how to get to your server, emby is not actually listening on these ports or doing much with them..     So for example if you have  nginx-----emby      setup  nginx is listeining on 80 & 443   emby is listening on 8096 & 8920   emby doesnt know you have nginx, so its going to tell everyone (emby connect) some apps and clients etc,  "hi im emby you can get to me using port 8096 and 8920 using my internet ip"  but thats not true,  you have nginx on your internet ip, and he is listening on 80 & 443, so when an emby client tries to reach you its going to be trying <INTERNETIP>:8096   and it will get blocked..    A similiar situation would be your firewall/router..   maybe you open port 123 and direct that to 8096, again emby has no clue you did that, hence the addition of the "public port" settings..   Now emby will ignore its Local port numbers that he is actually listening on and say "hey you can connect to me on <INTERNETIP>:<whatever the public port is set to>!".    if that helps...   

Edited February 1, 2020 by pir8radio

[crusher11 851]

So are my settings okay? If I turn off NGINX do I just need to change the public http port to match the local http port?

[ebr 14913]

So are my settings okay? If I turn off NGINX do I just need to change the public http port to match the local http port?

 

Only if you port forwarded it that way (which is doubtful).

 

Even if you eliminate NGNIX, you must have port forwarding rules in your router pointing 443 (or whatever you use externally)->8029(or whatever Emby is listening on) and 8096->8096.

[crusher11 851]

443 is being forwarded to 443 in my router. That's the only port that's set up.

[ebr 14913]

443 is being forwarded to 443 in my router. That's the only port that's set up.

 

Then, if you eliminate NGNIX, you would need Emby listening on 443.

[crusher11 851]

Should I be forwarding an http port as well?

[crusher11 851]

Tried forwarding port 80 to port 80, still no dice. Tried forwarding it to 8096 instead, and I'm now able to access emby via IP:PORT.

 

So here's my setup at the moment:

Router is forwarding external port 443 to internal port 8920.

Router is forwarding external port 80 to internal port 8096.

Emby has local http port 8096 and local https port 8920.

Emby has public http port 80 and public https port 443.

 

My NGINX config listens on ports 80 and 443, but NGINX isn't running at the moment.

 

Where to from here, in order to get NGINX up and running again?

[pir8radio 1292]

Tried forwarding port 80 to port 80, still no dice. Tried forwarding it to 8096 instead, and I'm now able to access emby via IP:PORT.

 

So here's my setup at the moment:

Router is forwarding external port 443 to internal port 8920.

Router is forwarding external port 80 to internal port 8096.

Emby has local http port 8096 and local https port 8920.

Emby has public http port 80 and public https port 443.

 

My NGINX config listens on ports 80 and 443, but NGINX isn't running at the moment.

 

Where to from here, in order to get NGINX up and running again?

 

so now you have bypassed nginx...   test stuff make sure everything works...  if yes, then you can change your router to forward 443 to 443 and 80 to 80  restart nginx.   then test again.. if stuff is broken, is nginx.

[crusher11 851]

So when I want to start up NGINX, I just change the router settings and leave the emby settings alone?

[pir8radio 1292]

So when I want to start up NGINX, I just change the router settings and leave the emby settings alone?

 

correct....                

Without NGINX:       INTERNET 443-------->ROUTER 8920---------->EMBY LISTENING ON 8920
                                                                NGINX LISTENING ON 443


With NGINX ON:       INTERNET 443-------->ROUTER 443----\       EMBY LISTEINING ON 8920<---\
                                                         \----->NGINX LISTENING ON 443-----/

[crusher11 851]

Okay, so with NGINX disabled the Samsung TV is able to connect via IP:PORT successfully, but http://sub.domain.com fails, which rules out NGINX and SSL as potential issues.

 

EDIT: Apparently it was actually http//sub.domain.com that failed, and for obvious reasons. With the typo corrected, connection was successful. Further troubleshooting required then.

 

EDIT 2: https://sub.domain.com fails without NGINX running.

Edited February 5, 2020 by crusher11

[ebr 14913]

Okay, so with NGINX disabled the Samsung TV is able to connect via IP:PORT successfully, but http://sub.domain.com fails, which rules out NGINX and SSL as potential issues.

 

EDIT: Apparently it was actually http//sub.domain.com that failed, and for obvious reasons. With the typo corrected, connection was successful. Further troubleshooting required then.

 

Okay, so that proves that your original issue is with the configuration of NGINX, correct?

 

It sounded like you had it configured to listen on the same ports as Emby on the same machine and that definitely would have been a problem.  Is this what it all comes down to?

[crusher11 851]

No, because with NGINX off the Samsung TV still can't connect to my server when using HTTPS, as per my second edit.

[ebr 14913]

No, because with NGINX off the Samsung TV still can't connect to my server when using HTTPS, as per my second edit.

 

Did you configure everything that is required for Emby to be accessible via SSL without NGINX?

 

At this point, knowing that you had a port conflict, I would go back to NGINX, use Pir8radio's config and go from there.

[crusher11 851]

I don't know, does anything need to be changed? I was able to access the server on my web browser using HTTPS so I would imagine the settings were fine?

Edited February 5, 2020 by crusher11

[crusher11 851]

Further, this issue predates the update to Emby that broke my NGINX config, and has only ever affected this Samsung TV. Seems it's something to do with SSL, as that's all that was active when it occurred today.

[pir8radio 1292]

I still think its an ssl issue.  some of those apps are picky..      what do you see when you run your domain name through this site?  https://www.sslshopper.com/ssl-checker.html

 

does it look something like this:

 

[crusher11 851]

Different domain, IP, and serial number obviously but otherwise exactly identical.

[pir8radio 1292]

Different domain, IP, and serial number obviously but otherwise exactly identical.

 

interesting.....    oh and you are using cloudflare too right?  yea should work...    I think you even tried connecting to my server and that worked?   I dont recall.. my memory sucks.

[crusher11 851]

Haven't tried your server on the Samsung TV, no.

[crusher11 851]

Enabled NGINX and http access is still working. An attempted https connection to @@pir8radio's server failed.

 

So it's a CloudFlare SSL thing, surely?