{"id":9300,"date":"2020-05-30T13:24:07","date_gmt":"2020-05-30T17:24:07","guid":{"rendered":"https:\/\/www.boldgrid.com\/support\/?p=9300"},"modified":"2021-01-28T13:47:02","modified_gmt":"2021-01-28T18:47:02","slug":"troubleshoot-htaccess-problems","status":"publish","type":"post","link":"https:\/\/www.boldgrid.com\/support\/troubleshooting\/troubleshoot-htaccess-problems\/","title":{"rendered":"How to troubleshoot .htaccess problems"},"content":{"rendered":"\n

The .htaccess file can be very useful, however it can also be time consuming and frustrating trying to track down issues within it. The goal of this guide is to provide you with resources to help identify and troubleshoot common .htaccess problems, as well as give a few tips that you can use to help should you run into problems related to this file.<\/p>\n

Note: To avoid having to troubleshoot problems with your .htaccess file by yourself, we recommend using a BoldGrid Official Partner web host for your WordPress hosting<\/a> needs. They are certified WordPress and BoldGrid experts, and can make issues like this go away in a flash. Back to the regularly scheduled article!<\/em><\/p>\n

The .htaccess file<\/h2>\n
The .htaccess file is a configuration file for web servers that run the Apache Web Server Software. When an .htaccess file, or Hypertext Access File, is detected within a web site’s document root, it is then loaded, and any rules in the file are executed. The .htaccess file is extremely useful for making configuration changes to the Apache service that only apply to the directory (and its subdirectories) in which they are added. You can perform redirects, change a sites header, and create SEO Friendly URL’s that exclude the file extension, and add a trailing slash (\/) making the link appear like a folder, rather than a file.<\/p>\n
<\/p>\n
In Linux, any file that begins with a dot (.) is treated as hidden. When a file is hidden it can not been seen with a file browser by default. In most cases, you can view the file browser’s settings, and ensure it is set to allow hidden files to be viewed.<\/div>\n
The most common error that you will see with .htaccess file problems is a 500, or Internal Server Error, as seen below.
\n $\"\"$ <\/a><\/p>\n
<\/p>\n
Common Reasons .htaccess is not working<\/h2>\n
<\/p>\n
Possible Typos<\/h3>\n
If you are replacing, or recreating the file, then you must be sure the filename is correct and that it begins with a period “.” If the period is not at the beginning, Apache will ignore the file – this will occur if it is misspelled as well.<\/p>\n
<\/p>\n
Rule Location<\/h3>\n
Some rules will affect others. If you have added a rule, and it is not working you may want to try and move it above any directives you have already, or even to the top of the file to see if that works. The reason being when .htaccess it read by Apache, it does so from top to bottom, and some rules may be conflicting with what you are attempting to add.<\/p>\n
<\/p>\n
Conflicting .htaccess files<\/h3>\n
An .htaccess file’s rules apply to the directory that it is in, as well as any sub-directories that are within that directory. Because of this, an .htaccess file in a higher level directory can affect your site files as well. An easy way to narrow down whether this is a cause would be to rename the .htaccess file, which will effectively disable it.<\/p>\n
<\/p>\n
Incorrect Syntax<\/h3>\n
The most common issues with .htaccess files are syntax related. Syntax errors in .htaccess will cause 500 errors in Apache. Make sure you check the file to ensure you are using the correct syntax for the directive in question.<\/p>\n
<\/p>\n
You can reference Apaches .htaccess documentation<\/a> for further information.<\/p>\n
How to troubleshoot .htaccess issues<\/h2>\n
<\/p>\n
Use an .htaccess validator<\/h3>\n
You can use tools such as http:\/\/www.htaccesscheck.com\/<\/a> to validate and check your syntax. This is very useful in identifying any errors that may cause problems.<\/p>\n
<\/p>\n
Check Apache Error Logs<\/h3>\n
If you make changes and your site breaks, you can check the Apache error log, which is normally located at \/var\/log\/apache2\/error_log<\/p>\n
<\/p>\n
For example, if I added a . to the bottom of an .htaccess file, and when the site loads, this error can be found within the Apache error log:
\nInvalid command ‘.’, perhaps misspelled or defined by a module not included in the server configuration<\/p>\n
<\/p>\n
Debugging with Apache Configuration<\/h3>\n
If you have access to the httpd.conf file, you can add your .htaccess file inside of a directory tag, and it will allow any errors to be logged, which will point out the issues you may be having quicker.<\/p>\n
<\/p>\n
Here is a sample of the configuration you can use:<\/p>\n
# BEGIN WordPress\r\n \r\n RewriteEngine On\r\n RewriteBase \/\r\n RewriteRule ^index\\.php$ - [L]\r\n RewriteCond %{REQUEST_FILENAME} !-f\r\n RewriteCond %{REQUEST_FILENAME} !-d\r\n RewriteRule . \/index.php [L]\r\n \r\n# END WordPress\r\n.\r\n<\/pre>\n
<\/p>\n
The Apache error log would then point directly to the line that has the error, helping troubleshooting by pointing to the exact location of the issue. In this case, it would be a stray “.” at the end of the file which could easily be overlooked.<\/p>\n
<\/p>\n
Enable Mod_Rewrite Logs<\/h3>\n
If you’re using Apache’s mod_rewrite module, you can enable the rewrite log to give you details about any issues you may have. To accomplish this, you will need access to the Apache configuration file.<\/p>\n
<\/p>\n
You can find out more about enabling this log in the Apache documentation<\/a><\/p>\n
<\/p>\n
There is a direct correlation between the trace log level you define, and the speed of Apache’s response. The larger the number is, that you use for trace logs, the slower your sites will load. Because of this, it is recommended to keep this disabled unless troubleshooting a specific issue.<\/div>\n
<\/p>\n
404 Errors \/ Permalink Settings<\/h3>\n
One of the most common errors when dealing with WordPress Permalink problems is a Server Level 404 Error. This is fixed by either adding back the permalink rewrites in .htaccess, or navigating to Settings > Permalinks and clicking save.<\/p>\n
<\/p>\n
Not Generated During Inspirations<\/h3>\n
If your .htaccess file is not automatically generated during Inspirations, then there is likely an issue with your file permissions, or your web server’s Apache configuration.<\/p>\n
Default WordPress .htaccess<\/h2>\n
There are multiple configurations for permalinks, as you have the option to change or customize them to suit your needs. Here are the default .htaccess files for WordPress single and multisite uses:<\/p>\n
<\/p>\n
WordPress Single Site:<\/h3>\n
# BEGIN WordPress\r\n\r\nRewriteEngine On\r\nRewriteBase \/\r\nRewriteRule ^index\\.php$ - [L]\r\nRewriteCond %{REQUEST_FILENAME} !-f\r\nRewriteCond %{REQUEST_FILENAME} !-d\r\nRewriteRule . \/index.php [L]\r\n\r\n# END WordPress<\/pre>\n
<\/p>\n
WordPress Multisite<\/h3>\n
Subfolder Example<\/h4>\n
RewriteEngine On\r\nRewriteBase \/\r\nRewriteRule ^index\\.php$ - [L]\r\n\r\n# add a trailing slash to \/wp-admin\r\nRewriteRule ^([_0-9a-zA-Z-]+\/)?wp-admin$ $1wp-admin\/ [R=301,L]\r\n\r\nRewriteCond %{REQUEST_FILENAME} -f [OR]\r\nRewriteCond %{REQUEST_FILENAME} -d\r\nRewriteRule ^ - [L]\r\nRewriteRule ^([_0-9a-zA-Z-]+\/)?(wp-(content|admin|includes).) $2 [L]\r\nRewriteRule ^([_0-9a-zA-Z-]+\/)?(.\\.php)$ $2 [L]\r\nRewriteRule . index.php [L]\r\n<\/pre>\n
<\/p>\n
SubDomain Example<\/h4>\n
RewriteEngine On\r\nRewriteBase \/\r\nRewriteRule ^index\\.php$ - [L]\r\n\r\n# add a trailing slash to \/wp-admin\r\nRewriteRule ^wp-admin$ wp-admin\/ [R=301,L]\r\n\r\nRewriteCond %{REQUEST_FILENAME} -f [OR]\r\nRewriteCond %{REQUEST_FILENAME} -d\r\nRewriteRule ^ - [L]\r\nRewriteRule ^(wp-(content|admin|includes).) $1 [L]\r\nRewriteRule ^(.\\.php)$ $1 [L]\r\nRewriteRule . index.php [L]\r\n<\/pre>\n
<\/p>\n
.htaccess rules for NGINX<\/h3>\n
Since NGINX does not use an .htaccess file, you would have to apply your rewrites directly to the configuration. To accomplish this, you can use a converter tool, such as https:\/\/winginx.com\/en\/htaccess which will give you the correct syntax to use for NGINX. You would then apply this to your NGINX configuration file.<\/p>\n
<\/p>\n
If you are unsure of how to make these types of changes, or running into issues attempting, then it is recommended to contact your host for additional information.<\/div>\n
<\/p>\n
Congratulations! With the troubleshooting techniques provided, you now have more information as well as some common steps to help solve common .htaccess problems. Looking for more? We have tons of other WordPress tutorials and articles for you to check out!<\/p>\n<\/body><\/html>\n","protected":false},"excerpt":{"rendered":"
The .htaccess file can be very useful, however it can also be time consuming and frustrating trying to track down issues within it. The goal of this guide is to provide you with resources to help identify and troubleshoot common .htaccess problems, as well as give a few tips that you can use to help […]<\/p>\n","protected":false},"author":529,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"bgseo_title":"How to troubleshoot .htaccess problems - BoldGrid","bgseo_description":"The goal of this guide is to provide you with resources and common practices to help identify and troubleshoot .htaccess problems.","bgseo_robots_index":"index","bgseo_robots_follow":"follow","footnotes":""},"categories":[74],"tags":[],"class_list":["post-9300","post","type-post","status-publish","format-standard","hentry","category-troubleshooting"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/9300","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/users\/529"}],"replies":[{"embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/comments?post=9300"}],"version-history":[{"count":13,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/9300\/revisions"}],"predecessor-version":[{"id":33339,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/posts\/9300\/revisions\/33339"}],"wp:attachment":[{"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/media?parent=9300"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/categories?post=9300"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.boldgrid.com\/support\/wp-json\/wp\/v2\/tags?post=9300"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}