I figured I might start a new thread about this since my replies on another thread were starting to drift off topic.
Recently using 2.1.1 I realize that all sites I create from my old blueprints (that are WP 4.9 and Apache) give a 500 Internal Error UNLESS… I change the web server to “nginx”. Upgraded to 2.1.2 and issue persists.
However, my blueprints are Apache and I’d like to continue working in Apache so that when the time comes to upload to my webhost, it will work. Oh another thing, the only sites I’ve been able to create off the blueprints and STILL work in Apache are those that I named the same as the original site that the blueprint was made from.
So my current workaround right now is to work in nginx mode but I’m worried of whether or not my site will work when the time comes to upload it to an apache remote host. Something’s not right here obviously.
NOTE: I am able to reproduce the error on both my desktop AND my laptop. In both cases, the only workaround is to switch my web server to nginx.
IS THERE A KNOWN ISSUE WITH USING BLUEPRINTS TO CREATE NEW SITES WITH APACHE WEB SERVER???
I only have 2 options at this point: change my newly created sites to nginx and hope for the best when i upload to apache remote server, OR, stop using blueprints to create a new site because Apache works for the new site as long as it is not based on a blueprint.
Other thing I notice is that I still get VirtualBox notice on shutdown of computer - even if all sites stopped and properly exited Local Flywheel. Also, the Database–>Adminer function leads to 500 error for these sites based on the blueprints.