DirectAdmin

To check the partition on our server, need to run the following commands. df -h The result would depend on what kind of partition we used on the server. If the server having an /home partition, then your quota_partition value will be /home. If it was not, then it will be /, so your quota partition will likely be /. In some cases, you might have a symbolic link like: /home –> /usr/home. In such cases, your quota will be same as above /usr. Set the partition value here, as needed: /home To check how much space is consumed by the system, DirectAdmin will run the following: /usr/sbin/repquota /home NOTE: repquota is a command used to print the overall summary of the server disk usage and quotas for the specified file system. Where /home is the quota_partition value being set in the /usr/local/directadmin/conf/directadmin.conf file. (Just like above examples: /home, / or /usr ). Then it will return the result with a list of numbers, example: /usr/sbin/repquota /home *** Report for user quotas on device /dev/hda3 Block grace time: 7days; Inode grace time: 7days Block limits                File limits User            used    soft    hard  grace    used  soft  hard  grace ———————————————————————- root      —  417796       0       0           7446     0     0 nobody    —       4       0       0              1     0     0 bin       —   56880       0       0            510     0     0 majordomo —       8       0       0              2     0     0 diradmin  —       8       0       0              2     0     0 admin     —     200       0       0             44     0     0 user123   —     100       0       0             22     0     0 user456   —     100       0       0             22     0     0 If the second column ” used ” is not showing anything or users are not in the list. Then we can run the following quotacheck command. On Redhat:  /sbin/quotaoff -a; /sbin/quotacheck -avugm; /sbin/quotaon -a; FreeBSD: /usr/sbin/quotaoff -a; /sbin/quotacheck -avug; /usr/sbin/quotaon -a; If the repquota throwing errors then we need to check in deeply this with the filesystem /etc/fstab file, it will be created automatically once the OS is installed. Whenever changes happen on the filesystem it will be modified automatically. To check with this, need to ensure that it contains rw, userquota, groupquota line beside the partition that is using the quotas. For an example: # Device                Mountpoint      FStype  Options            Dump    Pass# /dev/ad0s1a             /home           ext3     rw,usrquota,grpquota 1       1 /dev/ad0s1e             /tmp            ext3     rw                 2       2 proc                    /proc           procfs   rw                 0       0   In this case, the quota_partition is /home based on server configuration. Maybe it will / or /usr in your system. Or if it was shows, you may consider switching to journaled quota to avoid running quotacheck after an unclean shutdown: In that case, instead of “,usrquota,rpquota”, add “,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0” to your fstab file. Once the repquota program is returning a normal value, then you can run the tally to get the correct usage to show up in DirectAdmin: echo “action=tally&value=all” >> /usr/local/directadmin/data/task.queue This task.queue command will get picked up by the dataskq binary.   It calls the repquota command and dumps it into /home/tmp/quota-dump. Check /var/log/directadmin/errortaskq.log for any errors with this. Running the tally manually for a User can also help with debugging these issues.   If you need any further help, please do reach our support department.

