500 Server Error on Login

Where is the sandbox installed? On the customer datacenter or anywhere else?

I believe that this is an issue with .htaccess not point to correct RewriteBase. Double check the official best practices for installation here.

Hi Andre,

It is installed on a Debian server hosted by a third party. I am currently looking through the document you linked to see if any configurations are not set correctly. 

As far as I can tell our Sandbox .htaccess file matches Production's exactly, which is connecting fine.

It shouldn't match exactly. The Rewrite base should be different.

In case it wasn't clear, my two installations are located on individual servers. So to my understanding, a number of rules including the Rewrite base should be similar if their directories are matching.

If the directories match then yes the rewrite base would be the same.

Why not clone it to the same server?
https://support.sugarcrm.com/Knowledge_Base/Platform_Management/Cloning_a_Sugar_Instance_for_Testing/

I went ahead and followed that documentation and am now getting past that initial 500 error.

I am now running into additional 500 errors after login that I believe are related to the sandbox database not correctly compiling the cache folder. The Sandbox generates only a fraction of the files present in the Production server.

Check out the Sugar error log as well.

Can you get to the Repair option in the administration module?

If I recall correctly, you can safely delete the contents of the cache folder. If I have issues, I zip up all the contents of the cache folder as backup and then delete them. Sugar then rebuilds the cache. Don't delete the cache folder itself.

For some reason it isn't currently generating the error log in /var/log/sugarcrm. The error log in the Sugar install is pointing to some Elastisearch errors.

I am unable to get to the admin page to rebuild because the 500 errors kick in right after login. 

I have attempted to delete the cache manually to trigger a rebuild, but from what you've implied that may cause other issues. I have tried using some Repair and Rebuild CLI tools developers have shared, but they have not yet helped.

Did you do all of these?

Adjust the unique_key,

db_user_name,

db_password,

db_name,

site_url,

and host_name settings in the config.php file.

Adjust the RewriteBase setting in the .htaccess file

Can you share the errors that you are seeing in the logs? Are there any errors in the apache log? 

Thank you very much for all your help, Avi. As well as everyone else.

I had changed all those values at the Cloning document recommended. My final issue was due to me having fully deleted the cache file, which was causing some metadata related 500 errors. 

After dropping a fresh copy of the Prod cache into the Sandbox I was able to get in far enough to run the Quick Rebuild and Repair, which fixed a number of issues.

I am currently ensuring that my file structure's permissions are set correctly, and should be able to slowly work through any more smaller errors until I have a pretty good 1:1 representation.

Thanks again!!

Thank you very much for all your help, Avi. As well as everyone else.

I had changed all those values at the Cloning document recommended. My final issue was due to me having fully deleted the cache file, which was causing some metadata related 500 errors. 

After dropping a fresh copy of the Prod cache into the Sandbox I was able to get in far enough to run the Quick Rebuild and Repair, which fixed a number of issues.

I am currently ensuring that my file structure's permissions are set correctly, and should be able to slowly work through any more smaller errors until I have a pretty good 1:1 representation.

Thanks again!!