Wanted to check for PMS updates, was trying to find out why the plex media server can’t find the local server, had worked for a few months w/o any changes to the PC other than antivirus definition updates.
Can’t get past the PMS web app, get "Thanks! You have successfully signed in. You will be redirected automatically.
Never goes past that point.
Can’t this craptacular web app interface be bypassed?
Can’t this thing give out any helpful information?
Seems the only thing you can do is to repair or uninstall & reinstall and hope it works.
Capturing browser dev console should help find out where the loop is. Don’t know what browser you have but the dev console is normally opened through F12 and one can save the requests and responses to a file. If you can get screenshot and do that, it would help find the issue - there may be security passwords in the trace - so please send to me by private message. See section on Console Logs here https://support.plex.tv/articles/201611836-plex-web-app-logs/
With regards to your server, have you renamed your server and do you have two? Your account has links to NUC-0924 FLR and NUC-0924
If your server is running, you can try to get to it through the local IP or localhost on the server itself.
Also if the browser session has authenticated, you should be able to change the url to point to the server
For http the url would be http://local-ip-of-server:32400/web or on the server itself, http://localhost:32400/web
I am having this same issue - After the 1.12.0.4829 update, I am not able to reach my server settings.
I can access it locally on via the web but when I try to go to server settings the page redirects me to login
I am using chrome and it’s up to date.
I copied the Dev Console log from Firefox, and removed anything I thought might be personally identifiable: https://pastebin.com/L0WeH36F
This is connecting to a Raspberry Pi which I know is unofficial, but the exact same thing happened on my Windows 10 desktop with the same version until I rolled back the server version.
This happens when you load the “main” Library page, as well as the “General” Server settings page.
If you hit escape a the right time to allow the Library to load, you can navigate as normal.
But the “General” Server settings page will always trigger a redirect to plex.tv.
There were issues with the authentication servers in the last few days which are resolved now.
The dev console for firefox was running on which machine?
I can see it trying to connect to server on 127.0.0.1 and a server on 192.168.1.200
Was their a server on localhost?
It has found server named OSMC but is showing as both 127.0.0.1 and 192.168.1.200
So what IP is the server you are trying to access ?
I can these errors
[Connections] Testing connection for OSMC at http://127.0.0.1:32400
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:32400/?X-Plex-Product=Plex%20Web&X-Plex-Version=3.37.2&X-Plex-Client-Identifier=XXXXXXXXXX&X-Plex-Platform=Firefox&X-Plex-Platform-Version=59.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Plex%20Web%20%28Firefox%29&X-Plex-Device-Screen-Resolution=1920x25%2C1920x1080&X-Plex-Provider-Version=1.1. (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘app.plex.tv’).
[Connections] [Loopback] is unavailable at http://127.0.0.1:32400 (Status 0)
[Connections] All connections to [Loopback] failed
@twotimeassassin said:
I am having this same issue - After the 1.12.0.4829 update, I am not able to reach my server settings.
I can access it locally on via the web but when I try to go to server settings the page redirects me to login
I am using chrome and it’s up to date.
see screenshot
There were replication issues with the logon servers earlier this week. This was resolved. Is the problem still there?
@sa2000 said:
There were issues with the authentication servers in the last few days which are resolved now.
The dev console for firefox was running on which machine?
I can see it trying to connect to server on 127.0.0.1 and a server on 192.168.1.200
Was their a server on localhost?
It has found server named OSMC but is showing as both 127.0.0.1 and 192.168.1.200
So what IP is the server you are trying to access ?
Is there any proxy?
I have two machines, both with Plex Servers:
Windows 10 PC - 127.0.0.1 - Version 1.10.0.4523
OSMC on RasPi - 192.168.1.200 - Version 1.12.0.4829
I do not have any proxies.
Firefox was running on my Widnows 10 PC.
Authentication should be disabled on both Windows 10 and OSMC servers.
Windows 10 PC had the same issue when running v1.12, the problem went away when I installed an older version.
I exited the Plex Server on my Windows PC, and connected to the OSMC Server: https://pastebin.com/HQ2wp31B
The log does not show the Cross-Origin Request, but still redirects to plex.tv.
I don’t believe it has to do with authentication, as both servers should have it disabled via Addresses allowed without authentication 192.168.1.0/255.255.255.0
@sa2000 said:
There were issues with the authentication servers in the last few days which are resolved now.
The dev console for firefox was running on which machine?
I can see it trying to connect to server on 127.0.0.1 and a server on 192.168.1.200
Was their a server on localhost?
It has found server named OSMC but is showing as both 127.0.0.1 and 192.168.1.200
So what IP is the server you are trying to access ?
Is there any proxy?
I have two machines, both with Plex Servers:
Windows 10 PC - 127.0.0.1 - Version 1.10.0.4523
OSMC on RasPi - 192.168.1.200 - Version 1.12.0.4829
I do not have any proxies.
Firefox was running on my Widnows 10 PC.
Authentication should be disabled on both Windows 10 and OSMC servers.
Windows 10 PC had the same issue when running v1.12, the problem went away when I installed an older version.
I exited the Plex Server on my Windows PC, and connected to the OSMC Server: https://pastebin.com/HQ2wp31B
The log does not show the Cross-Origin Request, but still redirects to plex.tv.
I don’t believe it has to do with authentication, as both servers should have it disabled via Addresses allowed without authentication 192.168.1.0/255.255.255.0
Thank you for your help.
If this is still an issue, would like to see corresponding logs from web and the server so can compare the timestamps - on web enable verbose logging (settings / web / show advanced / debug ) and for Plex Media Server just debug would be sufficient.
Starting with fresh logs for PMS after restart.
And with verbose logging in web and also the web console logging - get to the point of the problem arising. Take a full screenshot (do not crop - as need to see url and time)
and see if you can get to settings / web / show advanced / debug/ view logs and select all and copy to text file
and save the web console network logging and let me see that together with the server logs zip
@sa2000 said:
If this is still an issue, would like to see corresponding logs from web and the server so can compare the timestamps - on web enable verbose logging (settings / web / show advanced / debug ) and for Plex Media Server just debug would be sufficient.
I will work on getting this, but it’s a giant pain. To navigate the settings menus you have to hammer the Escape key to stop it from redirecting, which has caused PlexMedia Server to stop responding twice today.
If you’re willing to, you can reproduce this yourself:
1). Navigate to your Plex server in your browser
2). Settings > Server > Network > List of networks that are allowed without auth
3). Add your local IP or IP Mask (i.e. 192.168.1.0/24)
4). Sign out of your account on the Plex Server
5). (Maybe?) Close the tab, open a new tab and navigate to your Plex server again
Yeah… so basically the Plex team knows of the issue, but because “it’s a feature” nothing will be done?
This basically removes the ability to manage the server if you’re not logged in. I can’t help but feel this is all for data collection/analytics purposes, which in light of Facebook should make everyone on both sides stop and think for a minute.
if it is going to web/index.html#!/setup/XXXXXXXXXX then it means it is a first run new server scenario
and yes you do need to access plex.tv currently for first run - this has already been raised and it is independent of whether allowed networks field has exemption
As this is already registered as an issue - I am only interested if it is happening to an existing previously setup server and not one that is being setup now
@sa2000 said:
If this is still an issue, would like to see corresponding logs from web and the server so can compare the timestamps - on web enable verbose logging (settings / web / show advanced / debug ) and for Plex Media Server just debug would be sufficient.
I will work on getting this, but it’s a giant pain. To navigate the settings menus you have to hammer the Escape key to stop it from redirecting, which has caused PlexMedia Server to stop responding twice today.
If you’re willing to, you can reproduce this yourself:
1). Navigate to your Plex server in your browser
2). Settings > Server > Network > List of networks that are allowed without auth
3). Add your local IP or IP Mask (i.e. 192.168.1.0/24)
4). Sign out of your account on the Plex Server
5). (Maybe?) Close the tab, open a new tab and navigate to your Plex server again
@sa2000 said:
If this is still an issue, would like to see corresponding logs from web and the server so can compare the timestamps - on web enable verbose logging (settings / web / show advanced / debug ) and for Plex Media Server just debug would be sufficient.
I will work on getting this, but it’s a giant pain. To navigate the settings menus you have to hammer the Escape key to stop it from redirecting, which has caused PlexMedia Server to stop responding twice today.
If you’re willing to, you can reproduce this yourself:
1). Navigate to your Plex server in your browser
2). Settings > Server > Network > List of networks that are allowed without auth
3). Add your local IP or IP Mask (i.e. 192.168.1.0/24)
4). Sign out of your account on the Plex Server
5). (Maybe?) Close the tab, open a new tab and navigate to your Plex server again
@sa2000 said:
If this is still an issue, would like to see corresponding logs from web and the server so can compare the timestamps - on web enable verbose logging (settings / web / show advanced / debug ) and for Plex Media Server just debug would be sufficient.
I will work on getting this, but it’s a giant pain. To navigate the settings menus you have to hammer the Escape key to stop it from redirecting, which has caused PlexMedia Server to stop responding twice today.
If you’re willing to, you can reproduce this yourself:
1). Navigate to your Plex server in your browser
2). Settings > Server > Network > List of networks that are allowed without auth
3). Add your local IP or IP Mask (i.e. 192.168.1.0/24)
4). Sign out of your account on the Plex Server
5). (Maybe?) Close the tab, open a new tab and navigate to your Plex server again
@sa2000 said:
If this is still an issue, would like to see corresponding logs from web and the server so can compare the timestamps - on web enable verbose logging (settings / web / show advanced / debug ) and for Plex Media Server just debug would be sufficient.
I will work on getting this, but it’s a giant pain. To navigate the settings menus you have to hammer the Escape key to stop it from redirecting, which has caused PlexMedia Server to stop responding twice today.
If you’re willing to, you can reproduce this yourself:
1). Navigate to your Plex server in your browser
2). Settings > Server > Network > List of networks that are allowed without auth
3). Add your local IP or IP Mask (i.e. 192.168.1.0/24)
4). Sign out of your account on the Plex Server
5). (Maybe?) Close the tab, open a new tab and navigate to your Plex server again
@sa2000 said:
A fix will be released in a new version of Plex Web that will be bundled within Plex Media Server. It would get released as beta initially
The issue affects servers that are not signed in. Until the fix is released, you need to have the server signed in and claimed
I don’t mean to sound impatient, I completely understand having a “buffer” of testing versions before public release, but as of 1.12.3.4973 (2018/04/12) this is still not fixed. I am not asking for a specific ETA, just a rough timeline; Is this fix in an update that we should see publicly in days/weeks, or will it take longer?
Thank you again for your help, and I hope you’re having a good day!
@sa2000 said:
A fix will be released in a new version of Plex Web that will be bundled within Plex Media Server. It would get released as beta initially
The issue affects servers that are not signed in. Until the fix is released, you need to have the server signed in and claimed
I don’t mean to sound impatient, I completely understand having a “buffer” of testing versions before public release, but as of 1.12.3.4973 (2018/04/12) this is still not fixed. I am not asking for a specific ETA, just a rough timeline; Is this fix in an update that we should see publicly in days/weeks, or will it take longer?
Thank you again for your help, and I hope you’re having a good day!
The fix is out already and there is no other fix waiting to come out
The fix went in the Plex web app version 3.41.2 that was bundled in Plex Media Server 1.12.3.4973 which was beta released on 13 April (for my region) and went public to everyone on 18 April 2018
See http://forums.plex.tv/discussion/comment/1655957/#Comment_1655957
Please note:
If the server is signed in to plex.tv (you can see that in settings / server / general, then all plex client apps must authenticate with the plex.tv account - you can whitelist specific local network IP Addresses or the local subnet through server setting List of IP addresses and networks that are allowed without auth which is within the advanced server network settings
If the server is not signed in to plex.tv, then client apps can access the server without authentication, provided they are on the same local network which must be on a subnet within the true definition of the Private Network (Private network - Wikipedia)
