Reinstalling an OS can’t be a diagnostic option for one application, no matter how much I may like the application. We need to find something less involved.
That’s a good point. A better option would be to install Linux on an external drive with Plex and test on that.
The largest issue with computers since the 1990s has been Windows.
I used to reinstall Win 3.11 for Workgroups once a day on a handful of computer in our lab.
NT added a degree of stability, but only if you kept it on SP 3.
There’s never been a stable Windows since.
So given the following:
- Plex works with Win10 as does its Remote Access just by installing Plex and setting a couple of configs like user:pass. It’s almost fully automatic with UPnP.
- Your doesn’t. Therefore the issue is unique to your hardware, ISP, or Operating System.
- You’re asking Plex to solve that.
So given those, the standard Plex answer could only be, get your hardware and Operating System back to a default configuration, because we all know that works fine.
Your response is how do I get my hardware and OS back to a default configuration.
That’s not really a fair question for this forum. Why? Because you’ve shown you can’t even curl a token from a website that gives out 100k tokens a day. You can’t even curl from the command line. It’s not a fair question for us.
I’m happy to be corrected, and I’d prefer to help you solve this.
But we need proof your hardware & ISP & OS work before worrying about Plex.
And that’s what Linux on an external drive will do.
I think it’s reasonable and non-invasive while you wait for Otto.
But so is asking this on stack exchange or a networking forum. What do they say about curl?
All right, let me see if I have this straight. Essentially, if I can revert Windows to a clean install, ensure my HW drivers are up to date, then install PMS, you will agree that I’ve done everything reasonable to isolate what I can?
The reason I’m asking Plex to help me solve this is that the machine works as expected for other network-capable applications, except for this one. You mention curl. Super. What should I install on this to perhaps narrow this down to a curl issue? Maybe that would help Plex find the problem – PMS is clearly relying upon curl to do work.
Curl is already low level, and it’s not working in your Windows. You can’t get much lower level. Given that, the issue remains below a simple curl, somewhere in Windows, your ISP, or hardware. The Plex Media Server app is not involved when using claimit.sh. You just getting a web page from plex.tv using curl.
I’m going to assume plex.tv is still working, as everyone else is getting tokens.
So the point is not to reinstall windows, but to put that aside temporarily and test better on Linux.
I would agree that’s the most crazy thing about this. It’s why your issue is such a pain for you but an interesting puzzle for me. I keep thinking, “How is it even possible that curl doesn’t work?” It’s maddening. When I lie in bed I think it’s a conspiracy where your ISP is blocking you because their parent company competes with Plex.
That’s probably why Otto didn’t bounce back in. Curl simply works 100k times a day. It’s not really going to be remotely possible it’s curl itself, but I won’t rule it out, and your question is valid. My solution is to boot a fresh Linux install off an external drive, using Debian, because they are the rock of Linux, and they have a known working curl.
Not only do they have a good curl, it’s a good everything. It will isolate any failures to some piece of hardware, or your ISP. But the important thing is it’s installed on the same computer that’s not working now.
Sorry for the wall of hassle. I haven’t used Windows in 10 years exactly because of these tiny issues that drove me crazy. I want to use the thing as a tool, not have it become my profession.
Again sorry. I know what it’s like.
I ran curl without params, and it failed. I added --ssl-no-revoke and it worked. So this is a cert issue. I checked certs and Eset inserts itself into the cert chain. Once I removed that Eset attribute, everything started working as normal… so, it was an Eset issue, not a Plex issue.
This issue is resolved, and I thank you for helping me work through it. Thanks to Otto for chiming in as well. Now I need to figure out how to modify Eset to help me protect SSL traffic without affecting Plex… at least I know what to fix now.
Thanks again all.
2 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
