Hey @ignasitort – There usually is a slight delay between when the UI of Local is ready and when the site is fully “turned on” and accessible. This is mostly just the Virtual Machine turning on the various pieces of code like MySQL, NGINX, etc. ...
Can you help with this issue? It’s similar but different. Here’s my error log:
2018/11/26 17:25:54 [error] 6#6: *5 upstream prematurely closed connection while reading response header from upstream, client: 172.18.0.3, server: starter.local, request: "POST /wp-cron.php?doing_wp_cron=1543253153.3822660446166992187500 HTTP/1.1", upstream: "http://192.168.95.100:4000/wp-cron.php?doing_wp_cron=1543253153.3822660446166992187500", host: "starter.local", referrer: "http://starter.local/wp-cron.php?doing_wp_cron=1543253153.3822660446166992187500"
Hey @thinkpath
That looks like an NGINX error. Can you describe in a little more detail what things are going wrong along with what you are trying to do when you see that error?
It might also be helpful if you can provide your Local log. See
“How do I retrieve Local’s log file? ” for instructions on how to do so.
– Ben