mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 06:55:53 +03:00
[GH-ISSUE #621] Shields.io JSON endpoint #452
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#452
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 @mircotroue on GitHub (Mar 16, 2022).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/621
The shields.io functionality seems to be broken in the selfhosted version of healthchecks. A correctly formatted json response is generated at the provided URL, however, testing of the endpoint of shield.io yields a "custom badge | inaccessible" error.
@cuu508 commented on GitHub (Mar 16, 2022):
Looks like shields.io returns "inaccessible" if the data endpoint returns HTTP status code >= 500.
Example: https://img.shields.io/endpoint?url=https://statuscod.es/500
Perhaps there are more conditions when it returns "inaccessible", I'm not sure.
Can you check in your server's access logs to see what the HTTP status codes are for requests initiated by shields.io?
@mircotroue commented on GitHub (Mar 16, 2022):
Performing a call on the badge URL from healthchecks results in a 200 (OK) status. Directly calling the shields.io URL does not produce any entry in my nginx access log. Therefore I believe that this a problem on the shield server side and that no GET request is actually performed. This might be due to an SSL problem.