input license here

Common errors on directadmin and how to fix them




During use, users often encounter errors on Directadmin. In the following article, BKNS will send to you common errors on directadmin and how to fix it for your reference. Let's follow up now.


Common errors on directadmin


1. Invalid login


Invalid login

Invalid login


Occasionally users will encounter invalid login error while using Directadmin even though username and password are not wrong. This error is caused because you used google translate. To fix this error, you need to remove the translate function according to the following steps:


Step 1: Proceed to login on another browser.


Step 2: Click the menu icon in the upper right corner of chrome. Then select settings, then select Show advanced settings. On this window, uncheck the box Offer to translate pages that aren't in a language you read.


Step 3: Perform login again.


2. Lỗi “This is a placeholder for the subdomain… demo.domain.com”


This error appears on DirectAdmin when a user creates a subdomain.


You take the following steps to fix the error:


Step 1: In domain.com, go to public_html.


Step 2: The demo folder appears on the screen. Including the file index.html


Step 3: You can delete the index.html file


Note: you need to upload the code in this section for the subdomain to run normally.


3. Lỗi “mod_fcgid: can’t apply process slot for”


When you use directadmin that sees the message mod_fcgid: can't apply process slot for, you need to do the following steps to fix it.


In case you use Hosting, you need to check if you have configured correctly. If you still see an error, you need to contact your hosting provider to ask if CGI Access is enabled on the host. If you use VPS, you need to adjust the MaxProcessCount parameter located in /usr/local/apache/conf/php.conf.


Code:


# Fastcgi configuration for PHP5

LoadModule fcgid_module modules/mod_fcgid.so

MaxRequestsPerProcess 500

MaxProcessCount 3

MaxRequestLen 33554432

IPCCommTimeout 60

IdleTimeout 120

IdleScanInterval 30

BusyTimeout 120

BusyScanInterval 90

ErrorScanInterval 3

ZombieScanInterval 3

ProcessLifeTime 3600

If it still doesn't work, try delegating 775 for FastCGI login


4. Lỗi No input file specified


Lỗi No input file specified

Lỗi No input file specified


This is the error caused by apache. To fix the error, refer to the following 3 ways:


Way 1: Go to file .htaccess add ? after index.php before "/"


for example the following code:


PHP:

RewriteEngine On

RewriteCond %{REQUEST_URI} ^/system.*

RewriteRule ^(.*)$ index.php?/$1 [L]

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule ^(.+)$ index.php?/$1 [L] 

Method 2: Maybe in the process of adding the domain there is an error. So try deleting the domain and adding it again.


Method 3: In case you cannot edit the .htaccess file, you can follow these 2 steps:


Step 1:


PHP runs in CGI mode when cgi.fix_pathinfo is set to 1. Open /system/application/config/config.php or where the config file is located and make sure these two options are set.


PHP:

$config['index_page'] = “”;

$config[‘uri_protocol’] = “AUTO“; 

Step 2:


Create a PHP.INI file under your website root directory with the content


PHP:

cgi.fix_pathinfo = 0;

5. Lỗi Nginx is functioning normally


Lỗi Nginx is functioning normally

Lỗi Nginx is functioning normally


During use, you will occasionally encounter Nginx is functioning normally. Fix it in the following ways:



  • If this error appears due to not assigning IP to the correct domain, you need to reassign the IP to the correct domain to fix the error.

  • When you just point the domain name to the hosting without adding the domain on the hosting or creating a domain on the VPS/Server is also a cause of the error. Nginx is functioning normally. So you need to add hosting to solve the error.

  • If the above 2 methods still do not make the error disappear, you need to contact your hosting provider for support.


6. Lỗi An error occurred while creating the compressed file


The cause of this error is that you try to compress the file above DirectAdmin but using too much storage space. To handle this error, you need to delete unnecessary files to free up space on your hosting or increase your hosting capacity by contacting your hosting provider to buy more space. You can use one of these two ways, but make sure the free space is larger than the size of the file you compress.


So the above article, BKNS sent to you common errors on directadmin and how to fix it. Hope the above article is useful to you. If you have any other questions, please leave a comment below for immediate support. Also follow the website https://www.bkns.vn/ Read more useful articles.


Related Posts
Diệp Quân
Nguyen Manh Cuong is the author and founder of the vmwareplayerfree blog. With over 14 years of experience in Online Marketing, he now runs a number of successful websites, and occasionally shares his experience & knowledge on this blog.
SHARE

Related Posts

Subscribe to get free updates

Post a Comment

Sticky