GitHub unavailability leads to health check failing

[hypervtechnics]

Description

GitHub had a downtime recently for my network and requests to github were timing out. Though no real impact on the running jellyseerr instance the corresponding status endpoint /api/v1/status timed out as well which led to my monitoring reporting jellyseerr as unhealthy. In my opinion this is either a bug in the implementation of the endpoint or there should be an option to skip the update check when calling the status endpoint.

Version

1.7.0

Steps to Reproduce

1. Block access to github.com
2. Call /api/v1/status

Screenshots

No response

Logs

jellyseerr-web-1  | 2024-02-05T21:56:22.621Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"connect ETIMEDOUT 140.82.121.6:443"}
jellyseerr-web-1  | 2024-02-05T21:56:41.052Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"connect ETIMEDOUT 140.82.121.6:443"}
jellyseerr-web-1  | 2024-02-05T21:57:00.023Z [debug][Jobs]: Starting scheduled job: Download Sync
jellyseerr-web-1  | 2024-02-05T21:58:00.027Z [debug][Jobs]: Starting scheduled job: Download Sync
jellyseerr-web-1  | 2024-02-05T21:59:00.028Z [debug][Jobs]: Starting scheduled job: Download Sync
jellyseerr-web-1  | 2024-02-05T21:59:22.845Z [warn][GitHub API]: Failed to retrieve GitHub releases. This may be an issue on GitHub's end. Overseerr can't check if it's on the latest version. {"errorMessage":"connect ETIMEDOUT 140.82.121.6:443"}

Platform

desktop

Device

Server

Operating System

Ubuntu

Browser

Firefox

Additional Context

No response

Code of Conduct

• [X] I agree to follow Jellyseerr's Code of Conduct