Lubelogger not connecting to remote postgresql server

[nzbtuxnews]

Checklist
Please make sure you have performed the following steps before opening a new bug ticket, change [ ] to [x] to mark it as done

• I have read and tried the steps outlined in the Troubleshooting Guide
• I have searched through existing issues.

Description
Container deployed via Portainer (docker compose), it works well but does not seem to even try to connect to my remote PGSQL server.

Container logs only show:

LubeLogger 1.4.3
Website: https://lubelogger.com
Documentation: https://docs.lubelogger.com
GitHub: https://github.com/hargata/lubelog
SMTP Not Configured
Message Of The Day: Not Configured
WARNING: No Locale or Culture Configured for LubeLogger, Check Environment Variables
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://[::]:8080
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /App

On the DB server side, I monitor connections and see nothing coming from the Lubelogger container. Firewalling and/or networking issues have been ruled out. I can connect to the remote PGSQL server from my computer using

psql -h dbserver_IP -p 5432 -U lubelogger lubelogger

Docker compose:

---
version: "3.4"

services:
  app:
    image: ghcr.io/hargata/lubelogger:latest
    build: .
    restart: unless-stopped
    volumes:
      - /home/lubelogger:/App/data
      - keys:/root/.aspnet/DataProtection-Keys
    ports:
      - 8009:8080    
volumes:
  data:
  keys:

Environment variables:

LC_ALL=en_US
LANG=en_US
LUBELOGGER_MOTD=Welcome to LubeLogger!
POSTGRES_CONNECTION=Host=dbserver_IP:5432;Username=lubelogger;Password=*****************;Database=lubelogger;

Platform

• [ x ] Docker Image

[hargata]

This is because environment variables aren’t being injected correctly, you need to run docker compose up everytime you make changes to environment variables.

If the environment variables are injected correctly you will see “Welcome to LubeLogger” when the container starts.

[hargata]

Closing this since this is a user error.

[nzbtuxnews]

Found the issue, for those facing the same type of issue.... Seems that Portainer is NOT parsing the env variables during the deployment.

portainer/portainer#10491