Any updates? See ya Tuesday.
I did not get any further feedback from development beyond the initial feedback
I will raise it as an issue
Could you establish if the issue arises when the HD Homerun Dual is on the same network subnet as the Plex Media Server
Logs showed Plex Media Server on 172.17.0.3
172.17.0.3 is the docker container’s IP
The host and the HD Homerun are on the same subnet.
The HD Homerun does not allow for static IP address configuration.
When I ran PMS on iron (same host) it worked fine.
I’ don’t think I’d be able to configure the HD Homerun to be in the Docker subnet though.
Thanks - i found some old forum topic on this here
Dockerised plex can’t see hdhomerun unless using network_mode: host
I am raising it as an issue with the development team - the impact of this problem is very limited as it only applies to the old HD Homerun DVR - the Dual and only for users on docker
Try passing port 32600.
you mean by -p 32600:32600/tcp
?
I’m going to ask “why?” I’m working on getting that test done, but i don’t understand.
That is the port that the tuner service uses.
/usr/lib/plexmediaserver/Plex Tuner Service /usr/lib/plexmediaserver/Resources/Tuner/Private /usr/lib/plexmediaserver/Resources/Tuner/Shared 1.21.2.3943-a91458577 32600
32600 is not mentioned in pms-docker, Firewall,
Might be time to update some documentation…
Also adding -p 32600:32600/tcp
to my container config did nothing noticeable.
Probably why when using older tuners only Host mode is supported. The tuner service opens random ports to talk to the tuners.
Seems like that should be configurable, allow the admin to select random ports or specify a port/portrange. Plex is popular even beyond the simple home use.
32600 is used through loopback (127.0.0.1) so firewall should not come into it
He is running docker in bridge mode so the localhost of the docker isn’t the same as the host, you only get that with HOST mode.
According to this thread the port used is random.
I presume that is between Plex Tuner Service and HD Homerun
The 32600 loopback port is used between Plex Media Server process and Plex Tuner Service process
Thanks for the clarification
Requests from Plex Media Server to Plex Tuner Service on port 127.0.0.1:32600 did get through according to the logs
Yeah. You are correct. according to netstat 32600 is bound to lookback. Sorry for the confusion.
For the connection for streaming from the HD Homerun to PMS, According to the previously linked post:
Plex listens on a random port and tells the HD Homerun to stream to that port. For this operation it would be great if the server owner was able to specify a port range for this interaction, from the tuner device configuration within PMS → Manage > “Live TV & DVR”. I’d even be happy with a config file.
But is this different from how the HD HomeRun Connect being used by Plex Media Server in the docker ?
Apparently so.
I’m not an HD homerun expert but I do know the interface changed significantly from the Dual to the Connect.
The random port is set on the application side, not the HDHomeRun side. Basically, Plex starts listening on a port, and then tells the HDHomeRun to stream to that port. Anything to specify a particular port/range would have to be within Plex, not on the HDHomeRun. This only applies to legacy HDHomeRun devices as well. Newer devices stream using HTTP, so the client (Plex) connects to the HDHomeRun and pulls from it, rather than the HDHomeRun pushing data to the client. That should not require any special port configuration since the connection comes from the client. Legacy devices just don’t have the hardware capabilities to do that.
Thanks - i have added that to the raised issue with the development team