Flywheel is packing up the files to get ready to transport. Giving it another try, you’ll find yourself in familiar territory. You’ll be redirected to their web service, and they’ll ask permission to redirect you back to Local. You can restart here if you want, but the goal is to reauthenticate your account. You click on your name and click log out.
You click on the Connect to Flywheel button and look for your account options in the top right of the application. Unfortunately, they do not prompt you or error anything out before this point. Flywheel uses a security token to associate your account, and now your old token is invalid.
#Local by flywheel support password#
Boy, Flywheel really wants you to see there is something wrong! This isn’t a bad thing.Īt this point, you realize that you changed your email or password to your Flywheel account. The environment is undefined.Īnd you also see an error heading stating the site container is missing as well. You also get a popup error that stipulates the same thing. Looking at the overview of your newly pulled site, you see the environment is unavailable, thus unable to even start. When it starts back up, you get different errors. You restart your web environments and the entire Local application. The site shows up under Local Sites but doesn’t start, and your directory doesn’t have the site listed. It goes through the motions, and when it’s done, you see this error: You click on the Connect to Flywheel tab, and under Available Sites, you select Pull to Local.
While you’re at it, ensure you’re running the latest release version of Local. Simply log out of the Connect to Flywheel tab and reconnect. If you’re trying to pull a site from one of your Flywheel slots and Local is giving you strange errors, the error pulling site fix in Local is simple.
0 kommentar(er)
