Because Cloudflare operates as a reverse proxy the IP address your server will see is one of a limited number of Cloudflare IPs. If the IPs that fail are consistent each time, that indicates some of the IPs in Cloudflare’s IP ranges are either being rate-limited or blocked by a network device at your hosting provider. Make sure your hosting provider isn’t rate limiting or blocking IP requests from the Cloudflare IPs and ask them to allow the IP addresses here. Make sure that you’re not blocking Cloudflare IPs in. When this happens, you’ll see “ERR_CONNECTION_TIMED_OUT”. This typically happens when Cloudflare requests to the origin (your webserver) get blocked. In the meantime, I will test developing in the cloud, which is not an option for locations without good internet access.Try the suggestions in this Community Tip to help you fix Error 522 “ERR CONNECTION TIMED OUT” in Google Chrome or “The connection has timed out” in Firefox.Ī 522 error happens when a TCP connection to the web server could not be established. Buying a Stick PC solved this and gives me a native local Windows hardware for less than 90€.īut a lack of Docker support made it clear that I will wait for the next generation of the MacBook Pro with more memory and an updated version of Big Sur and Docker. The only problem I have with my current setup is speed - some of my bigger PHP applications eat a lot of memory and CPU.Īfter studying benchmarks and posts, I first thought that my only problem was VirtualBox. My current development environment for web-based applications and services is based on:

When Apple presented the new MacBooks with M1 chips, I immediately canceled the order. I am currently using a 13' MacBook Pro 2016, Intel 3.3 GHz i7 and was planning to switch to a new MacBook Pro i7/32GB that I had ordered at the beginning of September. My Personal Roadmap to an M1-Based MacBook

Docker for mac network timed out