Manual Connect Issues

[wolf39us 1]

Hello All!

I'm a new Emby user.  I did try seeing if I can find someone with a similar issue but was unable to find one.  Here is my issue.

• I have Emby setup running as a server on Ubuntu 22.04.  (Docker)
• I am using a reverse proxy via swag using the default configuration

Using Emby Connect, my server is connectable and everything is just fine using the domain and subpath `/emby` -- However, when I use the same address via manual connect option, I always get server unreachable.  

I've repeated this at several locations with more than one account.  A manual connect always fails, but Emby connect always works.

I confirmed I have my secure connection set to "let reverse proxy determine" and I have my public port set to 443 for https.

Not sure what I'm missing here because the domain and subpath 100% work.

Edited September 12, 2024 by wolf39us

[Lessaj 467]

What address do you see after logging in to emby connect that works and what address are you trying manually?

[wolf39us 1]

In both cases, it is the same address.  

https://mydomain.com/emby -- which is what confuses me because it really should just work.  In Emby connect, it shows the exact same address and it works.  Do it manually though, and you'll end up with an error connecting.

[Lessaj 467]

You don't even need to go to /emby it will just 302 redirect you from / anyway.

If you try to telnet to that address on 443, does that connect or time out?

[wolf39us 1]

Thanks.  While I'm confused why it is set up this way, your response sort of hinted me in the right direction.

I'm surprised the app already specifies `/emby` in the target.  So I took away the subpath and then cleared out the port 443.  It worked and asked me to specify a user and password.

So I wrote https://mydomain.com and no port.

Edit:  Just confirmed that you can either use no port or you can use 443.  It works both ways.  But you MUST specify the protocol (in my case https)

Edited September 12, 2024 by wolf39us

[Neminem 1518]

Tbh Https means port 443 unless specified other wise.

[Neminem 1518]

If you had used emby standard port 8920 for https.

Then you would have needed to specify port 8920.

[wolf39us 1]

Yes, I'm fully aware of that.  

But you never know with some programs.  Like I didn't know my reverse proxy subpath would have an issue connecting.  Generally, applications don't build in the subpath in the request.  I suppose I could have corrected this by utilizing a subdomain instead... but well.  It works either way!

[wolf39us 1]

1 minute ago, JayceDK said:

If you had used emby standard port 8920 for https.

Then you would have needed to specify port 8920.

In a reverse proxy situation, you don't normally use the programs ports.  You almost exclusively use 80/443 and let the server redirect you from there.  I use reverse proxy because it keeps the native applications ports from being exposed to the internet.

[Lessaj 467]

I think you could get /emby to work if you also proxy it to the same path but there's really no reason to do that and I don't recommend it. Something like:

Quote

ProxyPass "/emby" "https://my.emby.server:8920/emby"

ProxyPassReverse "/emby" "https://my.emby.server:8920/emby"

 

Edited September 12, 2024 by Lessaj