Question 1

How do I fix 'Started Earlier' automatically populating a stopped time after updating to v25.12.1?

Accepted Answer

This was a regression in v25.12.1. Upgrade to the newest release containing pull request #597, which removes the timeout that caused Started Earlier to intermittently fill in a stop time. Do not rely on a release containing only the earlier fix #586, because that introduced another bug (#587). As a temporary workaround, roll back to v25.06.1, where the behavior works correctly.

Question 2

How do I prevent the start time from resetting to 01:00 when I press Enter in the end-time field?

Accepted Answer

This affects v26.1.1 in Chrome and Firefox. It occurs when the typed end time briefly becomes earlier than the start time, often after pressing Ctrl+A and replacing the whole value. The app automatically adjusts the start time, but the start-time field does not immediately show the changed value, so pressing Enter saves the unexpected 01:00. Workaround: avoid making the end time less than the start time even temporarily while typing. Use the time field's +/- buttons, edit only the minute part, or first move the start time earlier if needed. If the invalid state has already occurred, cancel or reload before saving, then re-enter the times using the buttons. A pull request with a fix was submitted; upgrade to a release containing it when available.

Question 3

How to remove the /timetagger URL prefix when self-hosting TimeTagger?

Accepted Answer

Use a reverse proxy like Caddy to redirect root requests to /timetagger/app and proxy to the TimeTagger container. Example Caddyfile: 'timetagger.example.com { redir / /timetagger/app/; reverse_proxy localhost:8081 }'. Alternatively, create a custom main script based on __main__.py to modify the path, or use the upcoming feature from PR #577 with arguments '--path_prefix=/ --app-redirect=true' (once merged).

Question 4

How to fix 'Runtime error because there is no client scope' when using Timetagger behind a reverse proxy with Unix socket binding?

Accepted Answer

This error occurs when Timetagger is bound to a Unix socket (TIMETAGGER_BIND=unix:...) and proxy authentication is enabled, because the ASGI request.scope may not contain a 'client' key. As a workaround, copy /timetagger/__main__.py to a separate location, then comment out or modify the trust check block near line 157. For example, replace:

```python
client = request.scope["client"][0]
if client not in TRUSTED_PROXIES:
    return 403, {}, "forbidden: the proxy is not trusted"
```

with:

```python
if "client" in request.scope:
    client = request.scope["client"][0]
    if client not in TRUSTED_PROXIES:
        return 403, {}, "forbidden: the proxy is not trusted"
```

Then start Timetagger with the modified file as the entry point. This preserves some trust checking when a client IP is available. Alternatively, simply comment out the entire block if your environment is fully trusted. No official patch is yet available (as of Timetagger 25.06.1). Track the issue for updates.

TimeTagger

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects