pwhodges 1717 Posted August 9 Posted August 9 Well done. Just check how long the certificate lasts and make a diary entry to renew it when required. Paul 1
HairyBizRat 11 Posted August 9 Posted August 9 1 hour ago, pwhodges said: Well done. Just check how long the certificate lasts and make a diary entry to renew it when required. Paul Side question - any idea how to change this stupid user name i have? When I click on my profile on the top right there is no option to change it
guunter 36 Posted August 9 Posted August 9 30 minutes ago, mjroberts said: Side question - any idea how to change this stupid user name i have? When I click on my profile on the top right there is no option to change it In the dashboard click the 3 dots next to your server name to change it.
HairyBizRat 11 Posted August 9 Posted August 9 7 minutes ago, guunter said: In the dashboard click the 3 dots next to your server name to change it. Sorry, I meant my username in these EMBY forums
podonnell 32 Posted October 16 Posted October 16 I am pretty sure my configuration is good but I wanted to check in here to validate something I saw -- recently set up an external client and I'm seeing Emby for Apple TV 1.9.0 Apple TV 72.231.19.117 http/1.1 I changed the above IP to a random one, but the key here is the http. My stack is --> DDNS service --> Caddy --> Emby My understanding is that I'm seeing http because the connection is technically from Caddy to Emby, which is internal. I believe I can see the external IP due to a setting with caddy that allows me to see the originating IP? Most importantly, there's no access to my server via IP or DNS name over HTTP when I tested. I can only get in https Further, the only rule on my firewall is for Caddy, which is HTTPS Just wanted to validate why I am seeing the http above, and again -- I believe that's because it's technically speaking to caddy via http on my internal network only?
darkassassin07 519 Posted October 16 Posted October 16 The 'http' here isn't https vs http, it's just denoting http protocol version 1.1 is being used. That may or may not be wrapped in a ssl/tls layer to make it into https (probably is if you're using a proxy in front), but that won't be shown there. 1 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now