As we all know that what is an IP address?. It is nothing but a logical numeric address that is assigned to each and every single computer, printer, switch, router, mobiles or any other device that is part of a TCP/IP-based network. An IP address is the most significant and important component in the networking phenomena that binds the World Wide Web (www) together. Direct Admin also supports IPv6 address from the version 1.37.0 onwards. Let’s look into how we can use IPb6 address in Direct Admin.   To Add IPv6 Address This is the first step. In order to use IPv6, we have to tell the Direct Admin that we need to use IPv6 address instead of IPv4. 1) Login to the server via ssh as the root user. 2) Open the DirectAdmin configuration file vi /usr/local/directadmin/conf/directadmin.conf 3) Find the ipv6 from the above configuration file. Then edit it as to 1 if it is mentioned as zero. Ipv6=1 3) Save the configuration file. 4) Then the very next step is to restart the service for the same. Execute the below command. service directadmin restart You can also add this by from the front end. 1) Login to the DirectAdmin panel using username and password. 2) Adding the IP address to DirectAdmin is done the same way as with we adding the IPv4 address. Select Admin Tools >> IP management. You can add the IPv6 address on the IP filed. Please be noted that the netmask 255.255.255.0 can only apply to an IPv4 address and should be ignored while adding an IPv6 address to the DirectAdmin. By default, the netmask of the IPv6 address is /64. But it is not yet supported. So that whenever we are adding the IPv6 address to the DirectAdmin, we need to use the full or short forms of the address. As we are giving in short forms of the address, the DirectAdmin will expand it to the full form of the IPv6 values. And please note that don’t give or use  around the IP address here. It is just fine with 1:2::9 Now the DNS system is ready for IPv6. We have dns_a.conf file and dns_aaaa.conf file default records for newly created zones. Each of these template files will check on the IP type. When an IP is sent to the template, the IP type is also included, so the template can choose to ignore adding any records if the IP type doesn’t match its format, or (with customization) you can add some other value if you’d like. For most people, leaving it alone will be best. How to Access the DirectAdmin via IPv6 address. 1) Login to the server via ssh as the root user. 2) Execute the following commands. /sbin/sysctl net.inet6.ip6.v6only=0 3) Set this in the /etc/rc.conf: ipv6_ipv4mapping=”YES” 4) Then verify with the sockstat command. If it is working correctly, It will give an output as follows. freebsd7-64# sockstat -l | grep direct | head -n1 nobody   directadmi 50362 0  tcp46  *:2222                *:* Otherwise, freebsd7-64# sockstat -l | grep direct | head -n1 nobody   directadmi 50362 0  tcp6  *:2222                *:* We have to get tcp46 in the output. If it is not, this means that the IPv6 is not enabled. 5) DirectAdmin should be restarted after this option is set. For the apache service, it already supports IPv6. So that no need of changes here. But we have to modify the exim and dovecot. Exim does not support IPv6. So we need to ensure it is compiled in. 6) Run the following command. /usr/sbin/exim -bV | grep Support Then you will get an output like as follows. Support for: crypteq IPv6 Perl OpenSSL move_frozen_messages Content_Scanning Old_Demime DKIM DNSSEC Event OCSP PRDR 7) If you are not seeing IPv6 in the output, then you’ll need to recompile exim, either using rpms, or from the source.  The latest Makefiles should have the required HAVE_IPV6=YES to ensure it’s included. 8) For the dovecot, edit the configuration file to the IPv6 support format. vi /etc/dovecot.conf 9) Find out the following line. #IPv4 listen = * #IPv4 and IPv6: #listen = *, :: 10) Change them to look like below. #IPv4 #listen = * #IPv4 and IPv6: listen = *, :: 11) Then restart the dovecot. service dovecot restart 12) For the older versions of dovecot vi /etc/dovecot.conf Add the following line. listen = “*, [::]”   If you need any further help, please do reach our support department.

cPanel is one of the most common and widely used control panels. But cPanel has recently announced a massive increase in their pricing scheme. This increase in the price schema has impacted so many customers and businesses. So, customers are now migrating their cPanel sites to other control panels, and some of them are migrating their cPanel sites to DirectAdmin. With the recent inrush of cPanel to DirectAdmin migration, there is a confusion in the access of PhpMyAdmin and RoundCube. In DirectAdmin, the PhpMyAdmin and RoundCube require login credentials. With cPanel, the users grant access to all the tables created under the cPanel user. The one-click feature within the cPanel interface helps an end-user to log into the PhpMyAdmin and RoundCube automatically. When clients migrate from cPanel to DirectAdmin, they get confused with the DirectAdmin credentials and the credentials for the PhpMyAdmin and RoundCube. To log in to the PhpMyAdmin, they need to input the database user name and password and in case of the RoundCube, they need to input the user’s email address and password. The SingleSignOn feature of the DirectAdmin can help the user to automatically log into the PhpMyAdmin and RoundCube with a single click via the DirectAdmin interface. Since October 2019, the Single SignOn feature of DirectAdmin is disabled by default. In this knowledge base, we will learn how to enable the one-click login or auto-login feature for PhpMyAdmin and RoundCube via the DirectAdmin interface. Steps to Enable One-Click Login for PhpMyAdmin from DirectAdmin To enable the one-click login for PhpMyAdmin in the DirectAdmin interface, follow these steps. First of all, Log in to the DirectAdmin server as a root user. Then, Switch to the ‘directadmin’ directory by executing the following command. # cd /usr/local/directadmin/ Run the following command to enable the one-click login for PHPMyAdmin. # ./directadmin set one_click_pma_login 1 After that, restart the DirectAdmin service by using the following command. # service directadmin restart Then, switch to the ‘custombuild’ directory. # cd custombuild After that, execute the following command to update the build. # ./build update Finally, Run the following command to make all the changes reflect in the DirectAdmin panel. # ./build phpmyadmin After enabling the one-click login feature of PhpMyAdmin, you can log in to the PhpMyAdmin from DirectAdmin panel without entering the login credentials as such of cPanel. To test, follow these steps: Log in to the DirectAdmin interface as a root user. Go to the ‘Account Manager’ option and select the ‘MYSQL Management’ from the drop-down. Then, select the database name from the list to which you want to login. Click the ‘Login’ button far right to the database to login to the PhpMyAdmin without entering the login credentials. To make PhpMyAdmin only accessible with the Single SignOn feature and not with the database user name and password, follow the steps given below. Log in to the DirectAdmin server as a root user. Switch to the ‘custombuild’ directory by using the following command. # cd /usr/local/directadmin/custombuild Then, update the build script by using the following command. # ./build update After that, disable the public feature of PHPMyAdmin by executing the following command. # ./build set phpmyadmin_public no Execute the following command to make all the changes reflect in the DirectAdmin panel. # ./build phpmyadmin After executing the above commands, when a user will try to log in to the PHPMyAdmin using the database credentials, the system will prompt the following message. Access to phpMyAdmin is only allowed from the control panel. Steps to Enable One-Click Login for RoundCube from DirectAdmin The one-click login is often known as ‘Single SignOn or SSO logins. To enable the one-click login for RoundCube from the DirectAdmin interface, follow these steps: Log in to the DirectAdmin server as a root user. Switch to the ‘directadmin’ directory by using the following command. # cd /usr/local/directadmin/ Then, enable the one-click Webmail login by executing the following command. # ./directadmin set one_click_webmail_login 1 After that, restart the DirectAdmin service by executing the following command. # service directadmin restart Now, switch to the ‘custombuild’ directory. # cd custombuild After that, run the following command to update the build script. # ./build update Then, update changes to the dovecot configuration by executing the following command. # ./build dovecot_conf Execute the following command to update the changes to the EXIM configuration file. # ./build exim_conf Finally, execute the following command to update RoundCube. # ./build roundcube After executing the above commands, follow the below-given steps to avail the Single SignOn feature for RoundCube. Log in to the DirectAdmin interface as a root user. Navigate to ‘Email Manager’ and click the ‘Email Accounts’ option from the drop-down.   Select the email account from the list to which you want to login. Then, click the ‘+’ symbol at the far right of the email account and select the ‘Sign In to Webmail’ option. This time, the system won’t prompt for login credentials and gets redirected directly to the RoundCube account. Please note that this above feature does not get applied to the system accounts, and you need to log in to the system accounts using the DirectAdmin login credentials. The virtual email accounts can only use this feature.

Autodiscover is a system to figure out which settings to use for the POP/IMAP/SMTP settings, that allows the mail client users to configure their email address automatically. We can set up this in DirectAdmin with basic requirement: subdomain and an SRV record. You can add the SRV record on which domain you wish to use these settings for. If you have any global SSL certificate in exim/dovecot for your hostname, it will be better to make sure the clients use the correct value. Hence they did not get SSL certificate errors. Let’s suspect that you are connecting your clients to server.hostname.com with clientdomain.com for both IMAP and SMTP. Then first of all need to create a subdomain called ” autodiscover.hostname.com ” to store the  XML. 1) Need to setup SRV record on the mentioned client domains “clientdomain.com” DNS zone: _autodiscover._tcp.clientdomain.com. 3600 IN SRV 10 10 443 autodiscover.hostname.com. 2) Next, need to create the subdomain autodiscover.hostname.com in Directadmin, then can we add the follwing code into a file called autodiscover.php: <?php //get raw POST data so we can extract the email address $data = file_get_contents(“php://input”); preg_match(“/\<EMailAddress\>(.*?)\<\/EMailAddress\>/”, $data, $matches);   //set Content-Type header(“Content-Type: application/xml”); echo ‘<?xml version=”1.0″ encoding=”utf-8″ ?>’; ?>   <Autodiscover xmlns=”http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006″> <Response xmlns=”http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a”> <Account> <AccountType>email</AccountType> <Action>settings</Action> <Protocol> <Type>IMAP</Type> <Server>server.hostname.com</Server> <Port>993</Port> <DomainRequired>off</DomainRequired> <LoginName><?php echo $matches[1]; ?></LoginName> <SPA>off</SPA> <SSL>on</SSL> <AuthRequired>on</AuthRequired> </Protocol> <Protocol> <Type>POP3</Type> <Server>server.hostname.com</Server> <Port>995</Port> <DomainRequired>off</DomainRequired> <LoginName><?php echo $matches[1]; ?></LoginName> <SPA>off</SPA> <SSL>on</SSL> <AuthRequired>on</AuthRequired> </Protocol> <Protocol> <Type>SMTP</Type> <Server>server.hostname.com</Server> <Port>587</Port> <DomainRequired>off</DomainRequired> <LoginName><?php echo $matches[1]; ?></LoginName> <SPA>off</SPA> <Encryption>TLS</Encryption> <AuthRequired>on</AuthRequired> <UsePOPAuth>off</UsePOPAuth> <SMTPLast>off</SMTPLast> </Protocol> </Account> </Response> </Autodiscover>  SRV record always using port 443 for autodiscover.hostname.com, So make sure you have got a valid certificate setup for this subdomain. You can check this by entering the domain on https://www.sslshopper.com/ssl-checker.html or can try to access it on a browser with https://autodiscover.hostname.com 3) Finally, we will need to set up a .htaccess hidden file so that we can trace any request to the needed subdomain like autodiscover.hostname.com results in the autodiscover.php being called. We need to add the following lines to the .htaccess file under the subdomain DocumentRoot. RewriteEngine On RewriteCond %{REQUEST_FILENAME} -s [OR] RewriteCond %{REQUEST_FILENAME} -l [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^.*$ – [NC,L] RewriteRule ^.*$ autodiscover.php [NC,L]   If you need any further help, please do reach our support department.

