ukdtom / ClaimIt

ClaimIt 4 Plex Media Server
Mozilla Public License 2.0
74 stars 19 forks source link

Error was: The underlying connection was closed #26

Closed ScrumpyCyder closed 3 years ago

ScrumpyCyder commented 3 years ago

Capture

Running the windows version of ClaimIt. The full error message is:

The underlying connection was closed: An unexpected error occurred on a send

Running PMS via a docker container using Portainer on OMV 5 on a Raspberry Pi.

ukdtom commented 3 years ago

Hmmm.....Plex.tv doesn't wanna talk with you, so either a bad username/pwd, or older version of Windows that doesn't support TLS1.1

ukdtom commented 3 years ago

Closed due to lack of respose

proimage commented 3 years ago

I'm getting the exact same error: image

Running Windows 10, with PMS running in a docker container on an unRAID box on my local network. The Windows machine IP is 10.0.0.19, and the unRAID box is at 10.0.0.10.

Should I open a new issue?

ukdtom commented 3 years ago

See here: https://github.com/ukdtom/ClaimIt/issues/27#issuecomment-778857644

proimage commented 3 years ago

The new executable got "stuck" for a while and then spit out this: image

ukdtom commented 3 years ago

As it says, see the wiki.

You either have a server that's already claimed, or a bad prefs file https://github.com/ukdtom/ClaimIt/wiki/Errors-and-Troubleshooting

proimage commented 3 years ago

Doesn't look like that's the issue. I've reinstalled the entire container from scratch and let it generate the preferences.xml just in case. Ping works fine (although the initial response took about 10 seconds after pressing Enter, the time= values were all in the normal ~195ms range).

Any other ideas? FWIW, the PMS docker container allows specifying the PLEX_CLAIM variable:

image

Could it be that the specified variable is conflicting with whichever one your app is trying to fetch? I know they supposedly only last for 4 minutes....

ukdtom commented 3 years ago

No idea, since not a docker dude.... But your DNS response was indeed too slow.... Try and switch to Google DNS as mentioned in the wiki

proimage commented 3 years ago

I've switched to Google's DNS, but still get the same error. :-/

ukdtom commented 3 years ago

Then please create a new issue, and on the forums, since not releated to the OP of this closed issue