mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #4447] Timezone Displaying Incorrectly #2845
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2845
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @asheersingh on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4447
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 commented on GitHub (Mar 24, 2025):
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
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.
@github-actions[bot] commented on GitHub (Sep 23, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