Add backend server error handling for startup failures - #14
Open
srbot2016 wants to merge 1 commit into
Open
Conversation
…ort listen failures such as EACCES and EADDRINUSE. Add an error handler to the Express backend server to capture and report listen failures such as EACCES and EADDRINUSE. Previously, when the backend failed to bind to its configured port, the application only reported that the backend failed to start after a timeout, without exposing the underlying Node.js error. This change makes backend startup failures easier to diagnose by logging the original server error details.
This file contains hidden or 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
1 participant
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.
Problem
When the backend failed during startup, the application did not provide
the actual reason for the failure.
In my case, the backend startup was failing because Node.js could not
bind to the configured port:
Error: listen EACCES: permission denied 0.0.0.0:3001
However, without a server error handler, this failure was not surfaced
clearly. The Electron application only reported:
Backend startup failed: Backend did not start in time
This made diagnosing the issue much harder because the real networking
error was hidden.
Solution
Added an error listener to the backend HTTP server:
Benefits
EADDRINUSE)EACCES)Testing