-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server timeout: Cannot read property 'replace' of undefined #16
Comments
Hi, thank you for reaching out to me! I've tried to reproduce, unsuccessfully. So, for the moment I can only share some considerations with you. 1. Stange output
This is the normal log of https-localhost. A line is missing, though. These two lines are usually preceded by this one:
where Can you please check if it prints this line? 2.
Supposing is not a React error, but an error concerning https-localhost, it should be related to an object on which I call the There are two This latter is executed when the For that reason, I suppose the problem is in It is possible that you visited this page and that this error appears only after that action? 3. Truncated logs Thank you for your cooperation! |
Could well be the problem, i'm gonna set the alias for the ENV variable to be permanent and watch for changes instead of feeding in the absolute path. |
I was calling react-scripts and serve simultaneously so, perhaps that had a conflicting issue, got the following output by adding the ssl path as a permanent environment variable and calling serve on it's own.
Will keep you posted on the state of operatives 🙌 |
Ok so it still occurred 😢
Strange though I access the HTTP gateway for the serve multiple times and it doesn't seems to effect the functionality, even though eventually the error just emits. Attempting to change Trying |
Thank you for the complete log. Unfortunately, it is not as useful as I hope. Anyway, it really seems related to index.js row 44: I've tried to reproduce again, even with a permanent environment variable, but even after many tries it still works to me. Let me know if your tries fix the bug. Meanwhile, I've prepared a workaround in case a fix is not found. It simply looks if |
Fixed by the hardcoding it as you said, thanks! |
Published v4.1.3 on npm with the fix. Thank you! |
Pretty simple I run the server and all works fine and dandy before it times out.
CLI:
Log:
The text was updated successfully, but these errors were encountered: