Best option for remote access

[Lazarus_Long 80]

Hey everyone,

I'm running Emby inside Docker on Ubuntu and looking to setup fairly secure remote access.  I'm not afraid of getting too technical and already have my own domain name.  Just wondering what the best option would be for me?  Would prefer to not use either Emby Connect or Cloudflare.  Have read some posts about Caddy but I believe that's more geared towards a Windows environment?

Thanks in advance.

[pwhodges 2012]

Caddy is fully cross-platform - indeed I think there are some (minor) facilities not fully implemented on Windows for the usual technical reasons.  But on any platform, Caddy by default does all you need for https connections, other than getting you a domain name!

Paul

[Lazarus_Long 80]

5 minutes ago, pwhodges said:

Caddy is fully cross-platform - indeed I think there are some (minor) facilities not fully implemented on Windows for the usual technical reasons.  But on any platform, Caddy by default does all you need for https connections, other than getting you a domain name!

Paul

Thanks Paul!  Can you point me to your current write-up on how to set it up?  I couldn't figure out the latest version lol.

[Lazarus_Long 80]

I found some more info and have a lot of it setup, but can't seem to connect.

I have confirmed that I can ping my domain and it resolves to my public IP.

I have Caddyfile setup as the following:

emby.xxxx.com {
    reverse_proxy / 10.0.0.187:8096
}

And looking at the docker logs for the container, I can see that it appears to have downloaded a certificate...

{"level":"info","ts":1758319306.5644734,"msg":"successfully downloaded available certificate chains","count":2,"first_url":"https://acme-v02.api.letsencrypt.org

I don't have any port forwarding setup on the router and changed my Emby network settings as shown below.

However, when trying to connect to it via an app (off network), or just the website within my network, it won't connect properly.

[pwhodges 2012]

1 minute ago, swallman said:

I have confirmed that I can ping my domain and it resolves to my public IP.

I don't have any port forwarding setup on the router

 

You need to have port 443 forwarded to 443 in Caddy - I also have 80 forwarded to 80, but I think that's no longer required (it used to be necessary for getting the certificate), though it's good, as it enables Caddy to tell the client to switch to https from http.  Ping doesn't tell you about ports (though it's a good start) - you need to run a website such as canyouseeme.org (or any of a multitude of similar sites) which will test if the ports are open.

Paul

[Lazarus_Long 80]

Yeah I have that setup in my Docker compose for Caddy, but wondering if I also need to port forward on the router?

Trying with DNSChecker.org and it can't connect on 443 or 80

[Lazarus_Long 80]

OK, making further progress...I opened port 443 on my router and now I can confirm I can hit it outside my network.

Still having issues getting Emby to connect up though.

[Lazarus_Long 80]

So I got it to work by temporarily running Caddy on my Windows server and pointing to the Ubuntu server.  Must be something wrong with my config in Docker compose so will need to dig into that a bit more.

[Luke 42077]

3 hours ago, swallman said:

So I got it to work by temporarily running Caddy on my Windows server and pointing to the Ubuntu server.  Must be something wrong with my config in Docker compose so will need to dig into that a bit more.

That's interesting. Please keep us posted. Thanks for following up.