Docker can sometimes be setup where the IP is more like NAT. For example, my dockers all sit on a 172.17.0.0/16 and the LAN side is basically NAT’ed through.
Is this what you have?
I am starting to think you are on to something since my OH Docker runs a custom br0 network
Similar yes, mine run on a synology. You may need to add that 172 network. My plex is on a NUC, my OH is in a docker.
Thank you for your help so far, where would I be adding it to?
This is what the docker setup looks like right now:
Additionally the plex binding came online when migrating back to an older version but then did stop working again in the same way.
I was meaning here on the plex. You may need to specify the 172 block as an additional LAN network.
I would give that a try to see if it fixes it.
No dice, but when I put openhab on a host network it did work (but a lot of my other bindings break)
Dockers can cause some weird things to happen. I’m not sure why converting from http to https breaks when you’re connecting on the same port number. Plex could be trying to validate you and is failing. I’d check logs on both plex and OH to see if you can find the error message.
Not seeing anything about it in the plex logs, for openhab would it write the error to openhab.log?
You would have to turn up the logging to DEBUG to see what’s happening.
Out of curiosity, what version of Plex are you running?
PLEX Version 1.32.5.7349
Cool. I’m also on that version here so I don’t think it’s a bug on the Plex side. I would go through the dockers and see if anything weird is happening there. Do you have any kind of application proxies or NGINX or anything on the network which may be getting in the middle?
EDIT: I’ll go update my snapshot to the newest to see if I have the same issue. I’m running a jar right now that was compiled in with the change.
No nothing else in the middle, it has to do something with the custom network because when I set it to custom it gets the error and when I set it to host it works fine
I updated to SNAPSHOT 3562 and it seems to be working clear on my side.
Well that’s not cool. Please open a bug on github with that info. Thats a weird regression.
@Joshua_Frankel do you run docker with a compose file?
Maybe you can either provide the docker-compose.yml or the commands u use to run docker. Then it’s would be possible to debug better.
Would be great to know if you linked the docker containers and if you exposed the correct ports.
I don’t think the docker container would be able to connect to the host that way. Normally a docker containers network is limited. Did it work in the past this way?
When I test with some simple docker/nc configuration:
This shows it is not able to connect. However if you use host.docker.internal instead of the hosts real ip it translates to the internal ip adres of the host used in docker and then the connection works.
So in this case I would suggest that you change the IP address of the Plex Server in OpenHAB to host.docker.internal. And of course add the Authentication Token as well.
Not sure what you mean, if I do that it acts like it doesn’t know that URL. These dockers are on the same server, just one is using host and the other is using custom.
Hey everyone, can I bother you guys for a quick test? I’m trying out the plex binding on v4.0.1 and I noticed that the end time channel stays null.
I tried with both a browser and an iOS app, and neither seem to populate it correctly. Anyone else seeing the same??
The logs don’t seem to receive anything about the end time at all.
Off topic: is there an official plex binding thread? Or GitHub to post issues?