Skip to content
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

Two or more instances of Locast2Plex on Docker? #269

Open
cahiatt opened this issue Jul 25, 2021 · 3 comments
Open

Two or more instances of Locast2Plex on Docker? #269

cahiatt opened this issue Jul 25, 2021 · 3 comments

Comments

@cahiatt
Copy link

cahiatt commented Jul 25, 2021

Anyone yet able to get two or more instances of Locast2Plex working on Windows Docker?

I have my Plex server and Docker running on the same bare metal Windows machine. I can get a second Locast2Plex instance to start and give it a different port but Plex won't connect to it.

@rocky4546
Copy link

First, can you explain why you need multiple instances, it would help to understand the overall problem.

Next, Plex uses SSDP to auto detect the HDHomerun device. To setup multiple instances, you want to make sure SSDP is disabled and use manual setup on Plex. Use the following address to setup the manual case.
http://ipaddress:port (note without the last slash)
Then you could use the xmltv.xml interface with the same info as
http://ipaddress:port/xmltv.xml

It is very possible that Plex will only allow a single app from an IP address. I have seen this before, but I do not remember which media server it occurred. If that is the case, you would need two different IP addresses for the two ports in your docker containers. If everything (Plex and the two L2P apps) are running in docker containers, you should be able to setup each app with different IPs.

Media Servers do a lot of assuming when it comes to the HDHomerun interface. One is that each appliance is on a separate IP address.

One final note. When plex gets confused on the setup, I normally have to remove all configuration data and try again. On linux, the location is
/var/lib/plexmediaserver/Library/Application Support/Plex Media Server.
It contains folders like Cache, Codecs, Logs, Plug-ins, etc.
I will shutdown the plex server, remove the files/folders in this directory and start Plex back up. This will give you a clean install to try again.

@CTJohnK
Copy link

CTJohnK commented Jul 26, 2021

I have several running on one machine, but not in Docker containers. I adjusted the config.ini as well as 'user_config.py' to hard code the 'reporting_friendly_name'. Sometimes when resetting Plex, those additional tuners will appear automatically, other times, not. When they don't appear I'm able to manually enter the IP and Port (I use 6077, 6078 and 6079) and I'm able to add the L2P tuner.

@cahiatt
Copy link
Author

cahiatt commented Aug 20, 2021

I have several running on one machine, but not in Docker containers...

Are they running on bare metal or inside virtual machines? I started testing the Python route today. Setup a stand alone Win10 VM with nothing but Pytyon to run the service. I keep getting the following error tyring to start it.

Error in function get_ip_location: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)
Could not acertain location. Exiting...

I installed Edge and followed the suggestion here to update the SSL but same error.
#182

I've manually entered zip code and coordinates into config.ini to bypass but the error continues.
#152

Did a pip install --upgrade certifi as outlined below and still no go.
https://stackoverflow.com/questions/35569042/ssl-certificate-verify-failed-with-python3

Anyone have the python script running in a Win10 virtual machine?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants