mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 15:05:49 +03:00
[GH-ISSUE #1051] Container unhealthy after update to 3.5.1 - not working anymore #731
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#731
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BeyondVertical on GitHub (Aug 21, 2024).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/1051
Hey there,
I just updated the image to the latest version - it is not working anymore at all, sadly, after the update.
I used Postgres 16 before and also tried the pgautoupdate-workflow - without success.
I did not change anything on my side. Can you tell me what is wrong?
Here is the log from the container:
Thanks for your work and your help!
@mariusc23 commented on GitHub (Aug 21, 2024):
Ran into the same issue with Traefik in front. After setting
DEBUG=TrueI see this:Adding
localhosttoALLOWED_HOSTSfixes the issue.@BeyondVertical commented on GitHub (Aug 21, 2024):
That is exactly my setup, @mariusc23. Will have a look at this later on. Where would I put the localhost, traefik config?
@huyz commented on GitHub (Aug 21, 2024):
My error was somewhat different. I ran the
pgautoupdateinstructions and it seems to have worked, but when I try to bring up the DB, I still getDETAIL: The data directory was initialized by PostgreSQL version 12, which is not compatible with this version 16.4strangely.My workaround was to change my docker-compose.yml to reference the image
pgautoupgrade/pgautoupgrade:16-bookwormrather thanpostgres:16sincepgautoupgradeis supposed to be a drop-in replacement.@techsolo12 commented on GitHub (Aug 21, 2024):
I ran a setup with MariaDB 10.8 and Traffik and got the same error. After adding
,localhostto my normal hc address inALLOWED_HOSTSthe stack work again.@cuu508 commented on GitHub (Aug 21, 2024):
I added a HEALTHCHECK instruction in the Dockerfile here:
github.com/healthchecks/healthchecks@8fed685f12The healthcheck script calls
http://localhost:8000/api/v3/status/, which fails iflocalhostis not inALLOWED_HOSTS. This is my error, I didn't think of ALLOWED_HOSTS while working on this. Not yet sure what the best fix would be.@BeyondVertical commented on GitHub (Aug 21, 2024):
Make it variable and configurable via Environment variable, so that the default is localhost and if someone needs another hostname, we could set the variable?
@cuu508 commented on GitHub (Aug 21, 2024):
I pushed a fix, and released v3.5.2 (image is up on Docker Hub).
The fix is to take the first value from the ALLOWED_HOSTS setting, and use it in the HTTP Host header when making requests to
http://localhost:8000/api/v3/status/.@BeyondVertical, @techsolo12 if you get a chance to test, please let me know if it works for you. If you added
localhosttoALLOWED_HOSTSto make v3.5.1 work, please try removing it – it should work without it same as v3.4 did.@techsolo12 commented on GitHub (Aug 21, 2024):
@cuu508 Thank you for the fix. I removed the
localhost, pull the new image and for now it seems to work. I will monitor it for some days.@etho201 commented on GitHub (Aug 21, 2024):
I can confirm
v3.5.2fixes the issue.@BeyondVertical commented on GitHub (Aug 21, 2024):
Yeah, confirmed. Thanks for this fix. I did not need to change anything - and couldn't because I wasn't at home all day. So, thanks! :)