XTeve is protected, but the URL needs to be public
Maybe I'm missing something obvious, but Xteve is set up as a protected app that requires login to access. The problem is that after you set it up, it gives you a URL to put into plex that is expected to be public, otherwise plex can't find it.
I'm confused what to do here. Am I able to make the app public?
25 Replies
hey @androbwebb 🙂
one sec, checking...
it's been a while, but https://elfhosted.com/how-to/connect-apps/#xteve says you just use
xteve:34400 in plex...Connect Apps
While each app is reachable externally as https://-.elfhosted.com, within your namespace, each app is reachable to each other app on its own hostname and port, as described below.
I think that only works if I’m hosting Plex also on ElfHosted as it’s a container URL. I have it hosted elsewhere.
aah, I see
Sorry, I should have mentioned that
then yes, we need to expose it - does xteve have a trustworthy auth layer?
Hmm.. trustworthy, I’m not sure. But they have something. They have an option in their app for preventing web UI access without credentials. Although it’s just a checkbox, I don’t see anywhere that I can actually configure the credentials.
mmm, without feeling certain that we're not opening your apps up to random scallywags on the internet, we can't really remove SSO...
let me have a poke around with my instance...
Is there a way I could pass the credentials to login to the instance via URL?
maaaaaybe, assuming it supports the https://user:password@blah syntax..
(as you can probably tell, I'm not a regular user!)
GitHub
xTeVe-Documentation/en/configuration.md at master · xteve-project/x...
Contribute to xteve-project/xTeVe-Documentation development by creating an account on GitHub.
looks like it, one of the examples is
DVR IP: username:[email protected]:34400here's a product which will disable SSO for XTeve, once you've confirmed you've secured it adequately: https://store.elfhosted.com/product/xteve-exposed/
legolas
ElfHosted Store
XTeve (Exposed!) | ElfHosted Store
This product is intended to be purchased on top of XTeve, and will allow the public exposure of XTeve without SSO. To this end, it’s mandatory that you enable the requirement for credentials for any XTeve access, and confirm it works before purchasing this product. Type in confirmation (“Yes I have secured XTeve”) below:
Hmm, ok. That’s promising. Ok, it seems like when I click that checkbox to turn on auth it’s just the first user to sign up that gets admin access. Lemme try to add that now then.
Perfect! Thanks!
if you're running plex externally, you might also be interested in the custom domain support we added to overseerr / jellyseerr yesterday - it'll be covered in today's blog post
Oh cool. I'll check it out!
Thanks again for all your help here. Amazing product you have - as a developer who hates the DevOps parts of my job, this is beautifully designed.
heh, thank you 🙂 Have you played with the kubernetes dashboard yet?
that'll really light up your devops twitches...
Yeah! At first I thought it was a built-in feature of k8, but then realized it's custom built!
Btw, should I be expecting to see a new entry for the
Exposed app, or does it just modify the existing Xteve app?
well, not by me, it's just a slightly hacked version of https://github.com/kubernetes/dashboard
GitHub
GitHub - kubernetes/dashboard: General-purpose web UI for Kubernete...
General-purpose web UI for Kubernetes clusters. Contribute to kubernetes/dashboard development by creating an account on GitHub.
It'll just change the hover color of the exist app, to indicate it's now exposed/public
mmm, minor bug, sec...
doh
xteveeexposed:
I used one too many e's
(been looking at too many arr products!)haha! No worries. Lemme know if I need to do anything on my side
ok, sorted
I fixed it manually this time, and fixed the SKU in the store (which is how the YAML is generated), so it should be OK after your 24-hour renewal tomorrow - if not, you'll need to delete the sub and just re-subscribe to fix it (there's only so much we can do with wordpress!)
Perfect, just tested it. Hah, no worries.
đź‘Ť