Closed RandomNinjaAtk closed 3 years ago
It seems like the FCC site is having issues. It might be good to ignore errors if we have an older facilities file already.
Same issue here - looks like there was a locast2plex issue for this about 3 weeks ago, then it started working again, but now it has once again started happening - for me it started about 3 hours ago with locast2tuner.
Recommend two things:
@scotte good points. I'll probably implement this tomorrow. The FCC URL where I download from has given me headaches because of SSL and I'm considering mirroring the FCC database on a different site as well.
I quickly mirrored the facilities on GCS, which is at least something. I'll create a proper mirror tomorrow and will implement the recommended items, but 0.1.32 should at least start again.
im Having the Same issue and I Narrowed it down to a few things the older version you were able to manipulate the zip code so let's say you lived in an area that didn't have Locast you could pop in a zip that would think it's from that area... but now the DMA Trigger on locast stating you aren't where your suppose to be.... this is really bad when you think about it because I think Locast computer system just triggered now how do I know this is True well real simple just Fire up a VPN and base it out of a location where locast is based out of like Detroit or Chicago and your able to watch whatever you want... also no workaround on unraid also Tryed to route my docker container through a VPN container Still nothing.... just a head up I just now updated to the latest locast in unraid before this I wasn't haven't any issues so if possible look at the older versions... i should have never touched this thing, to be honest, but the version said unavailable and my OCD couldn't take it anymore
@wouterdebie Thanks! @lawrence1986101 I just pushed an update for the Unraid container, check for updates in the next 20 or so minutes and it should have the latest fixes. (https://github.com/RandomNinjaAtk/docker-locast2tuner/commit/fe722f43459208071d7a708a639fe86900c98dd7)
I can confirm, after building my new image with the updated software, everything is working again!
Thanks!
Works nowSent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: RandomNinjaAtk @.> Date: 5/5/21 6:32 AM (GMT-05:00) To: wouterdebie/locast2tuner @.> Cc: lawrence1986101 @.>, Mention @.> Subject: Re: [wouterdebie/locast2tuner] Stuck "Downloading FCC Facilities" ... (v 0.1.31) (#45) @wouterdebie Thanks! @lawrence1986101 I just pushed an update for the Unraid container, check for updates in the next 20 or so minutes and it should have the latest fixes. @.***
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
@wouterdebie Thanks! @lawrence1986101 I just pushed an update for the Unraid container, check for updates in the next 20 or so minutes and it should have the latest fixes. (RandomNinjaAtk/docker-locast2tuner@fe722f4)
Is there any reason for you not to use the docker image we're already building?
I simplify the setup and configuration for Unraid usage.
@RandomNinjaAtk do you need to rebuild manually every time I upgrade? If so, I wouldn't mind adding your config for a specialized Docker build.
Ninja I was using a older version of the locast docker. I upgraded last time to yours and it didn't work..... it had that fcc bullshitSo who ever touched that and fixed that fcc thank youSent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: Wouter de Bie @.> Date: 5/5/21 9:53 AM (GMT-05:00) To: wouterdebie/locast2tuner @.> Cc: lawrence1986101 @.>, Mention @.> Subject: Re: [wouterdebie/locast2tuner] Stuck "Downloading FCC Facilities" ... (v 0.1.31) (#45)
@wouterdebie Thanks! @lawrence1986101 I just pushed an update for the Unraid container, check for updates in the next 20 or so minutes and it should have the latest fixes. @.***)
Is there any reason for you not to use the docker image we're already building?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
All good here as well. Thanks for the fix @wouterdebie
Won't start, see log data below: