Updating Plugins

Having no luck updating my plugins in Local:

Update Failed: Local Router Error blockquote { margin: 10% 25%; width: 50%; } body {font-family: arial,sans-serif} img { border:none; } Local Router Error Our apologies for the inconvenience. The Local router is not able to connect to the site you requested. We suggest you try the following: Restart Site - Go to the Local by Flywheel app and restart the site you are attempting to access. Contact us - If the issue persists please contact us.

@ElodieG,

Is this site running the Preferred or Custom environment?

Also, is this happening when updating multiple plugins at a time or is it still happening even when updating one plugin at a time?

Hi Clay:

The site is running Preferred. This happens for single and multiple plugins.

Elodie

I’m experiencing this same issue, running Preferred and for single or multiple plugins, or adding a new plugin, or updating wordpress. Related, everything (frontend and backend pages) began running much much slower (sometimes 30sec) the same time updates broke.

Yes, also tried to upload a theme plugin to a new build on Local and it timed out with the following message:

PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature

Wonder is it all related?

@ElodieG Every time I’ve seen this error it’s an authentication issue.

Interesting. Authentication with WordPress, permissions, or something else?


@nkraus @ElodieG,

Can you both try the steps in this article? Help! My Local site cannot establish a connection to WordPress.org - Local Classic FAQs - Local Community

@clay I only ever saw it when trying to update from a Bitbucket private repository.

1 Like

@clay , I followed those steps and still got the same error trying to update the plugins.

@nkraus,

Got it. Thanks for giving it a try!

Can you please zip up the logs folder (adjacent to app folder) for that Local site and upload it here? Feel free to private message me the archive in case it’s not a throwaway dev site.

@clay here you go, hope it helps!
logs.zip (194.6 KB)

@nkraus

Thanks! I appreciate it!

I have one more bit of information for you to gather if you’re up for it:

(Note: This will only work on macOS. If you need instructions for Windows let me know.)

  1. Open Terminal and run the following (leave this Terminal window open):
/Applications/Local\ by\ Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker ps | grep nginx | awk '{print $1 "\t"}' | xargs -I '{}' /Applications/Local\ by\ Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker exec {} tail -f /var/log/nginx/error.log
  1. Attempt an upgrade in WordPress that normally causes an error
  2. Check the Terminal window for errors.
  3. Copy and paste any errors you see here.
  4. Feel free to close the Terminal window :slight_smile:

@clay I received this when running that command “Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?”

Agh, I’m sorry! I forgot a step. Here are the new instructions.

  1. Make sure Local is open and a site is running
  2. Open Terminal and run the following:
eval $(/Applications/Local\ by\ Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine env local-by-flywheel)
  1. Run the following and leave this Terminal window open.
/Applications/Local\ by\ Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker ps | grep nginx | awk '{print $1 "\t"}' | xargs -I '{}' /Applications/Local\ by\ Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker exec {} tail -f /var/log/nginx/error.log
  1. Attempt an upgrade in WordPress that normally causes an error
  2. Check the Terminal window for errors.
  3. Copy and paste any errors you see here.
  4. Feel free to close the Terminal window :slight_smile:

@clay

2018/04/23 21:48:39 [error] 5#0: *115 upstream prematurely closed connection while reading response header from upstream, client: 192.168.95.1, server: gsbcolorado.test, request: "GET /wp-admin/update.php?action=update-selected&plugins=woocommerce%2Fwoocommerce.php%2Cwoocommerce-discounts-plus%2Findex.php&_wpnonce=918875a3e8 HTTP/1.1", upstream: "http://192.168.95.100:4000/wp-admin/update.php?action=update-selected&plugins=woocommerce%2Fwoocommerce.php%2Cwoocommerce-discounts-plus%2Findex.php&_wpnonce=918875a3e8", host: "gsbcolorado.test", referrer: "http://gsbcolorado.test/wp-admin/update-core.php?action=do-plugin-upgrade"
1 Like

@nkraus,

Thanks again.

How soon do you see the router error after starting the WordPress/theme/plugin update(s)?

@clay it took about 30 seconds to go from the updates page to http://gsbcolorado.test/wp-admin/update-core.php?action=do-plugin-upgrade (which is about how long pages take to load) and then it died at 1:25

1 Like

Hi Clay:

I am not a regular cmd user! I am on a mac. Copied and pasted your instructions into the Terminal and here is the result. Still having the update issue?

@clay this matter seems to be resolved. Managed to update all the plugins. The only thing I did of note was log out of one of my websites?