We can set up MySQL to be run on an external server when we have a large database that would require management and monitoring of its own. The best way to do so is to host MySQL on a different server. Then we can connect our application to our Remote MySQL database which is pretty simple. This shouldn’t be needed too often, as usual, you can just move all those user accounts to another server to comfort and maintain the load. But in the case of a large database using up the whole server, you don’t have many choices. Set up DA to Use a Remote MySQL Server 1) Firstly, install MySQL on the remote server. DirectAdmin is not required on this server, as it just used to host our MySQL Databases and nothing else. 2) The next move is to create/setup up a user that a DirectAdmin can connect to on the remote MySQL server. Normally the default user for DirectAdmin is da_admin, so the connection with the same name is better but not required. The username and password you have created for the new user must be set in the /usr/local/directadmin/conf/mysql.conf file for DirectAdmin to use. On a side note, if the remote server is on a LAN IP, and the connecting IP to that remote server will not be the same as your server IP, but rather some other IPs. Instead of server IP, you can add an access host by default in the /usr/local/directadmin/conf/mysql.conf file. Add the following line to the file mentioned in the previous paragraph: access_host=x.x.x.x Where x.x.x.x is the IP or host will be the IP address of your remote database server. Please note that the above given method is only for grants da_admin on the “localhost”, meaning you have to already be on that remote MySQL server to use the account. You will need to add another access host or IP to allow the DA server to connect to it. Normally, you just run the GRANT ALL PRIVILEGES ON *.* TO da_admin@localhost command again, but change localhost to the IP of your DA server. Just like this. GRANT ALL PRIVILEGES ON *.* TO da_admin@1.2.3.4 WITH GRANT OPTION; FLUSH PRIVILEGES; We don’t need the “identified by pass” again in this case, because the password is already from adding it the first time. 3) In this instance, the remote MySQL database will be ready and found to accept the DA to use it. You can test this by logging to your DA via SSH and then type: mysql -uda_admin -p --host=x.x.x.x Where x.x.x.x is the IP of your MySQL server. If you are not able to connect, then you must need to check your settings again, also make sure that the MySQL port 3306 is open on the remote box. 4) Then tell DirectAdmin to use the remote server. Edit the configuration file: /usr/local/directadmin/conf/mysql.conf add the line: host=x.x.x.x where x.x.x.x is the IP of your remote server. Make sure there is a newline character at the end of the line. (Eg, press enter) 5) Enter into DA and check the MySQL section of your user level to see if you get any kind of errors related to this. If not, then you can try for adding a database to make sure it works. 6) The only authorize task would then be to fix up phpMyAdmin also connect to the remote host. To do so, Edit /var/www/html/phpMyAdmin/config.inc.php. Then find the following line in the configuration file: $cfg['Servers'][$i]['host']          = 'localhost'; // MySQL hostname or IP address Change it to the following. $cfg['Servers'][$i]['host']          = 'x.x.x.x'; // MySQL hostname or IP address Where x.x.x.x is the IP of your MySQL server. 7) For new MySQL user databases, you will need to tell the DirectAdmin about the new IP, so they have that IP assigned into their access hosts.

