Timezone Displaying Incorrectly

[asheersingh]

I'm having an issue with the time that is displayed in the NPM UI. I have set the TZ settings in the Docker Compose but it is still not reflecting on the UI. It seems to be defaulting to the current UTC time. My docker compose is attached below. Is anyone else having similar issues?

version: '3.8'
networks:
default:
ipam:
driver: default
config:
- subnet: 172.18.0.0/16
services:
npm:
container_name: jc21-nginx-proxy-manager
image: 'jc21/nginx-proxy-manager:latest'
healthcheck:
test: ["CMD", "/usr/bin/check-health"]
interval: 10s
timeout: 3s
restart: always
ports:
- '8080:80'
- '8443:443'
- '8081:81'
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "npm"
DB_MYSQL_NAME: "npm"
DISABLE_IPV6: 'true'
TZ: 'Pacific/Auckland'
volumes:
- /home/administrator/docker/npm/data:/data
- /home/administrator/docker/npm/letsencrypt:/etc/letsencrypt
depends_on:
- db
networks:
default:
ipv4_address: 172.18.0.2

db:
container_name: jc21-mariadb-aria
image: 'jc21/mariadb-aria:latest'
healthcheck:
test: ["CMD-SHELL", "mariadb-admin --user=root --password=root --host=localhost ping"]
start_period: 60s
start_interval: 15s
interval: 30s
timeout: 5s
retries: 3
restart: always
environment:
MYSQL_ROOT_PASSWORD: 'root'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
MARIADB_AUTO_UPGRADE: '1'
TZ: 'Pacific/Auckland'
volumes:
- /home/administrator/docker/npm/db:/var/lib/mysql
networks:
default:
ipv4_address: 172.18.0.3

geoipupdate:
container_name: maxmind-geoipupdate
image: 'ghcr.io/maxmind/geoipupdate:latest'
restart: always
environment:
GEOIPUPDATE_ACCOUNT_ID:
GEOIPUPDATE_LICENSE_KEY:
GEOIPUPDATE_EDITION_IDS: GeoLite2-ASN GeoLite2-City GeoLite2-Country
GEOIPUPDATE_FREQUENCY: 12
TZ: 'Pacific/Auckland'
volumes:
- /home/administrator/docker/npm/data/nginx/geoip2:/usr/share/GeoIP
depends_on:
- npm
networks:
default:
ipv4_address: 172.18.0.4

[jc21]

Yep I'm seeing this too. I guess I haven't noticed because the exact times are mainly useful for the audit log. The API is returning times as

"created_on": "2025-03-24 04:21:24"

and this probably should be a fully formed iso date with zone. This used to be a UNIX timestamp and I think that was modified in a PR but this wasn't considered.