I’m assuming macOS 11 will are released soon - either ant next week’s event or just a bit later. I don’t see anything much about whether the current version of Local works on it. Can staff confirm if it does or not?
Anyone? Bueller??
Local mostly works with Big Sur. There’s currently only one issue that we know about, related to opening a site’s shell, but it appears that you can still open the shell environment, it just isn’t as automated as it was before:
Right now it’s VERY SLOW to do updates within WP. Anyone else seeing this?
OK it’s not slow. It just doesnt do anything. At all. It goes the screen, hangs and then returns:
*( ! ) Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the <a href="https://wordpress.org/support/forums/">support forums</a>. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /Users/rick/Local Sites/soundside/app/public/wp-includes/update.php on line *607*"*
*Downloading update from https://downloads.wordpress.org/release/wordpress-5.5.3-no-content.zip…*
*Download failed.: cURL error 28: Operation timed out after 300000 milliseconds with 5914214 out of 11718757 bytes received*
*Installation failed.*
I can, of course, manually download from that link just fine.
So the answer to the title question is… , No, Local doesnt work under Big Sur, not really. Yes, it starts sites etc but if you can’t update and the like, is it really working? I’m disappointed - betas of the new macOS have been around for months. There’s been no real engagement here and now this.
I suppose you’ll eventually fix this but… come on.
Hi @rickg,
I just tested one of my sites after updating to macOS Big Sur last night with the current version of Local WP 5.9.2+5056.
Yes I had the issue most people are having where you need to downgrade from PHP 7.4.1 to 7.5.3 but other than that I was able to successfully upgarde my version of WordPress along with any plugins/themes that also required updating.
Hopefully there is a solution to the issue you’re having. I unfortunately am not running into this issue.
Brand new install. Using the Preferred settings. Go to the Updates page:
- ( ! ) Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. …*
Same error. This is ridiculous. Unless this happens to be a WordPress.org outage but I’d expect to see a lot on Twitter etc about that.
I asked weeks ago if this worked. I asked again. And it doesn’t. Not reliably at least. And yes, this is 5.9.2
In case they help, Here’s the relevant lines from that from the router log:
2020/11/13 13:45:18 [error] 984#0: *130 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: ::1, server: soundside.local, request: "GET /wp-admin/?cache-buster=396 HTTP/1.1", upstream: "http://127.0.0.1:10030/wp-admin/?cache-buster=396", host: "soundside.local"
2020/11/13 13:45:18 [error] 984#0: *132 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: ::1, server: soundside.local, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10030/favicon.ico", host: "soundside.local", referrer: "http://soundside.local/wp-admin/?cache-buster=396"
2020/11/13 13:47:02 [warn] 1071#0: *138 a client request body is buffered to a temporary file /Users/rick/Library/Application Support/Local/run/router/nginx/client_body_temp/0000000001, client: ::1, server: soundside.local, request: "POST /wp-admin/update.php?action=upload-plugin HTTP/1.1", host: "soundside.local", referrer: "http://soundside.local/wp-admin/plugin-install.php"
and regular local logs attached. local-lightning.log (23.8 KB)
OK, got it. If you create a new Local site, it’s not SSL trusted by default. You need to click Trust and let Local do its thing. If you do this, everything works. if you do NOT, you get the above error.
This is new to me in Big Sur and might be some interaction or it might be coincidence.
Well… it looks like I owe the Local team an apology. I was troubleshooting very slow downloads from one of my servers with the folks at Vultr and in running some tests, we noticed that the connection at my end with Comcast was showing very high and very variable ping times, up to 500ms.
I restarted the cable modem and router which fixed that issue… and seems to have fixed this one. I’ll test more, but for the Local people you might want to keep this around as a known issue that affects Local, but isn’t Local’s problem per se.
To figure this out, I used mtr, a tool that exists on all platforms. See this link for details: https://www.vultr.com/docs/how-to-send-an-mtr-report-to-support
1 Like
Thanks for replying back with the fix – I hadn’t ever seen that mtr tool, but it looks handy!
In general, this error:
Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration
Means that WordPress can’t reach wordpress.org. Like you discovered, it’s usually network or infrastructure related.
In your case it sounds like your router, but other instances I’ve seen are things like a VPN connection, or a coffee shop or other public wifi that locks down outbound requests.
Definitely a hard error to zero in on a fix!
4 posts were split to a new topic: Only Getting localhost for Local Site
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.