Local Community

Bug: Erroneous "Connection to Flywheel does not support multisite" messages

Bugs
#1

Bug Summary

“Connection to Flywheel does not support multisite” messages appear for non-multisite sites.

This happens randomly. Stopping and starting the site again usually fixes it, but sometimes multiple times are required.

Steps to reproduce

Start a non-multisite site. Click on push or pull icons.

Environment Info

Describe your environment.

  • What Operating System are you using? macOS, all versions going back a year or two
  • What version of Local is installed? All versions going back at least a year or two

Screen Shot 2021-09-30 at 11.42.13 AM
Screen Shot 2021-09-30 at 11.42.13 AM815×265 14.7 KB

#2

It’s hard to say what’s going on without reliable recreation steps.

Is there anything in the Local log that points to something specific? You can find the Local log by following this Community Forum post:

#3

I know. Unfortunately, it’s random. Just an FYI that this happens. Maybe there’s some check that times out or gets a truthy/falsey answer that needs === instead of ==

1 Like
#4

This happens to me as well and has been happening to me for over a year. It usually doesn’t happen until I’ve been developing for a few hours with the site running and then randomly it will stop allowing me to push to staging or production with the same error noted above. I’m running my own local environment (Postcss, Livereload Server) and the Local App. I’m on the latest Mac version 12.0.1 and Local version (6.2.1+5711). Attached are my logs and screen shot. I filed a ticket to Flywheel and they sent me to this post.

Screen Shot 2022-02-05 at 12.53.39 PM
Screen Shot 2022-02-05 at 12.53.39 PM1312×912 98.4 KB

local-logs.zip (74.7 KB)

#5

Yep. I get this too and it behaves just as @jessetrippe describes. Restarting the app fixes it.

#6

I also get this sometimes. I usually don’t have to restart the site, but I just click on another one of my sites in the list, then click back on the site that’s doing it. That usually fixes it.

#7

I also just got this error. I had rebooted both Local itself and the local site and still was getting this message. The “trick” of clicking on another site and then back to the one I was trying to work with appears to have “fixed” this particular issue, at least temporarily.

#8

Just updated to 6.4.1. I can’t push or pull any site. Restarting the app does not fix it.