That page does mention using an IP address, but it is for the initial server installation process. It does not mention any server disappearing or expired credentials, or that steps on that page might be part of the solution to it. That page is not what comes up when doing a search for my problem. I did searches for weeks and could not resolve it on my own, which is why I posted here. I really think the docs need improvement.
Search string: âsite:support.plex.tv unable to access serverâ
The article initially suggested is the first one listed on DuckDuckGo and the second on Google. Changing to âsite:support.plex.tv canât access serverâ itâs the second hit on both engines. I know that using the âsite:â modifier in searches isnât used a great deal (in my experience) but it can really help narrow results. Especially in this case as, for whatever reason, support.plex.tv doesnât seem to indexed very well by search engines. Or forums.plex.tv for that matter. Redditâs SEO game is strong.
But why struggle with it for weeks to begin with? I mean, I understand that itâs nice to figure out things for ourselves, but waiting for weeks to ask for assistance seems⊠unnecessary.
Iâm not picking on you and admire the tenacity. Iâm very much a âlearn by doingâ person myself. But it seems like youâre tilting at windmills here. You asked for assistance and had the information you needed to resolve your issue within five posts (two of which were made by you). If you feel the documentation is inadequate, comment on the article. Thereâs a Yes/No question at the bottom of every one; if you select âNoâ youâre given the opportunity to provide feedback.
And, in my opinion, the document is fine. It clearly outlines the steps required to recover from the issue; itâs not meant be an exhaustive guide which duplicates the installation document. As such, it links to other appropriate documents for further information. This is how good documentation works, in my opinion. (I do very much agree with you that some of the color/contrast choices do need an overhaul to improve readability.)
At any rate, Happy Plexing!
1 Like
Thanks.
I really appreciate getting the answer quickly after posting ! Itâs just that I wish I didnât have to post. The reason I waited that long to post is that it wasnât a high priority thing to fix - there are many other things going on in my life than Plexing.
Reddit is definitely polluting the google searches. I looked at my google search history. I searched for âplex media server missing from plex.tvâ. Once I added +support.plex.tv to the query, the first link that came up was https://support.plex.tv/articles/204604227-why-can-t-the-plex-app-find-or-connect-to-my-plex-media-server/ .
I still think the content on that support page is inadequate in its current state.
-
it only covers the URL to use if the browser is on the same computer.
-
one of the 2 examples uses localhost in the URL. That is a hostname, not an IP address, usually defined in /etc/hosts . I expected that using another hostname, one defined in the local DNS server, not /etc/hosts, would also work.
-
There is no hint that one needs to click the related pages to figure out how to properly access the server from a different host
-
if one actually knows of the need to click âload the bundled version of the Plex web appâ, it leads to https://support.plex.tv/articles/200288666-opening-plex-web-app/ . The example given for a remote browser does show using an IP address, and not a local DNS hostname.
What I wish would change in the docs :
- this page : https://support.plex.tv/articles/204604227-why-can-t-the-plex-app-find-or-connect-to-my-plex-media-server/ should either cover both the case of using a local browser or remote browser, or neither, and provide a link to the second page to do so.
- there should be a big red warning at https://support.plex.tv/articles/200288666-opening-plex-web-app/ that local DNS names canât be used with remote browsers. IP addresses and hostnames are often used interchangeably, as they are for the local browser case.
Of course, I would much prefer if local DNS hostnames just worked in the first place, and none of this was an issue. Having to manually lookup the IP is a PITA. Computers are supposed to automate things. Thatâs the job of a DNS server. And being forced to add /web to the URL when the server is orphaned is totally unintuitive, too.
I appreciate the thoughtful response. Thanks!
Regarding the use of local DNS hostnames, they do work generally, just not during the claiming process. Itâs a security consideration where the Plex server looks at the HTTP headers at the target domain. If itâs one it doesnât recognize it assumes non-local access.
Since non-local access is precluded for the purposes of claiming, bare IP addresses must be used. I know it could look at the source IP address. But itâs trying to eliminate extreme edge cases.
Think badly configured reverse proxies or routers with really, really dumb DNAT and SNAT rules. The time period when a server is unclaimed is fairly sensitive, particularly when someone has decided to start enabling remote access ahead of time (setting up port forwarding, or reverse proxies). Plex has made the choice to limit this function (claiming) to clients on the same (logical) network, to the IP of the server. Or localhost (127.0.0.1) if on the same host. Like it or lump it, thatâs how it is.
For what itâs worth, I hope your documentation concerns are addressed, or at least explained, to your satisfaction. While they seem perfectly fine to me, there is always room for improvement.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
