After ensuring logs were turned on I checked every log file I could think of (Apache, PHP, ElasticSearch,MySQL, Sugar). No hints.

Through XDEBUG and PHPSTORM, I was able to trace the patch of execution as follows:

In the execute function of SugarApplication.php, the conditions at lines 84 and 108 evaluate to false and we are hitting line 117 which returns us to the $app->execute(); at line 27 of index.php which of course results in the Sugar application shutting down.

As I am not totally familiar with the framework yet, I was wondering if someone could point me in the right direction. What path should we be taking through the execute function in SugarApplication.php. I did notice in the debugger output that $msid was null after the request invocation at line 79. Should $msid have a value at this point?

When you copied your instance, did you also copy the cache directory? if so, remove the contents of your cache directory (it's in your sugarcrm root directory) and try again

Also check that your .htaccess (in your sugarcrm root directory) is set correctly.

Finally, note that, as far as I know, 7.11 was never available for onPremise deployments, it was only for Cloud. You can download 7.11-dev (the developer edition for those who want to test their customizations) from developer builds on the Developer pages: Developer Builds

I wonder if there is something in place to keep you from using 7.11 onPremise.

You should also be able to download the full version 8 (which was released for both onPremise and Cloud customers) from your SugarCRM portal.

Here's a copy of everything that is in the .htaccess file. Note: As the .htaccess file did not come with the backup instance I downloaded I created one. I found this one by searching through the Sugar community.

Not sure if this helps, but I captured the javascript console information from the working production instance at SugarCRM and the javascript console information from the non working local instance....

1. check the session_dir in the config.php, be sure that the path you specify is reachable(file permission) by the apache user. If in the session_dir array there is no specify value, please check also session.save_path setting in your php.ini.

2. Another checkpoint is the default permission array in the config.php

Rather than just checking the file permissions, I actually executed the following commands to be sure everything was set properly. Shout out to Francesca Shiekh for providing the commands!

sudo find . -type d -exec chmod 775 {} \;

sudo find . -type f -exec chmod 664 {} \;

sudo chmod 775 bin/sugarcrm

Not sure if it would have an impact, but I did create a second hard disk in the virtual machine to hold the mysql data. The backup instance had 28G of data and I ran out of space on the primary harddrive. Currently, mysql is set up to use /mnt/sdb1/mysql

I finally have the backup instance up and running in Vagrant box sugarcrm/php71es54. Yeah! I did add a second disk to the virtual box to support the 28G of mysql data that came with the back up instance. Clearly, I have a configuration issue in the LAMP stack I built, but as I need to move forward with my development project I will leave finding and resolving that issue for another day.