After the certificate is issued and sent to you from the Certificate Authority, you can proceed with the certificate installation. Log in to your DirectAdmin panel with User access. Click on SSL Certificates in the Advanced Features section. Tick the ‘Paste a pre-generated certificate and key’ radio button. In the field below, paste your Private Key that was generated along with the CSR code and the certificate that you received from the Certificate Authority right after the RSA key from the new line. If the private key is already filled in, simply copy your certificate including —–BEGIN CERTIFICATE—– and —–END CERTIFICATE—– tags and paste it below the key. Once you have both codes in, click Save. For the certificate to be trusted in all web browsers, you also need to install a CA certificate chain (CA Bundle) you received from the Certificate Authority.You can also download the CA chain file in your account with us or find the appropriate file on this page. To upload a CA bundle file, click on the link ‘Click Here to paste a CA Root Certificate’. Copy all the certificates from the CA bundle file, paste them into the Certificate Authority SSL Certificate field, check the box Use a CA Cert and click Save.   Make sure that the SSL connection is enabled for this domain. The corresponding confirmation is available at the top of the SSL Certificates page. If SSL is disabled, you can click on the link ‘You can enable it here’, check the box Secure SSL and press Save.

To generate the certificate request using DirectAdmin control panel, please follow the steps below: 1. Log in to your DirectAdmin panel. If you are logged as Admin, please choose User Level access in the upper right corner of the screen. 2. Select SSL Certificates from the Advanced Features section. 3. Click on the Create A Certificate Request radio button and fill in the required details. The provided information will be provided in the CSR code to the Certificate Authority. Two-letter Country Code;State/Province;City;Company;Company Division;Common Name – a fully qualified domain name you want to secure with an SSL certificate;E-mail;Key Size (bits), the modern size is 2048 bits least;Certificate Type – the hashing algorithm of the CSR code. Note: The selected hashing algorithm will not influence the issued certificate. Starting from November 6, 2014 all our certificates are issued with SHA-2 hashing algorithm by default. The last two parameters may be lacking, depending on the version of the DirectAdmin panel. After all the details are filled in, click Save at the bottom of the page. 4. After that, DirectAdmin will show the CSR code and the private key. You can use the CSR code to activate your SSL certificate. Please copy it with the header and footer —–BEGIN/END CERTIFICATE REQUEST—–. The private key will be needed for the installation of the issued certificate. Please make sure you backed it up in a separate file because after you close the page, the private key will not be available anymore. If the page shows you only the Certificate request, do not worry – the private key is already copied to the SSL installation page. After you receive the issued certificate, you can use the following guide for the certificate installation.

In order to restore your website with system backup, your website hosting account shall have enough space for –1. temporary backup file, and2. extracted public_htmlApproximately, it shall be double of your current website file size If you are running out of the storage, you may contact us for a temporarily increment of the storage quota (for 3 days) Note: Below procedure may not be applicable to Parallels Site Builder 4.5 or Parallels Web Presence Builder 11.5 [Website Files restoration] Login DirectAdmin Panel (e.g. https://www.YourDomain.com:2222 ) At the top, goto File Manager Goto the folder – /domains/YourDomain.com ,you shall find a folder called public_html ,click on Rename link Rename it as (e.g.) public_html.141117 Goto DirectAdmin panel front page,at the bottom, choose – “Get System Backup” You will see the following, choose a day of backup It will take a few seconds/minute, and create a compressed files at the folder – /backups(If you have MySQL databases, it will also copy MySQL dump file) Then, click the link (as above image), goto /backup folderYou shall see the tar.gz file (and the MySQL dump zip file if have) You may consider to download the tar.gz , and extracted by WinZip to restore individual file if necessary.Below we will illustrate to restore the whole public_html folder In the tar.gz file, click on Extract link It will show the tar.gz archive file content as below,and keep default to extract to /backups folderclick on Extract button Extracted website files to /backups/… You will see there is a folder – domains – under the folder /backups Actually, you will have the following path generated –/backups/domains/YourDomain.com/public_html Now, we need to move the webpage folder (public_html)from /backups/domains/YourDomain.com/public_htmlto /domains/YourDomain.com/public_html Use File Manager,Navigate to /backups/domains/YourDomain.com/You shall see the folder – public_html – as belowselect the public_html folder (at the right hand side)at the bottom, click “Add to Clipboard” Navigate to /domains/YourDomain.com (no /backup)(You shall find the previously renamed folder)At the bottom, click on button – “Move Clipboard files here” Then, you have moved the restored public_html folder. On the right hand side, select the folder – public_htmlAt the bottom, nearby “set Permission”, fill in permission – 711and click on button – “set Permission”(i.e. change the permission from 710 to 711 for Apache web access) We have finished the website file restore. Now, we will goto MySQL database restoration [MySQL restoration] Note: not ALL websites require MySQL database restoration.If you are running CMS (e.g. WordPress, Joomla, Drupal, OpenCart, Magento), or PHP/MySQL application else, you may need to restore MySQL database too. If you do not need to restore MySQL, you may goto the bottom part for clean up section. Use the File Manager, goto /backups folder,and Download the MySQL dump file in zip format to your desktop. Extract it and check how many SQL files inside the ZIP archive. If there are 1 SQL file inside the zip file, it means you have only 1 database.If there are 2 SQL file inside the zip file, it means you have 2 database, and the same. If you have 2 (or more) SQL files inside the ZIP file, please unzip those SQL files, and proceed the following once per database. Goto DirectAdmin panel front pageAt the bottom, goto phpMyAdminYou may login with your MySQL database username/password,or DirectAdmin panel username/password After login phpMyAdmin, you shall see the following list as below –Jot down the number of tables and records for reference (Optional) for clean restoration, you may select all tables, and drop it (i.e. delete ALL table before restore) Confirm to drop the tables? Now, we will import the MySQL dump fileAt the top, choose Import Choose your SQL (or zip) file(Choose zip file if you have only 1 SQL file inside the ZIP) and proceed the import Then, it will import the MySQL dump file (example as below) Check (and compare) the number of tables and records. If the SQL backup file is too large, exceed the phpMyAdmin import limit (around 20MB), you may consider to use this method. Generally, it shall have a small difference of number of records, as the backup shall be yesterday, or a few days ago. Then, the MySQL restore is completed.You shall re-visit and check your website. [Clean Up] If everything OK, you shall clean up the unnecessary files Goto DirectAdmin panel, File Managergoto /domains/YourDomain.com/and remove the old website folder – (e.g.) public_html.141117 Use File Manager, goto /backupsand remove the /domains folder, the tar.gz file, and the zip file. Done.

In this tutorial we will show how to use file manager in direct admin.  You may use file manager in direct admin create,copy, delete, modify, upload and download files/folders …etc.  At first, you need to login to direct admin.  Here are the picture is successful login direct admin.In this page, go to click file managerOnce you are in file manager.  Here are the following picture show you. In this page, you may choose one of your file/folder and select in the select box. At the end of the page, in right hand side, you will see a lot of function button on it. We are going to introduce those button, what they are and what they use. 1. Set PermissionOnce you had selected folders/files, and click set permission button, your folders/files will change the permission.**in our web hosting service, (.php  644), (folder 755)** 2. Add to ClipboardThis button function just like “Copy” function, it will temporary add a files/folders in to Clipboard. 2.1 “Copy Clipboard Files here” “Move Clipboard Files here” “Empty Clipboard”These three button is use for Copy clipboard file in to the other folder.  (it will move the files/folders copy) Move Clipboard Files here. (it will move the original files/folders which you selected) Empty Clipboard (clean the files/folders which you copy, select, or move) 3. Deletethis button is use for delete files/folders which you selected.  **please use it  with care** In Filesystem Tools user usually will useCreate New Folder & Create New File These two button which is use for create new folder and create new file.

To increase the maximum size of a database that can be uploaded in DirectAdmin’s PHPMyAdmin, one must edit the used PHP version’s php.ini to adjust the setting, and then restart the appropriate services. The examples given below apply to a DirectAdmin server using PHP-FPM as the PHP handler. 1) Find the default PHP version’s php.ini You can run the following command to find out what configuration files are in use on your server and what their locations are: PHPMyAdmin on DirectAdmin will use the default PHP version. There may be a blank php.ini section in the output of the command above, but you can ignore that as we just want to know the default PHP version and the location of its php.ini file. 2) Edit the php.ini Now that you can see the location of the default PHP version’s php.ini file, you can now edit it to increase the post_max_size and the max_upload_filesize variables. Using the example in the image above, you could use this command via SSH as root to edit the file: Note that the upload_max_filesize determines the Mib displayed in PHPMyAdmin, but you’ll want to increase both. 3) Restart the webserver and any related services Now you need to restart the webserver and any related services to ensure the changes take place. Apache: If using php-fpm, restart it (replace XX with the appropriate version of PHP, e.g., php-fpm73): 4) Check your work Now you can log into PHPMyAdmin and confirm that the value has been increased as desired by checking under the Import tab.