Server inaccessible remotely via EmbyConnect

[asitz21 3]

Hey all, I used a Caddy guide and Caddy combined with a domain from noip to try to set up my Emby server through a reverse proxy. Everything seems to be working correctly when I go to my domain name remotely in a web browser or by manually entering my domain name and port in the apps, but for whatever reason, EmbyConnect is not saving the proper connection or is not connecting properly. Every time I try to log in with EmbyConnect, it says it can't connect.  Here's what Caddy shows me when it runs:

2024/09/02 21:55:55.834 INFO    using adjacent Caddyfile
2024/09/02 21:55:55.835 INFO    adapted config to JSON  {"adapter": "caddyfile"}
2024/09/02 21:55:55.835 WARN    Caddyfile input is not formatted; run 'caddy fmt --overwrite' to fix inconsistencies   {"adapter": "caddyfile", "file": "Caddyfile", "line": 2}
2024/09/02 21:55:55.842 INFO    admin   admin endpoint started  {"address": "localhost:2019", "enforce_origin": false, "origins": ["//localhost:2019", "//[::1]:2019", "//127.0.0.1:2019"]}
2024/09/02 21:55:55.842 INFO    tls.cache.maintenance   started background certificate maintenance      {"cache": "0xc000430e80"}
2024/09/02 21:55:55.842 INFO    http.auto_https server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {"server_name": "srv0", "https_port": 443}
2024/09/02 21:55:55.842 INFO    http.auto_https enabling automatic HTTP->HTTPS redirects        {"server_name": "srv0"}
2024/09/02 21:55:55.844 INFO    http.log        server running  {"name": "remaining_auto_https_redirects", "protocols": ["h1", "h2", "h3"]}
2024/09/02 21:55:55.844 INFO    http    enabling HTTP/3 listener        {"addr": ":443"}
2024/09/02 21:55:55.844 INFO    http.log        server running  {"name": "srv0", "protocols": ["h1", "h2", "h3"]}
2024/09/02 21:55:55.844 INFO    http    enabling automatic TLS certificate management   {"domains": ["my doman"]}
2024/09/02 21:55:55.845 INFO    autosaved config (load with --resume flag)      {"file": "C:\\Users\\Andy\\AppData\\Roaming\\Caddy\\autosave.json"}
2024/09/02 21:55:55.845 INFO    serving initial configuration
2024/09/02 21:55:55.848 INFO    tls     storage cleaning happened too recently; skipping for now        {"storage": "FileStorage:C:\\Users\\Andy\\AppData\\Roaming\\Caddy", "instance": "f9be30e8-14fd-4b07-9fdd-7dd8f1b965ad", "try_again": "2024/09/03 21:55:55.848", "try_again_in": 86400}
2024/09/02 21:55:55.848 INFO    tls     finished cleaning storage units

 

I'm pretty sure I set port forwarding up correctly, but I have a question about that as well. When I go to forward ports 80 and 443, do I forward the external ports 80 & 443 to internal ports 80 & 443, or do I forward them to the internal Emby local ports 8096 and 8290?

If anyone has any ideas as to why I can connect to the server in a web browser using the domain name and why I can connect to it using manual entry in the Emby apps, but not with Emby Connect, I would be greatly appreciative of any assistance you might be able to offer. I'm kind of a newbie when it comes to some of this stuff, so if you need more information from me that I didn't think to provide in order to accurately assess or help me troubleshoot my issue, please let me know! Thanks!

[seanbuff 994]

14 minutes ago, asitz21 said:

When I go to forward ports 80 and 443, do I forward the external ports 80 & 443 to internal ports 80 & 443, or do I forward them to the internal Emby local ports 8096 and 8290?

You forward external ports to the internal ports that Caddy would be listening on, which by default would be 80 and 443 so I'd say you have done that bit correctly.

 

15 minutes ago, asitz21 said:

f anyone has any ideas as to why I can connect to the server in a web browser using the domain name and why I can connect to it using manual entry in the Emby apps, but not with Emby Connect

What do you have on your 'Network' tab in Emby, ideally it should look something like this if using a reverse proxy:

[asitz21 3]

13 minutes ago, seanbuff said:

You forward external ports to the internal ports that Caddy would be listening on, which by default would be 80 and 443 so I'd say you have done that bit correctly.

 

What do you have on your 'Network' tab in Emby, ideally it should look something like this if using a reverse proxy:

Hi, thank you for your prompt reply! Here's what my Network settings look like from the same view as your screenshot:

Edited September 2 by asitz21

[seanbuff 994]

and on the Dashboard, does it show your public "Remote" address with port 443?

[asitz21 3]

26 minutes ago, seanbuff said:

and on the Dashboard, does it show your public "Remote" address with port 443?

Hmm, no. It just shows the domain name without the port under Remote access:

 

No colon after the domain name to indicate a port either, it just ends with the domain suffix.

Edited September 2 by asitz21

[Lessaj 197]

Since your port is 443 it will display like that, mine does not show the 443 either.

Does canyouseeme show that 443 is open?

[asitz21 3]

6 minutes ago, Lessaj said:

Since your port is 443 it will display like that, mine does not show the 443 either.

Does canyouseeme show that 443 is open?

Thanks for the clarification!

It's open according to canyouseeme

 

Edited September 2 by asitz21

[asitz21 3]

Oh silly silly me...  I was browsing other topics on here and found another user who was having Connect issues and it was suggested for them to unlink and relink their Connect email. I hadn't thought to try it because I had just recently configured the reverse proxy and that's when I started having difficulties. Anyway, I unlinked and relinked my connect email and it's working now. To the both of you who offered your help in troubleshooting, thank you and I am most sorry for wasting your time.

Edited September 3 by asitz21