504 errors require computer restart
See original GitHub issueChecks
- I understand project setup issues should be asked on StackOverflow or in GitHub Discussions.
- I updated to latest
http-proxy-middleware
.
Describe the bug (be clear and concise)
Firstly, Thank You!
Frequently my team requires restarting our computer to solve all our requests resolving to a 504. We have been following this thread which seems to accurately describe and diagnose the problem. I have a very detailed post of our latest findings and figured belongs here.
https://github.com/netlify/create-react-app-lambda/issues/19
This could very well be a OS/System issue, but I want your eyes on it /// see if you’ve seen it.
Best, Richard Miles
Step-by-step reproduction instructions
https://github.com/netlify/create-react-app-lambda/issues/19
Expected behavior (be clear and concise)
Non 504 errors.
How is http-proxy-middleware used in your project?
All request proxy to apache Wordpress.
What http-proxy-middleware configuration are you using?
simple routing.
What OS/version and node/version are you seeing the problem?
Monterey 12.2.1
Additional context (optional)
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to Fix 504 Gateway Timeout Errors - Business Insider
A 504 gateway timeout error is an error that arises when a website server ... Close and re-open the web browser, or restart...
Read more >How to Fix the 504 Gateway Timeout Error on Your Site - Kinsta
A 504 Gateway Timeout error indicates that the web server is waiting too long to respond from another server and “timing out.” There...
Read more >The Quick & Easy Guide to Fixing 504 Gateway Timeout Errors
In Windows-based programs, a 504 error will appear as ERROR 504, HTTP_STATUS_GATEWAY_TIMEOUT, or “The request was timed out waiting for a ...
Read more >What is 504 Gateway Timeout Error and How To Fix It [5 Ways]
A 504 error will occur as ERROR 504, HTTP_STATUS_GATEWAY_TIMEOUT, or “The request was timed out waiting for a gateway message.”.
Read more >Here's how to fix a 504 Gateway Timeout error - Lifewire
A 504 Gateway Timeout error means that one server involved in displaying the web page did not communicate to another one quickly enough....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In react v18 the behavior has changed to allow DNS to resolve ipv4 or ipv6 in any order, ie use first provided by OS. With macOs 12.4 (21F79) I believe ipv6 is the default regardless of order provided in your hosts file. This may have more or less been random, chosen at restart, but the links provided go into this in more detail.
My apache configuration was not setup to receive traffic from ipv6. Adding the listener as follows and restarting apache fixed this issue without a restart.
httpd.conf
This solves // completes my research. Hopefully this info I’ve added here will help the next person. 😃
Thanks for getting back and sharing your research and solution! 🚀