Docker Startup failing at Starting EPG Thread - v0.6.5

[RaaZeR2169]

Just a few days ago everything was working fine. However, I needed to clean up my VM that I have this running on and used a snapshot from 4 days ago. And the docker launch now hangs at Starting EPG thread. This is a windows 10 VM that worked without issue prior to this. I have even run it with a brand new VM install and a fresh install of docker and the L2P script. Thoughts?

Creating locast2plex_locast2plex_1 ... done
Attaching to locast2plex_locast2plex_1
locast2plex_1 | Initiating Locast2Plex v0.6.5
locast2plex_1 | Opening and Verifying Configuration File.
locast2plex_1 | /app/config/config.ini
locast2plex_1 | Loading Configuration File: /app/config/config.ini
locast2plex_1 | Tuner count set to 3
locast2plex_1 | Server is set to run on 192.168.X.X:6077
locast2plex_1 | UUID set to: ...
locast2plex_1 | Getting user location...
locast2plex_1 | Getting location via IP Address.
locast2plex_1 | Got external IP X.X.X.X.
locast2plex_1 | Got location as XXXXX - DMA XXX - Lat\Lon XX.XX-XX.XX
locast2plex_1 | Logging into Locast using username [email protected]...
locast2plex_1 | Validating User Info...
locast2plex_1 | User Info obtained.
locast2plex_1 | User didDonate: True
locast2plex_1 | User donationExpire: 2021-05-09 22:53:05
locast2plex_1 | Starting First time Stations refresh...
locast2plex_1 | Checking FCC facilities database for updates.
locast2plex_1 | Online facilities database is newer. Downloading the latest FCC facilities database...
locast2plex_1 | Unzipping FCC facilities database...
locast2plex_1 | Reading and formatting FCC database...
locast2plex_1 | Found 6129 stations.
locast2plex_1 | Getting list of stations based on DMA...
locast2plex_1 | Found 50 stations for DMA XXX
locast2plex_1 | Starting Stations thread...
locast2plex_1 | Starting device server on 192.168.X.X2:6077
locast2plex_1 | Now listening for requests.
locast2plex_1 | Starting SSDP server...
locast2plex_1 | Starting First time EPG refresh...
locast2plex_1 | Fetching: https://api.locastnet.org/api/watch/epg/807?startTime=2021-04-11T00:00:00
locast2plex_1 | Fetching: https://api.locastnet.org/api/watch/epg/807?startTime=2021-04-12T00:00:00
locast2plex_1 | Fetching: https://api.locastnet.org/api/watch/epg/807?startTime=2021-04-13T00:00:00
locast2plex_1 | Fetching: https://api.locastnet.org/api/watch/epg/807?startTime=2021-04-14T00:00:00
locast2plex_1 | Fetching: https://api.locastnet.org/api/watch/epg/807?startTime=2021-04-15T00:00:00
locast2plex_1 | Fetching: https://api.locastnet.org/api/watch/epg/807?startTime=2021-04-16T00:00:00
locast2plex_1 | Starting EPG thread...

[RandomName-Here]

I am also getting the same in my log, I've never seen it go past Starting EPG thread so I'm assuming there is supposed to be more. I just started trying it yesterday, so have never had it working to compare. I've tried in Unraid and docker for windows same result. Only thing different that I can see that I am doing is using a zipcode override for location as its not available yet in my location.

[RandomName-Here]

@RaaZeR2169 its possible you will have to add it again to your Plex, manually put in the IP. I did that anyway from my Docker from Windows setup and its working. Even though my log has not moved off of starting epg thread it is working in Plex.

[ecowitness]

Are you getting snagged on the IP address? Do you have the empty file "is_container" (used as a switch) in your image? When this "switch" is set, L2P will bind to address ip address 0.0.0.0 in the container. The ip and port that you specify will still be used internally for everything except the bind.

Maybe you can override the --ENTRYPOINT on your docker RUN to specify a shell. This would allow you to look around within the container while it is running. You could start L2P from the shell and cntl-c to get back to the shell.

You could also go to a browser and try to access L2P by typing in --> your_ip_address:your_port/anything <-- you should get back a 501 msg. If not, then nothing else can talk to L2P either.

Otherwise, we are going to have to see a lot more of your setup.

((I run my L2P in docker under Ubuntu server 20.04. I have no experience with Win 10 VM, etc.))