Common Website Errors¶

Use this page to troubleshoot common website errors. Note the affected URL, exact error, and recent site or DNS changes before making adjustments.

Quick Reference¶

Resource And Capacity Errors¶

PHP Limits And Code Errors¶

Server Configuration And Security Errors¶

Related Email Errors¶

Adjusting PHP Settings In cPanel¶

Most Fused users should adjust PHP from cPanel first. Depending on the account and PHP handler, the relevant area may be named MultiPHP INI Editor, Select PHP Version, PHP Selector, or Manage PHP Settings.

Review the full PHP settings guide

Use the PHP settings guide for:

• Changing the PHP version.
• Increasing memory_limit.
• Increasing upload_max_filesize and post_max_size.
• Increasing max_execution_time.
• Increasing max_input_vars.
• Reviewing disable_functions.

Resource And Capacity Errors¶

CloudLinux LVE Resource Limits¶

Fused servers may use CloudLinux LVE limits to keep one account from consuming resources needed by other sites on the same server. These limits are not only about disk space or bandwidth. They can involve CPU, memory, disk throughput, disk operations, concurrent web requests, or total processes.

Fused automatically adjusts resources in many normal growth situations, such as legitimate increases in traffic. Some cases still justify upgrading the hosting account, especially when the site consistently needs more CPU, memory, IO, or concurrency than the current service is designed to provide.

Common LVE Symptoms¶

LVE Limit Names¶

What To Do First¶

1. Log in to cPanel.
2. Open Resource Usage, CPU and Concurrent Connection Usage, or a similarly named CloudLinux resource page.
3. Check whether the account recently hit CPU, Memory, IO, IOPS, EP, or NPROC.
4. Note the time window and compare it to traffic, imports, backups, cron jobs, plugin updates, or marketing campaigns.
5. Check error_log for PHP errors that might explain the spike.

Common Fixes¶

Try the fix that matches the pattern:

• Traffic spike: confirm whether the traffic is legitimate, then contact Fused if the account needs more headroom.
• Bot traffic: add caching, review security rules, and contact Fused with the affected URL and time window.
• Slow PHP pages: check plugins, themes, database queries, and PHP errors.
• Imports or backups: run them during quieter periods, increase PHP limits where appropriate, or use a safer backup/import method.
• Repeated WooCommerce, membership, or booking spikes: consider whether the account has outgrown the current service level.

507 Insufficient Storage¶

A 507 Insufficient Storage response usually means the server or account could not complete the request because storage or a related resource was exhausted. For hosting accounts, start with disk usage and then review CloudLinux resource usage if disk space looks normal.

Check Disk And Resource Usage¶

1. Log in to cPanel.
2. Check account disk usage.
3. Remove unneeded backups, old archives, cache files, or abandoned staging copies if the account is full.
4. Check Resource Usage for memory, IO, IOPS, EP, or process faults around the same time.
5. Contact Fused if the account is not full or the error repeats.

Server Configuration And Security Errors¶

500 Internal Server Error¶

A 500 error usually means the server could not complete the request because of a configuration or application problem.

Example:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to
complete your request.

Check File And Folder Permissions¶

Incorrect permissions can cause 500 errors.

Avoid setting files or folders to 777. If you are not sure what permissions should be, contact Fused before changing large parts of the account.

Check .htaccess¶

Invalid .htaccess rules can also cause 500 errors. Common causes include:

• Old php_flag or php_value directives.
• Rewrite rules copied from another host.
• Rules added by plugins or applications.
• Redirect loops.

If .htaccess contains PHP settings, move those settings into the appropriate PHP configuration tool instead. See changing PHP settings.

Check error_log¶

Look for an error_log file in the same folder as the affected site or script. The newest lines usually identify the file, line number, or setting causing the problem.

406 Not Acceptable¶

A 406 Not Acceptable response usually means a security rule blocked the request. This can happen when a request resembles an exploit attempt, even if the action was legitimate.

Contact Fused and include:

• The affected URL.
• The exact time of the request.
• Your IP address if available.
• The form, upload, or action that triggered the error.

PHP Limits And Code Errors¶

Fatal Error: Allowed Memory Size Exhausted¶

This error means PHP ran out of memory while processing a request.

Example:

Fatal error: Allowed memory size of 67108864 bytes exhausted

Increase PHP Memory In cPanel¶

1. Log in to cPanel.
2. Open MultiPHP INI Editor, PHP Selector, or Manage PHP Settings.
3. Select the affected domain.
4. Increase memory_limit.
5. Save the change.
6. Test the page again.

Start with a modest increase, such as 128M or 256M, then test. If the site needs unusually high memory, a plugin, theme, import, or custom script may need review.

Increase PHP Memory With php.ini¶

If you manage PHP settings with a php.ini file, add or update:

memory_limit = 256M

Uploaded File Exceeds upload_max_filesize¶

This error means the uploaded file is larger than PHP allows.

Increase Upload Limits In cPanel¶

1. Log in to cPanel.
2. Open MultiPHP INI Editor, PHP Selector, or Manage PHP Settings.
3. Select the affected domain.
4. Increase upload_max_filesize.
5. Increase post_max_size to the same value or higher.
6. Save the change.
7. Retry the upload.

Increase both upload and post limits:

upload_max_filesize = 64M
post_max_size = 64M

post_max_size should be equal to or larger than upload_max_filesize. After changing the values, retry the upload.

Maximum Execution Time Exceeded¶

This error means a PHP request ran longer than the configured limit.

Example:

Fatal error: Maximum execution time of 30 seconds exceeded

Increase Execution Time In cPanel¶

1. Log in to cPanel.
2. Open MultiPHP INI Editor, PHP Selector, or Manage PHP Settings.
3. Select the affected domain.
4. Increase max_execution_time.
5. Save the change.
6. Retry the action.

For imports, exports, backups, or plugin actions, try a moderate value such as 120 or 300. If a normal page needs a much higher value, the application may need review.

If you manage PHP settings with a php.ini file, add or update:

max_execution_time = 300

max_input_vars Limit Reached¶

This usually appears when a large form, menu, page builder, translation plugin, or settings screen submits more fields than PHP accepts.

Example:

Input variables exceeded 1000

Increase Input Variables In cPanel¶

1. Log in to cPanel.
2. Open MultiPHP INI Editor, PHP Selector, or Manage PHP Settings.
3. Select the affected domain.
4. Increase max_input_vars.
5. Save the change.
6. Retry the form or settings save.

Common values are 2000, 3000, or 5000. If the setting is not shown in Basic Mode, use the editor mode or contact Fused.

If you manage PHP settings with a php.ini file, add or update:

max_input_vars = 3000

Cannot Modify Header Information¶

This warning usually means PHP sent output before it tried to modify headers.

Example:

Warning: Cannot modify header information - headers already sent by
(output started at /home/user/public_html/config.php:40)
in /home/user/public_html/index.php on line 6

Check the file and line referenced after output started at. Common causes include:

• Blank lines before <?php.
• Extra whitespace after a closing ?>.
• Accidental output from debugging code.
• Plugin or theme code sending output too early.

If you cannot find the source, contact Fused with the full warning text.

exec() Disabled For Security Reasons¶

Some PHP functions are disabled by default because they can create security risk.

Example:

Warning: exec() has been disabled for security reasons in
/home/username/public_html/script.php on line 5

Before enabling a disabled function, confirm the application truly needs it and that the script is trusted.

Review Disabled Functions¶

1. Log in to cPanel.
2. Open MultiPHP INI Editor, PHP Selector, or Manage PHP Settings.
3. Select the affected domain.
4. Review the disable_functions value.
5. Remove only the specific function the trusted script requires.
6. Save the change.
7. Test the script.

Avoid clearing the whole disable_functions list unless you understand the security impact.

When To Contact Fused¶

Contact Fused if:

• The site is down and you are not sure which change caused it.
• The error started after a server, PHP, plugin, or theme change.
• You see a 406 error.
• You need help interpreting error_log.
• Reverting your change does not restore the site.