# Incorrect timestamp in bitwarden.log
**URL:** https://vaultwarden.discourse.group/t/incorrect-timestamp-in-bitwarden-log/177
**Category:** Help
**Created:** [July 6, 2020, 3:09pm UTC](https://vaultwarden.discourse.group/t/incorrect-timestamp-in-bitwarden-log/177 "2020-07-06T15:09:58Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@IOUSiVer](https://vaultwarden.discourse.group/u/IOUSiVer)
#### Post date: [July 6, 2020, 3:09pm UTC](https://vaultwarden.discourse.group/t/incorrect-timestamp-in-bitwarden-log/177/1 "2020-07-06T15:09:58Z")
I"m setting up fail2ban and noticed the timestamp in the bitwarden.log is incorrect. It’s not matching the host or container timestamp. Is there a way to sync the log timestamp with that of the container it runs in so the logs reflect the date and time correctly?
Is TZ an acceptable param for docker compose? I can’t find documentation even on the wiki for all the compose environment params.
- TZ=America/Los\_Angeles
Thank you!
---
### Author:  [@jjlin](https://vaultwarden.discourse.group/u/jjlin)
#### Post date: [July 7, 2020, 6:11am UTC](https://vaultwarden.discourse.group/t/incorrect-timestamp-in-bitwarden-log/177/2 "2020-07-07T06:11:32Z")
IIRC, setting `TZ` will work in the Debian-based image (`latest` tag), but not in the Alpine image. Bind-mounting the Docker host’s `/etc/localtime` into the container should work in both images:
```auto
volumes:
- /etc/localtime:/etc/localtime:ro
```
---
### Author:  [@IOUSiVer](https://vaultwarden.discourse.group/u/IOUSiVer)
#### Post date: [July 9, 2020, 1:22am UTC](https://vaultwarden.discourse.group/t/incorrect-timestamp-in-bitwarden-log/177/3 "2020-07-09T01:22:30Z")
Thank you. That fix worked great! Fantastic! SOLVED