Generally, 404 errors can be resolved by npm installs in the frontend wherever there is a package.json file. You may need to delete generated directories like node_modules & next.. Be sure to check for unsynced fields from ACF too.
500 errors tend to be resolved by running composer install wherever there is a composer.json file.
It seems that the php code takes priority so we need to comment code or the include until we are happy with where it gets then export again.
Can't Access WP Admin from HTTPS/ Can't see block preview
net::ERR_CERT_AUTHORITY_INVALID
I had to delete the certificate from my keychain on Mac. Then, reload Local By Flywheel to generate a new certificate.
My wouldn't work with HTTPS & I couldn't change my password either.
Solution: Update password manually.
Open Adminer
Adminer
select wp_users & update user_pass with a generated MD5 Hash then the string that you put in for your password should work at the login screen for https.
Putting this here for anyone else that encounters this and gets stumped:nvm keeps switching to the a newer version of node for some reason. Until I can figure out why that’s happening, the solution I’m using to fix it is to kill the dev instance, then:
This may error may also be due to a side effect of a particular configuration in Local by Flywheel. If Local's RouterMode is set to localhost rather than Site Domains, this error will occur because graphql will not have the proper path.
I solved a lot of "not assignable to type 'IntrinsicAttributes & IntrinsicClassAttributes" type of errors just by declaring an object that is passed entirely to the component.
Error: Please set a page as the Front Page in the WP backend > settings > reading section.
This one turned out to be a data problem too. Particularly ACF Fields. A new field was added without syncing. Solution was to back out the changes, sync first & try again.