Unable to load with postgres database

[junction1153]

🐛 Bug Report

🔬 How To Reproduce

Steps to reproduce the behavior:

1. ...

Code sample

docker run -d -p "5100:5100" pglombardo/pwpush:latest -e DATABASE_URL="postgres://pwuser:PASSWORD@postgres:5432/pwpush_db"

root@monitor:~/PasswordPusher# docker logs magical_mccarthy

DATABASE_URL not specified. Assuming ephemeral backend. Database may be lost on container restart.
To set a database backend refer to https://docs.pwpush.com/docs/how-to-universal/#how-does-it-work

Password Pusher: migrating database to latest...
Password Pusher Version: 1.48.1
Password Pusher: starting puma webserver...
[10] Puma starting in cluster mode...
[10] * Puma version: 6.4.3 (ruby 3.3.6-p108) ("The Eagle of Durango")
[10] * Min threads: 3
[10] * Max threads: 3
[10] * Environment: production
[10] * Master PID: 10
[10] * Workers: 2
[10] * Restarts: (✔) hot (✖) phased
[10] * Preloading application
Password Pusher Version: 1.48.1
[10] * Listening on http://0.0.0.0:5100
[10] Use Ctrl-C to stop
[10] - Worker 0 (PID: 16) booted in 0.0s, phase: 0
[10] - Worker 1 (PID: 20) booted in 0.0s, phase: 0

Environment

Where are you running/using Password Pusher?

• pwpush.com
• Docker Image
  • pwpush
  • Custom image
• Heroku
• Digital Ocean
  • App Platform
  • Kubernetes Service
• Microsoft Azure
  • App Service
  • Container Instances (ACI)
  • Kubernetes Service (AKS)
• Google Cloud
  • App Engine
  • Cloud Run
  • Kubernetes Engine
• AWS
  • Elastic Container Service (ECS)
  • Kubernetes Service (AKS)
• Source Code
• [X ] Other (please specify) - Debian 12 install with Docker

If applicable, what version of Password Pusher? Latest

Screenshots

📈 Expected behavior

To load with Postgres successfully. We tested the credentials and they do work

📎 Additional context

[github-actions]

Hello @junction1153, thanks for contributing to the Password Pusher community! We will respond as soon as possible.