# There was an error signing in

**URL:** <https://forums.plex.tv/t/there-was-an-error-signing-in/230138>\
**Category:** General Discussions\
**Created:** [March 24, 2018, 4:32am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138 "2018-03-24T04:32:28Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [March 24, 2018, 4:32am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/1 "2018-03-24T04:32:28Z")

</div>

Since a week ago when I start my PMS locally over the taskbar icon as usual, the local address of PMS is called:  
[http://127.0.0.1:32400/web](http://127.0.0.1:32400/web) initially, but after 1 second (attempting to load the start page of PMS) I get an error message:

[There was an error signing in]

Before the error occurs, the local address in the browser address bar changes to a humangeous address line of about 500 chars:

[https://app.plex.tv/auth/#!clientID=fr33vlhn15cvdmt4etixwq8x&context[device][product]=Ple](https://app.plex.tv/auth/#!clientID=fr33vlhn15cvdmt4etixwq8x&context%5Bdevice%5D%5Bproduct%5D=Ple) … and so on… and so on…

If I just call the first part of the address:  
[https://app.plex.tv/](https://app.plex.tv/)  
it’s OK and it loggs me in as usual and the address doesn’t change.  
So I could always start the web page of PMS with [https://app.plex.tv/](https://app.plex.tv/) or even use a bookmark favorite to this but it’s a few unconvenient clicks more as I have to start the browser first and it’s weird why it should not work the way it used to a week ago and before.

Where can I change this behaviour? It seemes like a server internal routing like you know in the hosts-file (C:\windows\sytem32\drivers\etc\hosts) but my hosts-file is unmodified (standard).  
So I assume it’s in the PMS web server config somewhere?

Any help appreciated.

Thank you.

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [March 25, 2018, 11:40am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/2 "2018-03-25T11:40:26Z")

</div>

Who do I have to ■■■■ to finally get support here?

> **[Paid Support](https://forums.plex.tv/discussion/315154/paid-support#latest)**
>
> I paid for the Lifetime membership. Even then it is hard to get an answer from support unless the answer is very quick and simple (IE there is already a link in the documentation someone can send over). Is there a tier I should be paying for on top...

Tell me if and what kind of information is needed to solve the problem.

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 4, 2018, 10:31am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/3 "2018-04-04T10:31:13Z")

</div>

Is there anybody out there?

---

<div class="post-metadata">

**Author:** ![lanboyguyton](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/lanboyguyton/32/3232_2.png) [@lanboyguyton](https://forums.plex.tv/u/lanboyguyton)\
**Post date:** [April 4, 2018, 4:51pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/4 "2018-04-04T16:51:25Z")

</div>

I remember this happening to me before. I believe I substituted the loopback address with the server address. I don’t think it should ask for authentication. however, in “Network” in server settings, you can identify your LAN networks and even add the own server’s address in the “List of IP addresses and networks that are allowed without auth” field. But that might be overkill.

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 4, 2018, 6:48pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/5 "2018-04-04T18:48:01Z")

</div>

Thx lanboyguyton.  
I’m using Win10 x64 as PMS. So not really “server settings” there as it would be on a Win Server. I’m curious if there is such a setting on the PMS confug somewhere?

---

<div class="post-metadata">

**Author:** ![lanboyguyton](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/lanboyguyton/32/3232_2.png) [@lanboyguyton](https://forums.plex.tv/u/lanboyguyton)\
**Post date:** [April 4, 2018, 7:05pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/6 "2018-04-04T19:05:09Z")

</div>

Yes, there is, that’s actually what I meant, sorry.  
If you click the wrench icon in plex web then click on the server tab, that’s what I meant for Server Settings.  
 ![](https://global.discourse-cdn.com/plex/original/3X/d/1/d1c31c812a4246636e7512b6b03d79597f9357c1.png)

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 6, 2018, 8:49pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/7 "2018-04-06T20:49:58Z")

</div>

Thank you. I must have missunderstood 🙂

But, unfortunately none of the settings that I tried over the WebUI under [Server] - [Network] did solve the problem.  
I tried putting 127.0.0.1, 192.168.1.50 (my local LAN-IP)  
also tried own Web-URL: [https://app.plex.tv/desktop](https://app.plex.tv/desktop) in the appropriate section.  
Of course SAVED settings and even restarted the PMS.

But everytime I try to call PMS WebUI over the ICON from the taskbar the problem persists. The same whenever I enter: [http://127.0.0.1:32400/web](http://127.0.0.1:32400/web) in any browser - oh yeah did I mention - it’s the same problem with IE 11 / EDGE and CHROME. Vice versa [https://app.plex.tv/desktop](https://app.plex.tv/desktop) works on all mentionned browsers.

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 6, 2018, 11:44pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/8 "2018-04-06T23:44:35Z")

</div>

I am aware of a problem with the version of Plex Web that is bundled with Plex Media Server (the one that responds to `http://127.0.0.1:32400/web` or `http://local-ip-of-pms:32400/web` where if the server is unclaimed, there would be a request to authenticate to access the server. This will be fixed in bundled Plex Web 3.41.2 which is expected to be bundled into the next release of Plex Media Server (1.12.3)

The hosted web app ([https://app.plex.tv](https://app.plex.tv)) is already at a later version

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 7, 2018, 10:39am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/9 "2018-04-07T10:39:06Z")

</div>

Thanks sa2000.

> I am aware of a problem with the version of Plex Web that is bundled with Plex Media Server (the one that responds to `http://127.0.0.1:32400/web` or `http://local-ip-of-pms:32400/web` …

I have version Web: 3.44.1 / Server: 1.12.0.4829.  
Are there “unbundled” versions around that don’t respond to `http://127.0.0.1:32400/web` or `http://local-ip-of-pms:32400/web` or how do you meant that? Sorry my native language is german. Maybe I just don’t understand it right.

> where if the server is unclaimed, there would be a request to authenticate to access the server.

When is a PMS unclaimed? Why? Why did this happen with this version? Why only me? Are there ways to reclaim it or only with the next fix?

> This will be fixed in bundled Plex Web 3.41.2 which is expected to be bundled into the next release of Plex Media Server (1.12.3)

When can we expect Server v 1.12.3? Bundled with 3.41.2??? I already have 3.44.1.

> The [hosted web app](https://app.plex.tv/) ([https://app.plex.tv](https://app.plex.tv)) is already at a later version

So, when I get it right I have the [hosted web app](https://app.plex.tv/)? Or more precisely I have the bundled AND the hosted Plex web and whenever the bundled one is called, the problem happens?

Would be great if you could explain all questions (if you can).

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 7, 2018, 12:08pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/10 "2018-04-07T12:08:12Z")

</div>

Updated to Server 1.12.2.4929 which still has Web 3.44.1 and the problem still persists.

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 7, 2018, 12:37pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/11 "2018-04-07T12:37:24Z")

</div>

> @RazorPlex said:  
> Updated to Server 1.12.2.4929 which still has Web 3.44.1 and the problem still persists.

There are two different versions of the web app

Version 3.44.1 is the one you get from the cloud hosted app available through url `https://app.plex.tv` and `https://plex.tv/web`

Version 3.39.5 is the current bundled version (one embedded in Plex Media Server and released with it) - it is used when you go through urls `http://localhost:32400/web` or `http://127.0.0.1:32400/web` or `http://192.168.1.50:32400/web`

I see in plex.tv settings for your server that you have added a `Custom Server access URL` of `app.plex.tv` - this would only complicate matters and troubleshooting issues and may actually be the reason you have issues - please clear the field (in Settings / Server / Network / Show Advanced) and save changes and restart the server

> When is a PMS unclaimed? Why? Why did this happen with this version? Why only me? Are there ways to reclaim it or only with the next fix?

A server is unclaimed if settings / server / general shows it as not signed in to plex.tv

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 7, 2018, 12:48pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/12 "2018-04-07T12:48:39Z")

</div>

> So, when I get it right I have the [hosted web app](https://app.plex.tv/)? Or more precisely I have the bundled AND the hosted Plex web and whenever the bundled one is called, the problem happens?

> Would be great if you could explain all questions (if you can).

Once the `http://app.plex.tv` or `https://app.plex.tv` is removed from your server `Custom Server Access URL` - then we are in a standard configuration and can take it from there. I do not know the implications and impact of having that in the custom access url field. It was not intended to have this but to have your own domain or perhaps a vpn ip address

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 7, 2018, 2:49pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/13 "2018-04-07T14:49:23Z")

</div>

The reason why I set a custom URL is because the tip of @lanboyguyton above - so after the problem. Before I had nothing in there (standard config).

> @lanboyguyton said:  
> I remember this happening to me before. I believe I substituted the loopback address with the server address. I don’t think it should ask for authentication. however, in “Network” in server settings, you can identify your LAN networks and even add the own server’s address in the “List of IP addresses and networks that are allowed without auth” field. But that might be overkill.

Now I changed it back to standard configuration, which of course didn’t change anything concerning the problem.

Would any logfile give more insight to the errors source?

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 7, 2018, 4:14pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/14 "2018-04-07T16:14:10Z")

</div>

I now activated IPv6 as DualStack on my Router just to see if it helps and then restarted all.

Now the URL in the browsers address bar stays unchanged as initially called:  
[http://127.0.0.1:32400/web/index.html](http://127.0.0.1:32400/web/index.html)  
but a new error message with an exclamation mark within a triangle is saying (translated from the german error message):

PLEX is not available due to maintenance.  
But no worries it won’t take long.

status.plex.tv

…which is a false negative because I can still call my PMS over [https://app.plex.tv/desktop](https://app.plex.tv/desktop) and it’s also reachable from PLEX apps outside my LAN.

Find attached the console-output from the Chrome browser after reproducing the error:

---

<div class="post-metadata">

**Author:** ![The\_Wicked\_One](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/the_wicked_one/32/4703_2.png) [@The\_Wicked\_One](https://forums.plex.tv/u/The_Wicked_One)\
**Post date:** [April 7, 2018, 4:37pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/15 "2018-04-07T16:37:33Z")

</div>

all with same error

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 7, 2018, 7:04pm UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/16 "2018-04-07T19:04:22Z")

</div>

> @RazorPlex said:  
> I now activated IPv6 as DualStack on my Router just to see if it helps and then restarted all.
> 
> Now the URL in the browsers address bar stays unchanged as initially called:  
> [http://127.0.0.1:32400/web/index.html](http://127.0.0.1:32400/web/index.html)  
> but a new error message with an exclamation mark within a triangle is saying (translated from the german error message):
> 
> PLEX is not available due to maintenance.  
> But no worries it won’t take long.
> 
> status.plex.tv
> 
> …which is a false negative because I can still call my PMS over [https://app.plex.tv/desktop](https://app.plex.tv/desktop) and it’s also reachable from PLEX apps outside my LAN.
> 
> Find attached the console-output from the Chrome browser after reproducing the error:

It is unfortunate that there was an outage today - see the chart for the plex.tv application on [http://status.plex.tv](http://status.plex.tv)

Could we repeat the test now and get fresh dev console log from chrome  
May be this is the issue but need to see if it is present when the plex.tv site is operational  
Looks like some Symantec check on certificate

```auto
main-1-5e147fb05f10a421c106-plex-3.39.5-cafe702.js:2637 [Servers] Found all servers = plex.tv
index.html:1 The SSL certificate used to load resources from https://api.webtest.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information.
2main-1-5e147fb05f10a421c106-plex-3.39.5-cafe702.js:2610 Refused to get unsafe header "Location"
(anonymous) @ main-1-5e147fb05f10a421c106-plex-3.39.5-cafe702.js:2610

```

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 8, 2018, 12:14am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/17 "2018-04-08T00:14:55Z")

</div>

OK, it gets weird, let me tell you this. Now it is like described in my first post above. Same behaviour, same error.

But wtf has my PMS to do with twitter analytics?  
“Refused to execute script from '[https://analytics.twitter.com](https://analytics.twitter.com)”

See whole Chrome console log N°2. I’m starting to feel like a labour rat testing some undocumented features and I wonder, if I’m the only one who turns in circles or am I the one at all.

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 8, 2018, 12:24am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/18 "2018-04-08T00:24:48Z")

</div>

Restarted PMS and now it works back normal as I have the bundled web version 3.39.5 now with Server version 1.12.2.4929.

Even though I’m happy that it works as usual again and being thankful for the support (finally after a whole week!) I must wonder what you guys are experimenting in the background. I mean when will be the next time you screw up a working system just to let your users scream for help and waste their times?!

It’s not to you personally @sa2000 but your managing brainies and their understanding of customer satisfaction.

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 8, 2018, 12:38am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/19 "2018-04-08T00:38:40Z")

</div>

> @RazorPlex said:  
> OK, it gets weird, let me tell you this. Now it is like described in my first post above. Same behaviour, same error.
> 
> But wtf has my PMS to do with twitter analytics?  
> “Refused to execute script from '[https://analytics.twitter.com](https://analytics.twitter.com)”
> 
> See whole Chrome console log N°2. I’m starting to feel like a labour rat testing some undocumented features and I wonder, if I’m the only one who turns in circles or am I the one at all.

I am more concerned about this

```auto
The SSL certificate used to load resources from https://api.webtest.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information.

```

What security product do you have running?  
Just wondering if it is using its own certificate

Could you check what certificate shows up when you go to plex.tv

So in chrome open `https://app.plex.tv`  
and follow the steps here to view the certificate details  
[https://www.thesslstore.com/blog/how-to-view-ssl-certificate-details-in-chrome-56/](https://www.thesslstore.com/blog/how-to-view-ssl-certificate-details-in-chrome-56/)

Could you get screenshots of the security certificate info

that error in the log is explained here  
[https://dzone.com/articles/chrome-distrusts-ssl-certificates](https://dzone.com/articles/chrome-distrusts-ssl-certificates)  
But the plex certificate is not issued by Symantec and so I am wondering if you have some software that is interfering with the certificate

The certificate should appear as follows

 ![](https://sea1.discourse-cdn.com/plex/uploads/default/original/3X/d/f/df555cb35f2cac76292fc989b407407dbfd07184.png)

---

<div class="post-metadata">

**Author:** ![RazorPlex](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/razorplex/32/18386_2.png) [@RazorPlex](https://forums.plex.tv/u/RazorPlex)\
**Post date:** [April 8, 2018, 1:38am UTC](https://forums.plex.tv/t/there-was-an-error-signing-in/230138/20 "2018-04-08T01:38:22Z")

</div>

Please find attached the certificate (seems OK) and a new chrome console log N°3.  
I have no Symantec products at all on my PC.

 ![](https://sea1.discourse-cdn.com/plex/uploads/default/original/3X/3/e/3e6f5633d068b4898ef0187e4408d370c87ded40.png)

Do you have Symantec products on your PLEX Servers? I mean in your company at PLEX.

[Next page](https://forums.plex.tv/t/there-was-an-error-signing-in/230138.md?page=2)
