"This site can’t be reached" until virtual machine restarted

Support
1

The latest version + Mojave appear to be having issues with the virtual machine. Even after stopping/starting my sites, they aren’t loading up. VirtualBox shows that the machine is running, but the sites won’t work. Even if I change the domains, they still won’t connect.

The only solution appears to be restarting the virtual machine.

Is this a known issue? Which logs can I provide to help?

2

Hey Scott,

Sorry about this!

VirtualBox may need updated after the update to Mojave. Have you tried the steps here recently? How can I manually update VirtualBox?

3

I manually updated already, and I’m on the latest version of Local :confused:

4

Gotcha, thanks for giving that a try!

What error are you running into in your browser? What happens if you ping the Local site domain in Terminal?

I’d start with the Local Router Log which is available under the Help menu. It may be failing to start up.

5

Here’s what I’m seeing:

2018/10/03 03:22:43 [error] 6#6: *48 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.95.1, server: [[LOCAL URL]], request: "GET / HTTP/1.1", upstream: "http://192.168.95.100:4028/", host: "[[LOCAL URL]]"

I believe I was getting err_connection_refused on Chrome. I’ll try a ping the next time it happens.

6 
Oct 3, 2018, 12:29 PM PDT - info: [EnvironmentCustom] Copying MySQL config to container prior to starting.
Oct 3, 2018, 12:29 PM PDT - info: [main/waitForFile] Waiting for  /conf/php/7.0.3/etc/php-fpm.conf eb0570abca37186cb5962ff0ff0a4dda9dd6d0353a228d4abafe873254636534
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-router] getRouterContainers()
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-router] teardown()
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-router] Removing router container 010e8b29ad7d3bfef2b6ba6dbf8c268191d10911e74e3424a1a5fe1ecfe7e141
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-router] updateProxyManager()
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-router] runContainer()
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-network-manager] removeExistingNetworks
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-network-manager] createNetwork
Oct 3, 2018, 12:29 PM PDT - info: [main/docker-router] reconnectNetwork()
Oct 3, 2018, 12:29 PM PDT - warn: [main/SiteModel] wpInstalled not returning "installed" 
{ stdout: '',
  stderr: 'Error: This does not seem to be a WordPress install.\nPass --path=`path/to/wordpress` or run `wp core download`.' }
Oct 3, 2018, 12:29 PM PDT - warn: [main/SiteModel] wpInstalled not returning "installed" 
{ stdout: '',
  stderr: 'Error: This does not seem to be a WordPress install.\nPass --path=`path/to/wordpress` or run `wp core download`.' }
Oct 3, 2018, 12:29 PM PDT - warn: [main/waitForFile] /conf/php/7.0.3/etc/php-fpm.conf does not exist 
{ stdout: '', stderr: '' }
Oct 3, 2018, 12:29 PM PDT - warn: [main/index] Unhandled Rejection at: Promise  Promise {
  <rejected> '/conf/php/7.0.3/etc/php-fpm.conf does not exist.' }  reason:  /conf/php/7.0.3/etc/php-fpm.conf does not exist.```
7

Thanks for the logs!

Based off of the WP not installed errors and conf file not existing, it may be a volume mounting issue. Toggling Faster Docker Volumes on or off (opposite of current state) might help.

8