Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timezone cannot be changed at the OS-level breaking TOTP #3824

Open
OdinVex opened this issue Jan 24, 2025 · 0 comments
Open

Timezone cannot be changed at the OS-level breaking TOTP #3824

OdinVex opened this issue Jan 24, 2025 · 0 comments
Labels

Comments

@OdinVex
Copy link

OdinVex commented Jan 24, 2025

Describe the issue you are experiencing

I've tried setting up TOTP but it refuses to accept any tokens. Some tinkering later in SSH (22222 since someone decided to change the standard port ...) and it turns out the system's stuck at Etc/UTC. It doesn't matter what timezone I specify in the Home Assistant web UI, it's always really Etc/UTC. It's also hardcoded to "time.cloudflare.com", so it'll never get updated anyway since I block any NTP unless it's to my NTP, as set by my DHCP, my preference. I attempted to edit the config and change the timezone as well but...read-only filesystem, of course, so it's stuck with TOTP being broken. I can't even disable the timesync service so I can feed it an incorrect time to make it work.

What operating system image do you use?

generic-x86-64 (Generic UEFI capable x86-64 systems)

What version of Home Assistant Operating System is installed?

6.6.66

Did the problem occur after upgrading the Operating System?

No

Hardware details

x86_64

Steps to reproduce the issue

  1. Install HAOS.
  2. "Set" timezone in web UI. (If you're around UTC is might work but anyone not around UTC it would fail.)
  3. Try to TOTP, fail. Check timezone via timedatectl in real SSH (22222).
    ...

Anything in the Supervisor logs that might be useful for us?

N/A

Anything in the Host logs that might be useful for us?

N/A

System information

No response

Additional information

Yes, my local TOTP tool's time is correct. I have no issues with it and other sites either.

@OdinVex OdinVex added the bug label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant