Update health check endpoint of Nocodb service #4736
Merged
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Update NocoDB config file with correct health check endpoint.
Issues
During the migration from an Alpine Linux-based Docker image to a Debian-based one, the behavior of wget changed. The previous setup worked because Alpine used BusyBox wget, which handled the / endpoint differently. However, in Debian, the GNU wget follows redirects more strictly, and the / endpoint now redirects to /dashboard, causing health checks to fail.
This update ensures compatibility with the Debian-based Docker image by pointing the health check to an appropriate endpoint, resolving the redirect handling issue.
Related Discord discussion: - here
Community forum topic: Cannot access NocoDB after install