Locast Login Credentials Missing. Exiting...

[codywarmbo]

I've just run the docker-compose example, and created a config.ini file in the /app/config/ directory. Locast seems to load the file but does not recognize my credentials. They are there!

The logged error:

Initiating Locast2Plex v0.6.5
Opening and Verifying Configuration File.
/app/config/config.ini
/app/config.ini
Loading Configuration File: /app/config.ini
Locast Login Credentials Missing. Exiting...

My config.ini:

[main]
plex_accessible_ip = 192.168.1.35
locast_username=username@example.com
locast_password=password

[TBoneStaek]

I'm having the same exact issue. Going nuts looking over paths.

[rubylaser]

I have donated to Locast, and I'm in the same boat as well. My error...

2021-03-11T22:07:23.978026372Z Opening and Verifying Configuration File.
2021-03-11T22:07:23.978048632Z /app/config/config.ini
2021-03-11T22:07:23.978051237Z Loading Configuration File: /app/config/config.ini
2021-03-11T22:07:23.978053555Z Locast Login Credentials Missing. Exiting...

Here's my docker-compose.yml

locast2plex:
    hostname: locast2plex
    container_name: locast2plex
    ports:
      - "6077:6077"
    volumes:
      - /docker/containers/locast2plex/config.ini:/app/config/config.ini
    restart: unless-stopped
    image: tgorg/locast2plex

and my config.ini file located at /docker/containers/locast2plex/config.ini on the host.

plex_accessible_ip = 192.168.172.10
locast_username=username@gmail.com
locast_password=exampledTzpCK37BP93od6Wi

If I don't use docker-compose, it works fine...

root@frontend:~# docker run -v /docker/containers/locast2plex/config.ini:/app/config/config.ini -p 6077:6077 tgorg/locast2plex
Initiating Locast2Plex v0.6.5
Opening and Verifying Configuration File.
/app/config/config.ini
Loading Configuration File: /app/config/config.ini
Tuner count set to 3
Server is set to run on  192.168.172.10:6077
No UUID found.  Generating one now...
UUID set to: siyolzis...
Getting user location...
Getting location via provided lat\lon coordinates.
Got location as Detroit - DMA 505 - Lat\Lon xxx\-xxx
Logging into Locast using username username@gmail.com...
Validating User Info...
User Info obtained.
User didDonate: True
User donationExpire: 2021-05-11 21:40:19
Starting First time Stations refresh...
Checking FCC facilities database for updates.
Online facilities database is newer. Downloading the latest FCC facilities database...
Unzipping FCC facilities database...
Reading and formatting FCC database...
Found 6378 stations.
Getting list of stations based on DMA...
Found 56 stations for DMA 505
Starting Stations thread...
Starting device server on 192.168.172.10:6077
Now listening for requests.
Starting SSDP server...
Starting First time EPG refresh...
Fetching:   https://api.locastnet.org/api/watch/epg/505?startTime=2021-03-11T00:00:00
Fetching:   https://api.locastnet.org/api/watch/epg/505?startTime=2021-03-12T00:00:00
Fetching:   https://api.locastnet.org/api/watch/epg/505?startTime=2021-03-13T00:00:00
Fetching:   https://api.locastnet.org/api/watch/epg/505?startTime=2021-03-14T00:00:00
Fetching:   https://api.locastnet.org/api/watch/epg/505?startTime=2021-03-15T00:00:00
Fetching:   https://api.locastnet.org/api/watch/epg/505?startTime=2021-03-16T00:00:00

[eiddor]

@rubylaser Try it with just the paths, vs. the explicit file:

    volumes:
      - /docker/containers/locast2plex:/app/config

[TBoneStaek]

@rubylaser Try it with just the paths, vs. the explicit file:

    volumes:
      - /docker/containers/locast2plex:/app/config

sonofa...

Ya’ know, I almost tried that... thanks! Worked perfectly after!

[rubylaser]

@rubylaser Try it with just the paths, vs. the explicit file:

    volumes:
      - /docker/containers/locast2plex:/app/config

Thanks! That did it. I could have sworn that I tried that first as all my other Docker containers mount volumes in a similar fashion, but I guess that I didn't.

[eiddor]

@rubylaser @TBoneStaek Great news!

This is one of those goofy issues that has been around for years - If you want a laugh, read this thread.

I've never been able to figure out why it works with docker-compose sometimes and with just Docker other times, but I haven't really put too much effort into it. Maybe permissions or UID?

I just use a directory and move on.