Please start another thread so it doesn’t convolute mine that I don’t get a response back, thanksssss
I was already moving it when I saw the post. Sorry for being so slow to break apart.
Thanks, any ideas with the last post i made with debug logs?
I had a friend send me his logs to compare, this is what i see in his:
DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
DEBUG - Relay: read 110 cached entries from hosts file
DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1
DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
DEBUG - MyPlex: updating with 103 access tokens
DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
DEBUG - HTTP requesting GET https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1
Compared to mine:
DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
DEBUG - Relay: read 0 cached entries from hosts file
DEBUG - Grabber: Cleaning up orphaned grabs.
DEBUG - Grabber: Cleaned up 0 decrepit directories in 0.0 sec.
DEBUG - Opening 1 database sessions to library (), SQLite 3.26.0, threadsafe=1
DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=
DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
Additionally, I see in his logs that an SSL is “installed” but i don’t see any of that on my server logs:
DEBUG - CERT: Installed certificate with fingerprint XXX.
DEBUG - CERT: Installed new private key.
DEBUG - CERT: Subject name is /C=US/ST=California/L=Los Gatos/O=Plex, Inc./CN=*.XXX.plex.direct
DEBUG - CERT: OCSP requests for stapling will be made to 'http://ocspx.digicert.com/'.
INFO - OCSP: Successfully retrieved response from cache.
DEBUG - CERT: Installed intermediate certificate.
My first question is this “hosts” file the logs talk about – is that some kind of internal host file? My /etc/hosts
file is just a standard host file
From everything I can tell, the problem is that PMS is trying to make a request without any kind of X-Plex-Token
… what could cause that? Why is it not sending request with any token? Seems an issue with connection to Plex (which wouldn’t be an issue if we weren’t forced to login through plex.tv)
Regarding the installation problems some are seeing, We did find a couple servers (EU it seems) didn’t update correctly. We (re) pushed the files and is reported by one user to be ok now.
speaking to the 127.0.0.1 problem,
If a full SSH-tunnel is setup (even on local LAN), and web browser traffic sent through it, what is the result?
ssh -L 8888:127.0.0.1:32400 ip.addr.of.host
sign in and let sit
Followed by: http://127.0.0.1:8888/web in the browser
Connected via SSH tunnel, then accessed http://127.0.0.1:8888/web
then it tries to direct me to:
http://127.0.0.1:8888/web/index.html#!/setup/XXXXX
Where XXXXX is the ProcessedMachineIdentifier
from my server’s Preferences.xml
Which then instantly redirects me to plex.tv to login, and then back to that URL above (after logging in), which then again gives me the “No soup for you”
So I just realized that your comment:
a. – This means “Select another user” → “What’s This?” (lower right corner) → Accept limited functionality.
The What's This?
was showing on the Plex.tv login page, so i was able to get past doing an actual login (not sure how i missed that, probably was looking for “Select another user” instead of “What’s This?”).
I’m guessing this only shows up when your accessing it “locally”? I don’t see it when trying to setup via the IP address.
Although I see this in the console logs on the final “finish” step, it appears it’s trying to connect via the 32400 port:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:32400/media/providers?X-Plex-Product=Plex%2…ce-Screen-Resolution=1920x983%2C1920x1080&X-Plex-Language=en. (Reason: CORS request did not succeed)
And just sits on the finish with loading button. I went ahead and retried it with 32400 as port forward locally, and going to wait to see if it does anything (I have a very large media library)
OMG YES IT WORKS!
Thank you @ChuckPa along with your help, I was finally able to get this resolved!
For anybody coming across this having a similar issue, here’s what I had to do to resolve the problem. You may not need to do all of these steps, but for me I had to.
- Remove the server from your account app.plex.tv under “Authorized Devices”
- Stop the plexmediaserver service
service plexmediaserver stop
- Rename
/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Preferences.xml
to something like/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Preferences.xml.old
(just to have a backup) - Start PMS
service plexmediaserver start
- Open an SSH tunnel from your local laptop/desktop to the server
Where10.0.0.2
should be the IP of your PMS server,root
as username (or use another user):
ssh -L 32400:127.0.0.1:32400 root@10.0.0.2
If you have SSH running on a different port, use-p 222
where222
is the port:
ssh -L 32400:127.0.0.1:32400 -p 222 root@10.0.0.2
- Open a web browser to
http://127.0.0.1:32400/web?secure=0
- Login with your Plex.tv login
- Follow the setup process, as long as you didn’t remove all the data from your
/var/log/plexmediaserver/
directory it should still have all your media setup - Goto Users & Sharing and re-share with any users (users should still be there just no longer with a share since your “server” id has changed (by renaming
Preferences.xml
in step 3 it auto generates a new one) - Profit!
For some reason this would not work for me unless I specifically was connected over an SSH tunnel … I don’t know why, but trying to do it from the IP of the server on a laptop/desktop would not work.
Thanks again @ChuckPa for all your help!
SSH tunnel always works for other hosts (local or remote) because it puts your browser on the loopback (as if it were on the graphics desktop) of the host.
Also, to all finding this thread: The services bundle ZIP failed to deploy properly.
We’re looking into the root cause and why the deployment automation didn’t catch & resolve it.
Maybe that along with what i marked as the solution is why it’s working now? Maybe it’s not requiring the SSH tunnel? Not sure but either way it works now and that made my day
It was trying to do both:
- Auth
- Update the services bundle.
Auth killed it for certain. The services bundle just added insult to injury. Since the title here is similar to other threads, I’m slightly cross posting information.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.