dizquetv
dizquetv copied to clipboard
vexorian
Plex Localhost gives UI Route error | SSL Related
Logs: https://gist.github.com/bakerboy448/ba956550674e709b057c8a422318a671
uri entered
http://localhost:32400
| Component | Version |
|---|---|
| dizqueTV-backend | 1.4.1 |
| dizqueTV-ui | 1.4.1 |
| FFMPEG | 4.2.4-1ubuntu0.1 |
Plex Version 1.22.1.4228
OS Ubuntu 20.04
the SSL certificate doesn't use localhost. So it is better to use the blahblahblah.plex.direct addresses to avoid SSL errors. The alternative if you really want to use localhost would be to use a http proxy or a custom SSL certificate
It's my understanding, and plex docs seem to confirm, there is an ability to access it locally without HTTPS. Given an HTTP URL is entered, HTTPS should not be used and thus this issue should not exist. Thus it appears to be a bug.
https://support.plex.tv/articles/200288666-opening-plex-web-app/
Any updates or any additional information I can provide?
The workaround with plex direct is reasonable, but illogical if they are on the same device.
This would also be unnecessary external traffic; no?
I was hoping to give it a further look when I have time for dizqueTV development.
Anyway, something interesting ... The UI route is not checked by the backend but by the front end. So it is possible that the logs were not related to it. Try again and this time check both the terminal logs AND the web browser's web developer console logs.
alright I think I see it
GET https://localhost:32400/ net::ERR_CONNECTION_REFUSED
That makes sense if it's trying to connect via my local browser to localhost given the server is remote.
on a likely unrelated note; I have dizquetv toss up behind an nginx RP w/ LE SSL, and console logs have issues with the images loading due to mixed content.
Mixed Content: The page at 'https://(mydomain)/#!/guide' was loaded over HTTPS, but requested an insecure image 'http://(my ip):8000/images/dizquetv.png'. This content should also be served over HTTPS.
I can open a new GHI for that if needed.
I think all of this really boils down to some edge case handling needed for users with remote, non-local servers.
Use Cases
- Plex local, dizquetv local, access to interface local
- Plex remote, dizquetv local, access to interface local
- Plex remote, dizquetv remote, access to interface local
The first use case I'm sure you have well covered; the second seems like it'd work as well; the third is the gap in functionality it seems.
Love the app regardless and very happy to see it. Hopefully you get more time to improve it even more! I'd consider it a very useable beta state right now (Similar to the state of Sonarr v3 for the last few years prior to it's formal release last month.)
