404 after updating environment


#1

As Local suggested, I updated the environment of my site. However, the clone it created gives me an 404. Both admin as the front side aren’t available. It is a nginx 404 error I get. Any suggestions?

Edit 1: I’m working on a MacBook Pro with macOS 10.14.1 running.
Edit 2: Every site isn’t working anymore. I’m getting 502 errors. Pretty bad this…


#2

Was there solution to this at all? I’m having the same problem on both of the sites I currently have in Local - https://www.dropbox.com/s/m2l3cc2hgou14z3/Screenshot%202019-02-02%2022.44.10.png?dl=0

Thanks


#3

From what I remember, it takes some time to update. Just wait a few minutes, and it will show up.


#4

He @8persap

As @wvanderzee indicates, it can take a little time for things to be fully updated. Are you still having issues with the sites giving an NGINX 404?

Some additional troubleshooting steps would be:

  • Wait a bit to see if it completes updating things
  • Restart Local
  • Restart the VM from the “Help > Restart Virtual Machine”

Let us know how it goes, or if you have any other questions – if you do, please include the Local log so we can see any additional errors that might be going on.

– Ben


#5

Ben,

I am getting 404’s an 403’s after restarting the local machine. What do you need to see in the logs to troubleshoot?


#6

It’s hard to say without seeing the logs. In general, I look to see if there are any errors being reported and look to see in what context they are reported in.

This kind of an issue should just work, so we’re kind of in the realm of not knowing what to look for until we see it.

If you have your Local log, you can attach it here and we can take a look.

– Ben


#7
Feb 16, 2019, 9:01 AM CST - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined,
  [ 'local-router:1.1',
    'flywheel:1.3.2',
    'flywheel:1.0',
    'local-by-flywheel:latest' ] ]
Feb 16, 2019, 9:01 AM CST - info: [main/docker-router] getRouterContainers()
Feb 16, 2019, 9:01 AM CST - info: [main/docker-router] teardown()
Feb 16, 2019, 9:01 AM CST - info: [main/docker-router] Removing router container 2105509165c10968326e363c24f67f6849464da86ccca9c0ca60f2c1077cac19
Feb 16, 2019, 9:02 AM CST - info: [main/docker-router] updateProxyManager()
Feb 16, 2019, 9:02 AM CST - info: [main/docker-router] runContainer()
Feb 16, 2019, 9:02 AM CST - info: [main/docker-network-manager] removeExistingNetworks
Feb 16, 2019, 9:02 AM CST - info: [main/docker-network-manager] createNetwork
Feb 16, 2019, 9:02 AM CST - info: [main/docker-router] reconnectNetwork()
Feb 16, 2019, 9:02 AM CST - 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`.' }

#8

Most things look like they are working, however Local can’t seem to find WordPress.

This can sometimes be cause by the DB having crashed, or possibly that the filesystem mounts aren’t in the correct state.

You can try a few things:

  • Manually restarting the Virtual Machine: “Help > Restart Virtual Machine” (this sometimes helps to restart the DB)

  • Toggle “Faster Docker Volumes” under “Preferences > Advanced” (this will refresh the filesystem mounts)

  • Zip up the site folder or use a backup, and re-import it as a new Local site. (this won’t “fix” the existing site, but it will create a new container with a new, working Database)

Let me know if that helps at all!

– Ben


#9

Thanks. Tried all three solutions, the first two did not work and the third hangs on “Creating Site Domain” when trying to import a zip’d export. Please advise.


#10

@ben.turner When trying to import the exported site it gives me a MySQL error which makes sense because that is why the current site is missing. Does this mean I have lost my local version of the site and need to start over? Please advise.


#11

Depending on how large the site is, it might make sense to start over – especially if there are a small number of pages or settings that need to be created.

You can also try reviewing the mysql errors by looking at the logs/mysql/error.log and see if there is anything useful in pointing to a way of fixing things.

Hope that helps you in thinking through a workflow for recoving things and getting on with development!

– Ben