Local Community

File not found error when trying to open Local

Support
#1

Hi,

I am having some issues with Local - I am no longer able to open the application. When I try to, I receive an error message “That file cannot be found.”

Background: After updated Local, I wasn’t able to create new sites (I was taken through the setup wizard, but ended on a blank screen after importing the environment). So, I uninstalled Local, removed the local-by-flywheel virtual box, and reinstalled the application. Now, not only can I not create a new site - I can’t even open the application!

This has been a huge, costly pain - so if anyone has any advice please let me know :slight_smile:

I am running on a 2011 Mac with High Sierra, VirtualBox 5.2.20

Thanks!

#2

Hey @jillii –

There could be a lot of things that are going on here. Can you please provide your local-by-flywheel.log file so we can see what Local is running into? See
“How do I retrieve Local’s log file?” for instructions on how to do so.

– Ben

#3

That will be a little difficult as I cannot open Local :wink:

I did do a search in my file directory for “local-by-flywheel.log” and there is nothing there. So maybe that’s a clue?

#4

Hey @jillii –

When you re-installed Local, did you try completely removing Local by following the steps in one of these guides:

I’m wondering if there is some sort of user-specific configuration files that are preventing things from being installed correctly.

– Ben

#5

You’re right! I forgot a step to fully remove Local. I was able to re-install it, which is great, but now it stalls on the “Starting Local Machine…” loading screen, and never actually opens. Much closer - but still doesn’t work :confused:

There must be a different problem. Let me know if I should open a new issue. My logs are attached.

Thanks,

Jill

local-by-flywheel.log.zip (1.4 KB)

#6

That does sound like progress @jillii –

A couple of things stand out to me in this Local log:

Feb 12, 2019, 4:19 PM EST - warn: [main/index] Unhandled Rejection at: Promise  Promise {
  <rejected> { Error: ETIMEDOUT
    at Timeout._onTimeout (/private/var/folders/l6/c0gt_yhn5hbgm8z4cd5pxbn80000gn/T/AppTranslocation/881860E9-1A49-4EEE-BCA4-332E734F83F7/d/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/request/request.js:849:19)
    at ontimeout (timers.js:427:11)
    at tryOnTimeout (timers.js:289:5)
    at listOnTimeout (timers.js:252:5)
    at Timer.processTimers (timers.js:212:10) code: 'ETIMEDOUT', connect: true } }  reason:  
{ message: 'ETIMEDOUT',
  stack:
   'Error: ETIMEDOUT\n    at Timeout._onTimeout (/private/var/folders/l6/c0gt_yhn5hbgm8z4cd5pxbn80000gn/T/AppTranslocation/881860E9-1A49-4EEE-BCA4-332E734F83F7/d/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/request/request.js:849:19)\n    at ontimeout (timers.js:427:11)\n    at tryOnTimeout (timers.js:289:5)\n    at listOnTimeout (timers.js:252:5)\n    at Timer.processTimers (timers.js:212:10)',
  code: 'ETIMEDOUT',
  connect: true }

The ETIMEDOUT warning usually means that Local wasn’t able to communicate with VirtualBox in the allotted time.

A couple things to think of and/or try:

  • Any antivirus software, or recent security updates? This might be interfering with Local communicating with VBox
  • I notice that Local is installed using Mac’s “AppTransLocation” (that’s the /private/var/folders/l.../AppTranslocation/.../Local by Flywheel.app/... part of the Local log) – Can you try to unquarantine the .app bundle using the link @clay mentions here: [macOS] Help! Local isn’t automatically updating!

Try a restart of the computer after doing that, and if that doesn’t work, can you provide an updated version of the Local log?

– Ben

#7