Fix 500 error on web hosting

Fix 500 error on web hosting

Theerror 500 Internal Server Error indicates a server-side problem on your web hosting Anthony IT Solutions : PHP, .htaccess, permissions or disk quota. This guide structure the diagnosis step by step.

Unlike a 404 (page missing), the 500 masks the exact cause to visitors. The server and PHP logs reveal the exact error message.

What you need

• Website in error 500 on web hosting
• Access panel and logs
• SFTP to rename files
• Recent backup, guard save

Identify context

1. Global or partial

   The entire site or a specific URL (admin, API)?

2. After which

   Update plugin, change .htaccess, migration?

3. Front vs admin

   Admin OK but front KO → theme or cache.

4. Sub-domain

   One affected vhost → local config.

View logs

1. Logs panel

   Guide logs : error.log PHP and Apache/LiteSpeed.

2. Time stamping

   Reproduce the error and refresh the logs.

3. Fatal error

   Search PHP Fatal error, Allowed memory size, Parse error.

4. Enable display_errors

   Temporarily in dev via php.ini or .user.ini, never in prolonged production.

Check .htaccess

1. Rename

   Rename .htaccess in .htaccess.off, if the site returns, the syntax is involved.

2. Restore backup

   Copy .htaccess.bak or regenerate from WordPress permaliens.

3. Invalid guidelines

   Requires, RewriteRule badly closed, guide htaccess.

4. Progressive test

   Reintroduce the rules into blocks.

WordPress : troubleshooting mode

1. Plugins

   Rename wp-content/plugins in plugins.off via SFTP.

2. Theme

   Activate a default theme by renameing your active theme.

3. wp-config.php

   Check DB_*; add WP_DEBUG_LOG true in wp-content/debug.log.

4. Memory limit

   definition('WP_MEMORY_LIMIT', '256M');

Quota, PHP and permissions

• Record the log's exact message
• Start time and recent actions
• Contact support Anthony IT Solutions with domain and log capture
• Restore backup panel if corruption base

1. Disk space

   Quotas, full disk = 500.

2. PHP version

   Change PHP if incompatible after MAJ CMS.

3. Permissions

   644 files, 755 folders; no 777.

4. Ownership

   Uploaded files with poor SFTP owner.

Troubleshooting

• Parse error, modified PHP file with invalid syntax.
• Memory enhanced, Increase memory_limit or optimize plugin.
• Max execution time, Script blocked; cron or import.
• Still 500, Contact support with error.log extract.

Frequently Asked Questions

500 without admin access?
SFTP: Rename plugins and theme.

Empty logs?
Wait 1-2 min; check good domain/vhost.

After migration?
BDD and .htaccess identifiers, migration.

Prevention ?
Sauvages, staging, progressive MAJ.

Related guides

• Logs
• .htaccess
• Quotas
• PHP version

See also our web hosting offer and all the procedures on wiki web hosting.