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

Connection reset #519

Open
langbival opened this issue Dec 18, 2024 · 1 comment
Open

Connection reset #519

langbival opened this issue Dec 18, 2024 · 1 comment

Comments

@langbival
Copy link

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.

@almarklein
Copy link
Owner

Hi, thanks for reporting!

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants