remote port with NPM and domain name

[ITGuy1024 18]

I have my domain name mapped to my ip address and NPM handling all secure connections for emby, nextcloud and a web server. It's worked perfect for years.

If I go to emby.mydomain.com it creates the secure connection and all that stuff as expected.
Emby shows this for the remote wan address which obviously doesn't work.

My one user is having issues with their roku HD and google tv boxes getting timeout errors connecting to the remote emby server. From their PC it works fine (chrome and windows app).
On the streaming boxes adding the server manually as https://emby.mydomain.net -I've tried with no port, 443 and 8920. 
I'm wondering if this remote address with trailing port is the issue for them. The PC browser is smart enough to route correctly and the streaming boxes aren't?
I have secure connection mode set to be handled by the reverse proxy.

Edited December 17, 2024 by ITGuy1024

[Luke 42078]

Quote

The PC browser is smart enough to route correctly and the streaming boxes aren't

Hi, most of our apps should be smart enough, although I'm not sure about Roku.

I would try walking him through step by step and see if you're able to connect, and then get back to us with the results of that. Thanks.

[Happy2Play 9780]

4 minutes ago, ITGuy1024 said:

I have my domain name mapped to my ip address and NPM handling all secure connections for emby, nextcloud and a web server. It's worked perfect for years.

If I go to emby.mydomain.com it creates the secure connection and all that stuff as expected.
Emby shows this for the remote wan address which obviously doesn't work.

My one user is having issues with their roku HD and google tv boxes getting timeout errors connecting to the remote emby server. From their PC it works fine (chrome and windows app).
On the streaming boxes adding the server manually as https://emby.mydomain.net -I've tried with no port, 443 and 8920. 
I'm wondering if this remote address with trailing port is the issue for them. The PC browser is smart enough to route correctly and the streaming boxes aren't?
I have secure connection mode set to be handled by the reverse proxy.

Since you mentioned Roku I believe you have to enter 0 or multiple zeros for port as it really is a defect of the client.

 

 

[ITGuy1024 18]

3 minutes ago, Luke said:

Hi, most of our apps should be smart enough, although I'm not sure about Roku.

I would try walking him through step by step and see if you're able to connect, and then get back to us with the results of that. Thanks.

I was there and tried it myself with no success.

[ITGuy1024 18]

3 minutes ago, Happy2Play said:

Since you mentioned Roku I believe you have to enter 0 or multiple zeros for port as it really is a defect of the client.

 

 

Ah that's interesting... We'll try that and report back.

[Lessaj 467]

So your remote access is actually on 443 and not 8920? Make sure to fill that in in the Network tab.

[ITGuy1024 18]

5 minutes ago, Lessaj said:

So your remote access is actually on 443 and not 8920? Make sure to fill that in in the Network tab.

The proxy takes the 443 https connection and forwards it internally to the correct ports on the server being requested.

Edited December 17, 2024 by ITGuy1024

[ITGuy1024 18]

43 minutes ago, Happy2Play said:

Since you mentioned Roku I believe you have to enter 0 or multiple zeros for port as it really is a defect of the client.

 

 

No timeout error with 0's but getting a quictls error.

[Lessaj 467]

2 minutes ago, ITGuy1024 said:

The proxy takes the https connection and forwards it internally.

Yes I understand that, but if you're not using 8920 externally then it shouldn't advertise it as such. This URL will be used by the apps.

[Happy2Play 9780]

5 minutes ago, ITGuy1024 said:

No timeout error with 0's but getting a quictls error.

So does this circle back to your previous topic?

 

[ITGuy1024 18]

5 minutes ago, Happy2Play said:

So does this circle back to your previous topic?

 

Yerp. Unfortunately back to that now it seems.

[ITGuy1024 18]

Changing embys external port in the proxy to 39000 fixed both issues. For now.
I have two subdomains - emby.mydomain and cloud.mydomain (nextcloud). I think they were both fighting for port 443 going into NPM.
No clue why it works fine for others and not them unless it's something to do with their Comcast connection. Or NPM is having issues routing the incoming 443 port.

[Carlo 4561]

What is NPM? I just keep thinking Node Package Manager for JavaScript.

Thannks

[ITGuy1024 18]

Nginx Proxy Manager
https://github.com/NginxProxyManager/nginx-proxy-manager?utm_source=nginx-proxy-manager
 

[Carlo 4561]

Dah,

Had a metal block as I kept think Javascript but knew it was a proxy from the context.
Thanks