Internal server error [500]

[Lala]

Hi

I have installed the latest nuBuilder onto a website, but when I try to login I get an internal server error [500]. Can you give me some advice please?

[kev1n]

A 500 Internal Server Error when trying to log into a fresh installation of nuBuilder Forte usually means something has gone wrong on the server-side—typically a PHP or database error. Here's a checklist and some debugging steps to help you find and fix the issue:

1. Check That nuBuilder Tables Were Created

Ensure the database contains nuBuilder system tables, typically prefixed with zzzzsys.

Code: Select all

zzzzsys_access  
zzzzsys_access_form  
zzzzsys_access_php  
zzzzsys_access_report  
zzzzsys_browse  
zzzzsys_debug  
zzzzsys_event  
zzzzsys_file  
zzzzsys_form  
zzzzsys_format  
zzzzsys_object  
zzzzsys_php  
zzzzsys_report  
zzzzsys_select  
zzzzsys_select_clause  
zzzzsys_session  
zzzzsys_setup  
zzzzsys_tab  
zzzzsys_timezone  
zzzzsys_translate  
zzzzsys_user  
zzzzsys_cloner  
zzzzsys_code_snippet  
zzzzsys_note  
zzzzsys_email_template  
zzzzsys_note_category  
zzzzsys_info  
zzzzsys_config  
zzzzsys_user_permission  
zzzzsys_permission_item  
zzzzsys_email_log  
zzzzsys_prompt_generator  
zzzzsys_item  

Note: If these tables are missing or incomplete, it's possible something went wrong during the installation or update process, and some tables were not created.


2. Enable Error Reporting (To See What the 500 Error Actually Is)

Edit php.ini, .htaccess, or your index.php file (temporarily) to show errors:

In php.ini:

Code: Select all

display_errors = On
error_reporting = E_ALL

Or in .htaccess (inside your nuBuilder folder):

Code: Select all

php_flag display_errors on
php_value error_reporting 32767

Or add to the top of index.php:

Code: Select all

ini_set('display_errors', 1);
error_reporting(E_ALL);

in nucommon.php, replace error_reporting(error_reporting() & ~E_NOTICE); with

Code: Select all

ini_set('display_errors', 1);
error_reporting(E_ALL);

Then reload the login page — this should display a specific error message instead of just a 500.

3. Check error_log or Web Server Logs

Apache: /var/log/apache2/error.log
Nginx + PHP-FPM: /var/log/php*/fpm.log or /var/log/nginx/error.log

Shared hosting: Check your control panel for error_log

You're looking for Fatal errors, Database connection issues, or missing files/classes.

4. Check for Errors in zzzzsys_debug Table**

Open **phpMyAdmin**, go to the `zzzzsys_debug` table, and review recent entries for any error messages or failed SQL operations.

5. An update can fail or cause issues if:

Core nuBuilder tables (e.g. zzzzsys_*) have been manually modified, such as adding or altering columns.
The update process was interrupted, incomplete, or ran into errors (e.g. timeout, missing privileges, file permission issues).

Next Steps

Meanwhile, Restore the Database from a Backup
If you're unsure what went wrong or need to get the system back online quickly, restore the database from a known good backup while you continue troubleshooting the issue.

Once you reveal the specific error using step 2, 3 or 4, paste it here.

[Lala]

Hi Kevin

Thanks for your help. I didn't get anywhere with your steps to sort it out, so as it is a new database I deleted it from Hostinger, deleted all the nubuilder files from my domain/website and started again. All good now! I don't know what I would have done in this whole journey without you and your team - thank you so much.