It should be fixed now. Sorry about that!
But yes in the near future we will be re-implementing the Cross-Origin-Opener-Policy. I’ll suggest we put a forum post out now that we understand the implications.
It should be fixed now. Sorry about that!
But yes in the near future we will be re-implementing the Cross-Origin-Opener-Policy. I’ll suggest we put a forum post out now that we understand the implications.
I can confirm that my issues are resolved. Appreciate the quick turnaround.
This was entirely related to Plex’s hosted authentication.
Right. I was having the same issue with a docker installation, but the authentication is done against Plex.tv, not the installed instance. ![]()
I’ve started getting CORS errors again, but it is non deterministic. Sometimes it happens and sometimes it doesn’t. I’ve also noticed sometimes my login is slow and sometimes it isn’t, though I’m not sure if it is related to CORS.
I know you said you were planning on re-implementing the CORS policy in the “near future.” Does that mean it has been turned back on?
Not back on just yet, and no recent changes. If it happens only sometimes that is rather odd ![]()
I tried on a different client and that seems to be working much better, so I suspect it was an issue with the original client. If it happens on other clients I can report back. Thanks!