-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Unknown connection error in Plex integration setup #28564
Comments
@SPCulhane Looks like a few of things going on here:
I'm not exactly sure why the config flow is failing for you as the exception is being gobbled up. I normally don't like to do it this way, but can you try to edit |
I made those changes and the results are the same. I tried it with my normal plex: config and then I remove config and tried using auto-discovery/integration.
|
At what point in the integration setup does it fail? Can you successfully authenticate at plex.tv? Does the redirect back to HA succeed? |
Well I have some good news. I changed my config to this:
Before the host was 192.168.0.10 So right now, it works just using the above config without authenticating via plex.tv watch counter does start off as unknown but it increases/decreases and players are showing up again |
It would fail when it would do the redirect back to HA. The first prompt "Connect Plex server :Continue to authorize at plex.tv." works and then this pops up "This step requires you to visit an external website to be completed.". I'm able to login then when it redirects back, i receive the 500 error (https://hassio.1234.net/auth/plex/callback?flow_id=123456) |
That's really good to hear. I'm still trying to understand what was going wrong with setting it up via the Integration page. |
It failed when it was redirecting back to HA using this url: https://hassio.1234.net/auth/plex/callback?flow_id=123456 that's were I would get a 500 error. My last set of logs everything at "2019-11-05 11:45:42 ERROR (MainThread) [aiohttp.server] Error handling request" and after is when its redirecting back to HA |
Just like @dshokouhi I'm also getting the plex sensor showing as unknown since upgrading to all versions of 0.101. My setup can be seen in #28630 which I've closed. My sensor however, never seems to update when streams have started. I also get timeouts/errors when trying to integrate using the frontend, just like @SPCulhane |
@SPCulhane will you be able to test this again when 0.102.1 is released? Bumping up the logging for Plex would also be very helpful:
|
I'm seeing the same results. I don't know if this factor, I do have Plex set to auto authenticate my local subnets With these options using local IP for host
With these options, still local IP
|
Looks like you're using
Perhaps this could be a factor. I'll have to run some more tests with this setup. |
i removed the config from the yaml file and deleted it. same results
|
Hmm. Your server has 10(!) ways to connect, most of which time out. The config flow is getting aborted before all of the connection attempts return. Perhaps the default |
lol. I can't help that. It's running on a QNAP NAS. the 10.x and 172.x are internal networks within the NAS for docker. I'm using the native QNAP Plex app |
I have a theory. Can you try to apply this change in your If that works I'll create a PR to put it in the release. |
same results :(
|
Bah, it didn't take the value, there's some confusing import logic on the defaults used in the library. Sorry. Please try this one instead: 00fe033 |
@SPCulhane did you see my last update? I'm hoping that will help your setup issues. |
I have not but I will try today |
@jjlawren I think you threoy is right. Cause it worked!! I'm going to try it again just to make sure =D
|
Was this ever fixed? I still can't connect to my plex server. I tried the discovered integration and seeing that it didn't work, I deleted it and tried through the config file. But that also does not work.
Using: plex: |
@chezpaul not sure why it's not ignoring the certificate validation, but it's because the hostname you're using doesn't match the certificate. Try to use |
Tried it. Still no luck but a more understandable error.
|
DNS probably isn't resolving then. Can you remove both the YAML config and integration and try to add via the integrations UI again? There's no known problems with setup now, so if you're still having issues can you please create a new issue with your details? |
I'm also using Plex running on a QNAP NAS. No native Apple Vision Pro successfully connects (one of them claims Plex IP is 10.0.5.1:3200). The iPad app works though. |
Home Assistant release with the issue:
0.101.2
Last working Home Assistant release (if known):
0.100.2
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io running as a VM on ESXi
Integration:
plex https://www.home-assistant.io/integrations/plex/
Description of problem:
Same as above
Removed, re-added. No new devices show up. Plex and Hass.io are on different subnets but never had an issue. Plex is running on a QNap NAS.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Originally posted by @SPCulhane in #28485 (comment)
Originally I have Plex setup with Required secured connection with the above Plex integration config. This was working until the recent update. Now its showing Unknown and doesn't show any plays.
If I change Plex to Preferred secured connection and change the Plex integration to ssl: false. It shows unknown until a show is played. It's reporting what is playing and adding devices.
Thinking my issue is different. I will do some more digging later but having Plex setup with Required secured connection isn't working right with the recently HA update. In the logs you'll notice some 10.x IPs, those are because the QNap NAS has docker running on it. When using autodiscovery, Plex is found and I login but end up with a 500 server error.
The text was updated successfully, but these errors were encountered: