You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @ALL,
docker setup according to https://timetagger.app/articles/selfhost2/
When the newest version v24.12.2 is run (with corrected ports 8080:8080) all HTTP Requests just get a read error:
In the last release the default binding was changed, but this should not affect that guide since it sets TIMETAGGER_BIND explicitly, so the default value does not matter.
I'm not sure what you mean with "with corrected ports 8080:8080". Can you please be more specific on what you expected to work that didn't?
Hi @ALL,
docker setup according to https://timetagger.app/articles/selfhost2/
When the newest version v24.12.2 is run (with corrected ports 8080:8080) all HTTP Requests just get a read error:
`
$ wget -O- http://localhost:8080
--2024-12-18 15:45:27-- http://localhost:8080/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8080... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.
--2024-12-18 15:45:28-- (try: 2) http://localhost:8080/
Connecting to localhost (localhost)|::1|:8080... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.
`
Exactly the same configuration sans the modification 80:80 to 8080:8080 did work.
The text was updated successfully, but these errors were encountered: