Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save Configuration Error #32

Closed
LysanderM opened this issue May 23, 2017 · 3 comments
Closed

Save Configuration Error #32

LysanderM opened this issue May 23, 2017 · 3 comments
Labels
bug this item causes errors that make the project unusable super-duplicate contains more information than it's duplicated counterpart(s)

Comments

@LysanderM
Copy link

LysanderM commented May 23, 2017

Hi there. The similar issue was written here already, but it was without the screenshot.

I'm using Chrome 58.0.3029.110 (64-bit) in Windows 10.

When I try to connect (Test within your options page) to the server on my Synology NAS, with my "proper" X-Plex Token, like in the 1st picture,
image

I get the following error in console as this.

image

It seems the token, I did enter, was valid. (Which was and is indeed. I'm sure of it :) )
By the way, both connection to my Plex server either via my remote DDNS address;

1

or via app.plex.tv/web/app page

1

are also reachable.

Well, I've also watched the result set Data.Device for you. There is no filter function, it says undefined.
Yet there are 2 devices, one is my private PC, and the other one (Remote DDNSed one) is my office PC.
The problem started right after I've configured my private pc.
Everything was working before though.

image

Any help is appreciated.
Sorry for the mess.

Thanks,

Emir.

@LysanderM
Copy link
Author

When I remove all the connected devices from Plex GUI, and re-login only via app.plex site (I mean setting X-Plex-Token to WebToPlex setting), the problem is gone.

If I login via DDNS address and try to set that X-Plex-Token to WebToPlex setting again, the problem might occurs again, possibly.

@SpaceK33z
Copy link
Owner

Hi, thanks for your very clear bug report. I realize I'm very late to commenting and you've perhaps already given up (?). I've been very busy with other things.

My first question is: do you still have this bug? This kinda looks like a bug in Plex Media Server, and perhaps it has been resolved in the mean time. I have some ideas if you still have this bug.
Second question: are you running the latest PMS version?

@SpaceK33z SpaceK33z added the bug this item causes errors that make the project unusable label Sep 17, 2017
@SpaceK33z
Copy link
Owner

I'm closing this issue because of inactivity. Feel free to comment, and we can always re-open it again.

@Ephellon Ephellon added the super-duplicate contains more information than it's duplicated counterpart(s) label Dec 15, 2018
This was referenced Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug this item causes errors that make the project unusable super-duplicate contains more information than it's duplicated counterpart(s)
Projects
None yet
Development

No branches or pull requests

3 participants