Unable to get service started

[sinfulcontortion]

using command line install

Command line used: C:\locast2plex-master\main.py -u:email@domain.com -p:passwd --debug --addy:10.0.0.250

(using python 2.7.17)

[sinfulcontortion]

Got it started and connected... but unable to play anything.. status of DVR says not found even though I was abe to see it during setup and even setup a few recording... (which aren't working because DVR not found error I assume

CLI command used: C:\python C:\LOCAST\locast2plex-master\main.py -u:email@domain -p:password --debug:false --addy:10.0.0.240

**I did have to add ":6077" to the ip address in the plex dvr search window...

[sinfulcontortion]

Error Message in Plex Program Guide is.... "Live playback could not be started" (Full guide is showing)

[sinfulcontortion]

Pervious error was while trying ot view pley live TV/DVR on Roku This error is via Web client... "Could not tune channel. Please check your tuner or antenna." and now longer showing cannot find Tuner... No errors any more

I have 2 instances on separate servers setup... Locast2Plex — 10.0.0.240:6077 2 tuners 22 channels — 17 Enabled

— 10.0.0.241:6077 2 tuners 1 in use No channels— 17 Enabled

[tgorgdotcom]

Hello. Would you be able to send across the output that locast2plex is displaying?

[sinfulcontortion]

LOCAST ERROR.txt

[sinfulcontortion]

Server 2...

LOCAST ERROR svr2.txt

[tgorgdotcom]

Hello. To be sure, these are on separate physical servers?

[sinfulcontortion]

That is correct Separate physical servers...

~ Brian

On 8/24/20, Thomas Gorgolione notifications@github.com wrote:

Hello. To be sure, these are on separate physical servers?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/tgorgdotcom/locast2plex/issues/31#issuecomment-679458806

-- Cyber Security and Operations Support Engineer

Brian Jones P.O. Box 555, Bedford, MA 01730 Phone 781-910-6151 - Fax - 781-658-2468

Affinityhb@gmail.com www.linkedin.com/in/jonesdb6940

[tgorgdotcom]

I think I know what could be causing it. Both services are reporting the same generated UUID number. If you go into one of the servers and delete the service_uuid file and restart the locast2plex service, that should fix it.

[sinfulcontortion]

Hi, and Thank you for your feedback, I tried this but it did not work. I actually do have HDHR device running (been down for days cuz of cut antenna wire) I just put it on line and Plex found it immediately, ...for my other two locast services should I add unique port #'s to the end of my startup statement..? That's not working either...

~ Brian

[tgorgdotcom]

Hmmm. Not sure what is happening. The only thing I could see in the logs are these lines:

error: [Errno 10054] An existing connection was forcibly closed by the remote host error: [Errno 10053] An established connection was aborted by the software in your host machine

Maybe there's a firewall that is blocking port 6077?

[sinfulcontortion]

Hi, Thank you for getting back to me.

I am looking to start over on this, and I am hoping you can help me with my syntax a bit.

-I do have an functioning HDHR on same subnet as 3 of my Plex servers. -All 3 PLEX servers are using the HDHR as the Live TV/DVR device in the plex config. and is working fine.(except for frequent antennae degradation in bad weather) I am guessing I will need to use alternative ports in my startup commands. Can you help me with that and provide exact syntax..?

Respectfully, Brian

On 9/3/20, Thomas Gorgolione notifications@github.com wrote:

Hmmm. Not sure what is happening. The only thing I could see in the logs are these lines:

error: [Errno 10054] An existing connection was forcibly closed by the remote host error: [Errno 10053] An established connection was aborted by the software in your host machine

Maybe there's a firewall that is blocking port 6077?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/tgorgdotcom/locast2plex/issues/31#issuecomment-686264904

-- Cyber Security and Operations Support Engineer

Brian Jones P.O. Box 555, Bedford, MA 01730 Phone 781-910-6151 - Fax - 781-658-2468

Affinityhb@gmail.com www.linkedin.com/in/jonesdb6940

[tgorgdotcom]

Definitely! Another quick question, is locast2plex and Plex running on the same server? So ultimately

3 Plex servers (separate machines)

• 2 with locast2plex installed

Is that correct?

[sinfulcontortion]

Yes.. that is correct..

On Sat, Sep 5, 2020, 1:54 AM Thomas Gorgolione notifications@github.com wrote:

Definitely! Another quick question, is locast2plex and Plex running on the same server? So ultimately

3 Plex servers (separate machines)

• 2 with locast2plex installed

Is that correct?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tgorgdotcom/locast2plex/issues/31#issuecomment-687556864, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE45WDHHS5C7RP466WCRS63SEHHC3ANCNFSM4QD2PYKA .

[tgorgdotcom]

Okay, so one thing we should check is whether ffmpeg is installed. For 0.4.2, you'll need to manually install ffmpeg onto the Windows servers that are hosting locast2plex (0.5.x fixes this, but there are a lot of config changes you would have to do to upgrade). After installing ffmpeg, add it's folder location to the environment PATH variable.

Then, start up locast2plex as before, using the server IP (10.0.0.240/10.0.0.241) and no custom ports. In Plex's Live TV/DVR, remove any old locast2plex configurations, then re-add them (make sure you use 10.0.0.240:6077 or 10.0.0.241:6077 as the manual address).