Incorrect timezone in email message "New Device Logged In From" #667

Closed
opened 2026-02-04 22:09:19 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @andpp on GitHub (Mar 31, 2020).

Subject of the issue

I changed timezone in Dockerfile to my local TZ and created bitwarden_rs container with correct timezone. All logs have correct timestamp. Running 'date' command inside container shows correct date. However in information emails I still receive time in UTC zone. All timezone settings inside the container are correct.

Your environment

  • Bitwarden_rs version: 1.14.1-5471088e
  • Install method: docker

Dockerfile I use:

FROM bitwardenrs/server:latest
RUN rm /etc/localtime; ln -s /usr/share/zoneinfo/America/Los_Angeles /etc/localtime; echo -n America/Los_Angeles >/etc/timezone
WORKDIR /
CMD ["/bitwarden_rs"]

Steps to reproduce

  • Change timezone in docker container. Enable Email nootification
  • Make sure 'date' in container shows correct result
  • Login from a new device
  • Check date in received email

Your account was just logged into from a new device.

Date: Tuesday, March 31, 2020 at 18:54 <- UTC timezone
IP Address:
Device Type: Chrome

Expected behaviour

Date should be according to docker's container timezone

Actual behaviour

Date in UTC

Originally created by @andpp on GitHub (Mar 31, 2020). <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unneccessary for your issue, feel free to remove them. Remember to hide/obfuscate personal and confidential information, such as names, global IP/DNS adresses and especially passwords, if neccessary. --> ### Subject of the issue I changed timezone in Dockerfile to my local TZ and created bitwarden_rs container with correct timezone. All logs have correct timestamp. Running 'date' command inside container shows correct date. However in information emails I still receive time in UTC zone. All timezone settings inside the container are correct. ### Your environment <!-- The version number, obtained from the logs or the admin page --> * Bitwarden_rs version: 1.14.1-5471088e * Install method: docker Dockerfile I use: ``` FROM bitwardenrs/server:latest RUN rm /etc/localtime; ln -s /usr/share/zoneinfo/America/Los_Angeles /etc/localtime; echo -n America/Los_Angeles >/etc/timezone WORKDIR / CMD ["/bitwarden_rs"] ``` ### Steps to reproduce - Change timezone in docker container. Enable Email nootification - Make sure 'date' in container shows correct result - Login from a new device - Check date in received email Your account was just logged into from a new device. Date: **Tuesday, March 31, 2020 at 18:54** <- UTC timezone IP Address: <IP of device> Device Type: Chrome ### Expected behaviour Date should be according to docker's container timezone ### Actual behaviour Date in UTC
Author
Owner

@andpp commented on GitHub (Apr 17, 2020):

Fixed after upgrade to the latest release. Closing.

@andpp commented on GitHub (Apr 17, 2020): Fixed after upgrade to the latest release. Closing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#667