How to fix 500 Internal Server Error after editing .htaccess

A 500 error right after editing .htaccess almost always points to a syntax issue, unsupported directive, or conflicting rewrite logic in the file.

Common symptoms

• The site fails immediately after a redirect change
• Admin and frontend both show 500
• Removing one rule appears to restore access

Troubleshooting steps

1. Rename the current .htaccess file temporarily to confirm it is the source of the error.
2. Restore the last known working version or rebuild the file using the application's default rules.
3. Add custom directives back one section at a time until the breaking rule is identified.
4. Check for unsupported directives that require modules not available in your hosting environment.
5. Be careful with copy-pasted rules from other servers that assume different software stacks.

Additional notes

• A malformed rewrite flag or missing condition can be enough to trigger 500 errors.
• Keeping a backup of .htaccess before edits dramatically shortens recovery time.

When to contact support

Contact support if a minimal known-good ruleset still triggers a 500 error.