Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

406 error in Drupal – How to fix it

by | Apr 20, 2021

A 406 error in Drupal can trigger due to a number of reasons which include disabling XML-RPC, security restrictions, etc.

As a part of our Server Management Services, our Support Engineers helps webmasters and website owners to fix similar Drupal-related errors regularly.

Today, let us discuss the possible reasons for this error and how we tackle it.

Causes and Fixes for 406 error in Drupal

Often while changing the admin/settings page  or while using the Drupal login module, users receive an error as shown below:

This error can trigger due to a number of reasons. Let us now discuss some top reasons for this error and how our Support Engineers fix it.

Using XMLRPC

To fix the security holes with older versions of XMLRPC libraries, some hosting providers may disable xmlrpc.php scripts. While we enable the BlogAPI module or the Drupal login module on such a provider,  our Support Engineers notices “406 errors”.

A possible solution here that we follow is to rename the xmlrpc.php file in drupal’s main directory. We will then alter blogapi.module to point to the newly renamed file, as well as any other modules that point to xmlrpc.php.

Special characters in the folder name

At times, the 406 error may trigger due to characters like “/” in the folder name. For instance, our Support Engineers have noticed this error when the field for the temporary directory was set as “/tmp”. The leading slash here was creating some chaos in the headers passed from the apache to the browser.

We can fix the error in such cases by changing the folder name to one without the slash character

Drupal 406 error due to security settings

The security settings at the server-side may also trigger the 406 error at times. Often our Support Engineers are able to fix this error by adding the following line to the .htaccess file.

SecFilterEngine Off

[Need any further assistance in fixing Disk space errors? – We’re available 24*7]

Conclusion

In short, the Drupal 406 error can trigger due to number of reasons. Today,  we saw how our Support Engineers tackle this error.

Are you using Docker based apps?

There are proven ways to get even more out of your Docker containers! Let us help you.

Spend your time in growing business and we will take care of Docker Infrastructure for you.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF