Archive

How to Change Server Timezone in cPanel/WHM [Closed]

Changing the timezone of a server using cPanel/WHM involves adjusting settings either through the WHM interface or via command line access. Here’s a step-by-step guide to help you through the process.

Method 1: Changing Timezone via WHM

1. Log in to WHM:

• Open your browser and go to the WHM login URL (usually https://your-server-ip:2087).
• Enter your WHM root username and password.

2. Navigate to Server Configuration:

• Once logged in, find the “Server Configuration” section in the left sidebar.
• Click on “Server Time”.

3. Set the Timezone:

• You will see the current time and timezone settings.
• From the “Configure Timezone” drop-down menu, select the desired timezone.
• Click the “Change TimeZone” button to apply the new timezone.

4. Confirm the Changes:

• The system will update the timezone and reflect the new settings in the interface.
• Check the updated server time and timezone to ensure they are correct.

Method 2: Changing Timezone via Command Line

If you have root access to the server, you can change the timezone directly from the command line. This method is often used for more direct control or when WHM is not accessible.

1. Access the Server via SSH:

• Use an SSH client (like PuTTY on Windows or Terminal on macOS/Linux) to connect to your server.
• Log in with your root user credentials.

2. List Available Timezones:

• Run the following command to list available timezones:
  bash
timedatectl list-timezones
• Browse through the list to find your desired timezone (e.g., America/New_York).

3. Set the New Timezone:

• Use the timedatectl command to set the new timezone. For example:
  bash
timedatectl set-timezone America/New_York
• Replace America/New_York with the timezone you want to set.

4. Verify the Change:

• Check the current date and time to confirm the timezone change:
  bash date
• The displayed time should reflect the new timezone settings.

Notes and Considerations

• System Restart: Changing the timezone usually does not require a server restart. However, some applications might need to be restarted to recognize the new timezone settings.
• Effect on Scheduled Tasks: Changing the timezone can affect cron jobs and other scheduled tasks. Review and adjust any schedules if necessary.
• cPanel Account Timezone: Individual cPanel accounts on the server may have timezone settings that can be adjusted through their respective cPanel interfaces. However, these changes are independent of the server’s system timezone.

Summary

• WHM Interface: Quick and user-friendly method for changing the server timezone via the “Server Time” settings.
• Command Line: Provides more control and is useful for servers without WHM access.

If you encounter any issues or need further assistance, feel free to ask for more detailed guidance!

Root Cname in WHM Explained: What You Need to Know [Closed]

It sounds like you need information about setting up a root CNAME record using WHM (Web Host Manager). Let’s break this down:

Understanding CNAME and Root Domain

CNAME (Canonical Name) Record: A type of DNS record that maps an alias name to a true or canonical domain name. For example, blog.example.com could be an alias for example.com.

Root Domain (Apex Domain): The highest level of a domain, such as example.com, as opposed to subdomains like www.example.com or mail.example.com.

Why Root CNAME Records are Special

Typically, a CNAME record should not be used at the root domain level because DNS specifications do not permit a root domain (also known as the zone apex) to have a CNAME. This is because the root domain often needs to have multiple types of records (like SOA, NS, etc.) that can’t coexist with a CNAME.

Alternative Approaches

Since CNAMEs are generally not allowed at the root level, there are a couple of alternative approaches:

1. Use A or AAAA Records: Point your root domain directly to the IP address of your server.
2. Use ALIAS or ANAME Records: Some DNS providers offer proprietary record types that function like CNAMEs but are designed for the root domain.

Setting Up DNS Records in WHM

WHM (Web Host Manager) allows you to manage DNS settings for the domains hosted on your server. Here’s how you can typically manage DNS records in WHM:

1. Log in to WHM: Go to your WHM login URL and sign in with your credentials.
2. Navigate to DNS Functions:

• In the WHM dashboard, find the “DNS Functions” section.
• Click on “Edit DNS Zone”.

3. Select the Domain:

• Choose the domain you want to manage from the list.
• Click “Edit”.

4. Add or Modify Records:

• You will see a list of existing DNS records.
• For root domains, you’ll usually see A or AAAA records. These are the records you would edit to point the root domain to a new IP address.
• If your DNS provider supports ALIAS or ANAME records, you might see options to add these types of records.

5. Save Changes: After adding or editing records, save the changes and wait for DNS propagation, which can take anywhere from a few minutes to 48 hours.

Example: Adding an A Record for the Root Domain

To set the root domain (example.com) to point to an IP address, you would:

1. In the WHM DNS zone editor for example.com, find the section where you can add a new record.
2. Leave the “Name” field blank or use @ to denote the root domain.
3. Select A for the record type.
4. Enter the IP address of your server in the “Address” field.
5. Save the record.

Summary

• Root CNAME: Typically not allowed due to DNS limitations.
• Alternatives: Use A, AAAA, or proprietary ALIAS/ANAME records for root domains.
• WHM: Use the DNS zone editor in WHM to add or modify records for your domain.

If you have any specific details or follow-up questions, feel free to ask!

WHM API: Find cPanel User by Domain Made Easy

To find the cPanel user associated with a specific domain using the WHM API, you can use the whmapi1 command-line tool or make an API call to the accountsummary endpoint. This endpoint returns information about an account, including the associated user, based on a domain name.

Using whmapi1 Command-Line Tool

1. Access Your Server:
   Connect to your server via SSH.

   ssh root@your_server_ip

2. Run the whmapi1 Command:
   Use the whmapi1 command to query the account information by domain.

   whmapi1 accountsummary domain=example.com

Replace example.com with the domain name you are querying.

3. Output:
   The output will include information about the account, including the username associated with the specified domain.

Using the WHM API Programmatically

You can also make an API call programmatically using cURL or any programming language that supports HTTP requests.

Using cURL

1. Construct the cURL Request:
   Make sure you have your WHM root access hash or API token. Replace YOUR_API_TOKEN with your actual token and example.com with the domain name.

   curl -s -H'Authorization: cpanel YOUR_API_TOKEN' "https://yourserver:2087/json-api/accountsummary?api.version=1&domain=example.com"

2. Output:
   The response will be in JSON format and will include the username associated with the specified domain.

Using a Programming Language (Python Example)

Here’s an example of how you can use Python to make the API call:

1. Install Required Library:
   Ensure you have the requests library installed.

   pip install requests

2. Python Script:

   import requests

   server = "https://yourserver:2087"
   api_token = "YOUR_API_TOKEN"
   domain = "example.com"

   headers = {
       "Authorization": f"cpanel {api_token}"
   }

   url = f"{server}/json-api/accountsummary?api.version=1&domain={domain}"

   response = requests.get(url, headers=headers, verify=False)

   if response.status_code == 200:
       data = response.json()
       if 'data' in data and 'acct' in data['data']:
           user = data['data']['acct']['user']
           print(f"The cPanel user for domain {domain} is {user}")
       else:
           print(f"No account found for domain {domain}")
   else:
       print(f"Error: {response.status_code} - {response.text}")

WHM API Documentation

Refer to the official WHM API documentation for more details and additional parameters you can use with the accountsummary endpoint: WHM API 1 – accountsummary

Summary

• Using whmapi1 command: Quick and direct method via SSH.
• Using cURL: Simple and effective for scripting.
• Using Python: Flexible and can be integrated into larger applications.

By following these steps, you can easily find the cPanel user associated with a specific domain using the WHM API.

Complete Guide to Setting Up Ruby on Rails 3 on WHM (CentOS)

Running Ruby on Rails 3 on a WHM (Web Host Manager) server with CentOS involves several steps, including installing Ruby, setting up Rails, configuring Apache or Nginx, and integrating with cPanel if necessary. Here’s a step-by-step guide to get you started:

Prerequisites

• A server running CentOS with WHM/cPanel installed.
• Root access to the server.

Step-by-Step Guide

1. Access Your Server:
   Connect to your server via SSH.

   ssh root@your_server_ip

2. Install Required Dependencies:
   Update your package list and install necessary dependencies.

   yum update -y
   yum install -y gcc-c++ patch readline readline-devel zlib zlib-devel libyaml-devel libffi-devel openssl-devel make bzip2 autoconf automake libtool bison curl sqlite-devel

3. Install RVM (Ruby Version Manager):
   RVM makes it easy to install and manage different Ruby versions.

   curl -sSL https://get.rvm.io | bash -s stable
   source /etc/profile.d/rvm.sh

Add your user to the RVM group:

   usermod -a -G rvm $USER

4. Install Ruby:
   Use RVM to install Ruby 1.9.3, which is compatible with Rails 3.

   rvm install 1.9.3
   rvm use 1.9.3 --default

5. Install Rails:
   Install Rails 3 using the gem command.

   gem install rails -v 3.2.22

6. Set Up Your Rails Application:
   Create a new Rails application or move an existing one to your server.

   rails new myapp -v 3.2.22
   cd myapp

If you have an existing application, just move it to your server.

7. Install Passenger:
   Passenger is a web and application server for Ruby, Python, and Node.js. It integrates well with Apache and Nginx.

   gem install passenger
   passenger-install-apache2-module

Follow the instructions provided by the Passenger installer to configure Apache.

8. Configure Apache with Passenger:
   Edit your Apache configuration file to include Passenger settings.

   nano /etc/httpd/conf/httpd.conf

Add the following lines at the end of the file:

   LoadModule passenger_module /usr/local/rvm/gems/ruby-1.9.3-p551/gems/passenger-5.0.30/buildout/apache2/mod_passenger.so
   PassengerRoot /usr/local/rvm/gems/ruby-1.9.3-p551/gems/passenger-5.0.30
   PassengerDefaultRuby /usr/local/rvm/wrappers/ruby-1.9.3-p551/ruby

   <VirtualHost *:80>
       ServerName yourdomain.com
       DocumentRoot /path/to/your/app/public
       <Directory /path/to/your/app/public>
           Allow from all
           Options -MultiViews
           Require all granted
       </Directory>
   </VirtualHost>

Replace /path/to/your/app with the path to your Rails application and yourdomain.com with your domain.

9. Restart Apache:
   Restart Apache to apply the changes.

   service httpd restart

10. Integrate with cPanel (Optional):
    If you need to integrate Rails with cPanel, you may need to manually configure each domain or subdomain through cPanel’s interface to point to your Rails application. This typically involves setting up the domain, creating the appropriate directory structure, and configuring the Apache virtual hosts as described above.

Additional Tips

• Database Configuration: Ensure your database (MySQL, PostgreSQL, etc.) is configured correctly in your config/database.yml file.
• Environment Variables: Set any necessary environment variables in your .bashrc or .bash_profile.
• SSL Configuration: If your application requires SSL, configure your virtual host for HTTPS.

By following these steps, you should be able to set up and run a Ruby on Rails 3 application on a WHM/cPanel server with CentOS. If you encounter any issues, refer to the logs and error messages for troubleshooting.

Set Backup Schedules in WHM: Step-by-Step Guide

To set up and manage backups via WHM (Web Host Manager), including scheduling specific times for the backups, you can follow these steps:

1. Access Backup Configuration

1. Log in to your WHM control panel.
2. In the left-hand sidebar, search for and click on Backup Configuration.

2. Enable Backups

1. Ensure the Enable Backups box is checked.
2. Configure the Backup Status to Enable.

3. Set Backup Scheduling

WHM allows you to configure the backup schedule in a flexible manner, specifying days of the week, times, and retention policies.

1. Backup Daily: Check this box if you want to enable daily backups. You can specify particular days and times for these backups.
   • Days of the Week: Select the days you want the backups to run.
   • Backup Time: Select the time you want the backups to start. WHM uses a 24-hour format, so be sure to specify the correct time.
2. Backup Weekly: Check this box if you want to enable weekly backups. You can specify particular days of the week.
   • Days of the Week: Select the days you want the weekly backups to run.
3. Backup Monthly: Check this box if you want to enable monthly backups. You can specify particular days of the month.
   • Dates of the Month: Enter the dates (1-31) you want the monthly backups to run. You can enter multiple dates separated by commas.

4. Retention Settings

Specify how many daily, weekly, and monthly backups you want to retain.

1. Retain Daily Backups: Enter the number of daily backups you want to keep.
2. Retain Weekly Backups: Enter the number of weekly backups you want to keep.
3. Retain Monthly Backups: Enter the number of monthly backups you want to keep.

5. Additional Backup Settings

Configure additional options such as backup type, directories, and databases.

1. Backup Type:
   • Compressed: This option compresses the backups to save space.
   • Uncompressed: This option creates backups without compression.
   • Incremental: This option backs up only the changes since the last backup.
2. Backup User Accounts: Check this box to back up all user accounts.
3. Backup System Files: Check this box to include system files in the backups.
4. Backup SQL Databases: Choose whether to back up databases per account, the entire MySQL directory, or both.

6. Backup Locations

Specify where the backups should be stored.

1. Default Backup Directory: Use the default directory or specify a custom directory.
2. Additional Destinations: You can also configure additional destinations like remote FTP servers, Amazon S3, or other remote locations.
   • Click on Additional Destinations.
   • Select the destination type and fill in the required details (e.g., FTP server details, Amazon S3 credentials).

7. Save Configuration

Once you have configured all the settings, scroll to the bottom and click the Save Configuration button.

By following these steps, you can set up and schedule backups in WHM to ensure your data is regularly backed up according to your specified schedule. This setup helps in maintaining data integrity and provides recovery options in case of data loss or system failures.

Easily Fix Subdomain Issues on WHM Control Panel – Quick Guide

If a subdomain is not working on a WHM (Web Host Manager) control panel, there are several steps you can take to troubleshoot and resolve the issue. Here’s a comprehensive guide:

1. Check Subdomain Creation in cPanel

First, ensure that the subdomain has been correctly created in the cPanel account associated with the domain.

1. Log in to the cPanel account.
2. Navigate to the Domains section and click on Subdomains.
3. Verify that the subdomain is listed there. If not, create it by filling in the subdomain name and selecting the main domain.

2. Verify DNS Settings

Ensure that the DNS settings for the subdomain are correctly configured.

1. Go to the WHM control panel.
2. Navigate to DNS Functions > Edit DNS Zone.
3. Select the domain that the subdomain belongs to.
4. Check if there is an A record for the subdomain pointing to the correct IP address. It should look something like this:
   subdomain 14400 IN A 123.456.789.012
   If the record is missing, add it manually.

3. Check Apache Configuration

Make sure that Apache is correctly configured to handle the subdomain.

1. In WHM, go to Service Configuration > Apache Configuration > Include Editor.
2. Check the Pre Main Include and Post VirtualHost Include sections to ensure there are no overriding rules affecting the subdomain.

4. Verify DNS Propagation

DNS changes can take some time to propagate. Use a DNS propagation checker tool (such as https://www.whatsmydns.net/) to verify that the subdomain is resolving correctly worldwide.

5. Check for Redirects or Misconfigurations

Ensure there are no redirects or misconfigurations in the .htaccess file or in the site configuration that might be affecting the subdomain.

1. Check the .htaccess file in the document root of the subdomain.
2. Look for any redirect rules that might be interfering with the subdomain access.

6. Clear Browser and DNS Cache

Sometimes, the issue might be due to cached data.

1. Clear your browser cache.
2. Flush the local DNS cache on your computer.

• On Windows, open Command Prompt and run:
  sh ipconfig /flushdns
• On macOS, open Terminal and run:
  sh sudo killall -HUP mDNSResponder
• On Linux, the command varies by distribution, but often:
  sh sudo systemctl restart systemd-resolved

7. Check Firewall Settings

Ensure that firewall settings on the server are not blocking access to the subdomain.

1. In WHM, navigate to ConfigServer Security & Firewall (CSF).
2. Check the firewall rules to ensure that the IP address and port for the subdomain are not being blocked.

8. Review Logs for Errors

Check the server logs for any errors that might give you more information about the issue.

1. Access the error logs from WHM under Server Configuration > Apache Configuration > Global Configuration.
2. Look for any relevant error messages that might indicate what’s going wrong.

9. Ensure Web Server is Running

Make sure that the web server (Apache, Nginx, etc.) is running and properly configured.

1. Restart the web server from WHM:

• For Apache: Restart Services > HTTP Server (Apache).
• For Nginx or other servers, ensure they are properly configured and running.

10. Contact Hosting Support

If all else fails, contact your hosting provider’s support team for assistance. They can help check server-side configurations and issues that might not be accessible from your end.

By following these steps, you should be able to identify and resolve the issue with the subdomain not working on your WHM control panel.

How to Enable SHMOP in WHM: Easy Step-by-Step Guide

To enable the shmop (Shared Memory Operations) PHP extension in WHM (Web Host Manager), follow these steps:

1. Log in to WHM

• Access WHM by navigating to http://yourdomain.com/whm and logging in with your administrator credentials.

2. Open EasyApache 4

• In the WHM dashboard, search for EasyApache 4 in the top left search bar and click on it.

3. Customize Your Profile

• Click on Customize next to the currently active profile.

4. Select PHP Extensions

• In the left sidebar, click on PHP Extensions.

5. Search for shmop

• Use the search bar on the PHP Extensions page to search for shmop.

6. Enable the shmop Extension

• Locate the shmop extension in the search results and check the box next to it to enable it.

7. Review and Provision

• After enabling the shmop extension, click on Review in the left sidebar.
• Review the changes to ensure that the shmop extension is selected for installation.
• Click on Provision to apply the changes. This will start the build process, which may take a few minutes.

8. Verify the Installation

• Once the provisioning process is complete, you should verify that the shmop extension is enabled.
• You can create a PHP file (e.g., info.php) in your web directory with the following content to check the PHP configuration:

<?php
phpinfo();
?>

• Access this file via your browser (e.g., http://yourdomain.com/info.php) and look for the shmop section to confirm that it is enabled.

Summary

Enabling the shmop PHP extension in WHM is a straightforward process using EasyApache 4. By following the steps above, you can ensure that the shmop extension is properly installed and enabled on your server, allowing your PHP applications to utilize shared memory operations.

Setting Up SPF with WHM Hostname: Step-by-Step Guide

Setting up SPF (Sender Policy Framework) and configuring the hostname in WHM (Web Host Manager) are important steps to ensure your emails are properly authenticated and reduce the chances of your emails being marked as spam.

Setting Up SPF in WHM

SPF records help prevent spammers from sending emails on behalf of your domain. Here’s how you can set up SPF in WHM:

1. Log in to WHM

• Access WHM by navigating to http://yourdomain.com/whm and logging in with your credentials.

2. Access the Email Authentication Section

• In the WHM dashboard, navigate to Email > Email Deliverability.

3. Select the Domain

• Choose the domain for which you want to configure SPF records.

4. Configure SPF Settings

• In the SPF section, you can generate an SPF record automatically.
• You can also manually configure the SPF settings. A basic SPF record might look like this:

  v=spf1 +a +mx +ip4:your_server_ip ~all

• +a: Allow the domain’s A record.
• +mx: Allow the domain’s MX records.
• +ip4:your_server_ip: Allow the specific IP address of your server.
• ~all: Soft fail for all other IPs.

5. Save the SPF Record

• After configuring the SPF record, save the changes.
• WHM will update the DNS zone for your domain with the new SPF record.

Configuring the Hostname in WHM

A properly configured hostname is crucial for your server’s identity and for email deliverability. Here’s how to set the hostname in WHM:

1. Log in to WHM

• Access WHM by navigating to http://yourdomain.com/whm and logging in with your credentials.

2. Access the Hostname Configuration

• In the WHM dashboard, navigate to Networking Setup > Change Hostname.

3. Set the Hostname

• Enter a fully qualified domain name (FQDN) for your hostname. It should be a subdomain of a domain you own, such as server.yourdomain.com.

4. Update the Hostname

• Click on Change to apply the new hostname.

5. Verify DNS and Reverse DNS (rDNS)

• Ensure that the new hostname has an A record in your DNS settings pointing to your server’s IP address.
• Also, configure reverse DNS (rDNS) for the server’s IP to match the hostname. This is often done through your hosting provider.

Example of SPF Record for WHM Hostname

Assume your server IP is 192.0.2.1 and your hostname is server.yourdomain.com. Your SPF record might look like this:

v=spf1 a mx ip4:192.0.2.1 ~all

To add this to your DNS zone file:

1. Go to DNS Functions > Edit DNS Zone.
2. Select your domain and find the SPF record section.
3. Add or update the SPF record with the above configuration.
4. Save the changes.

Summary

By setting up SPF records and configuring your hostname in WHM, you enhance email deliverability and ensure your server is properly identified. This setup helps in reducing the chances of your emails being marked as spam and ensures that your server’s identity is correctly presented to email recipients.

Troubleshooting WHM cPanel Installation – Sync Issue Fix

If the WHM cPanel installation process was unable to synchronize cPanel & WHM, it could be due to various reasons. Here’s a general troubleshooting guide to address this issue:

1. Check Network Connectivity

• Ensure that your server has proper internet connectivity.
• Check if there are any firewall rules blocking outgoing connections from your server.
• Verify that DNS resolution is working correctly on your server.

2. Verify cPanel & WHM License

• Ensure that your cPanel & WHM license is active and valid.
• Check if your license IP is properly registered with cPanel’s licensing server.
• If you recently renewed your license, make sure the renewal process completed successfully.

3. Restart cPanel & WHM Services

• Restart the cPanel & WHM services to see if it resolves the synchronization issue.
• You can restart services using WHM’s Service Manager or via command line interface (CLI).

4. Check for Updates

• Make sure that your cPanel & WHM installation is up to date.
• Check for any pending updates and apply them if available.

5. Review cPanel & WHM Configuration

• Double-check your cPanel & WHM configuration settings to ensure everything is properly configured.
• Verify that the correct IP addresses and hostname are set in your cPanel & WHM configuration files.

6. Review Logs

• Check the cPanel & WHM logs for any errors or warning messages that might provide clues about the synchronization issue.
• Look for logs in /usr/local/cpanel/logs directory.

7. Contact cPanel Support

• If the issue persists, consider reaching out to cPanel’s support team for further assistance.
• Provide them with relevant details about your server configuration and the steps you’ve taken to troubleshoot the issue.

Conclusion

Troubleshooting synchronization issues between cPanel & WHM during installation can be complex and may require investigating multiple factors. By following the steps outlined above and systematically checking different aspects of your setup, you can often identify and resolve the problem. If you’re unable to resolve the issue on your own, don’t hesitate to seek assistance from cPanel’s support team or your hosting provider for further help.

Configuring WHM mod_rewrite and mod_userdir – Step-by-Step

To configure mod_rewrite and mod_userdir in WHM (Web Host Manager), follow these steps. These modules are used to enable URL rewriting and user directory access in Apache web servers.

Enabling mod_rewrite in WHM

mod_rewrite is an Apache module that allows for URL rewriting. This is useful for creating clean, user-friendly URLs and for redirecting requests.

1. Log in to WHM:

• Access WHM by navigating to http://yourdomain.com/whm and logging in with your credentials.

2. Ensure mod_rewrite is Enabled:

• Go to the Apache Configuration section.
• Select Global Configuration.
• Ensure that mod_rewrite is listed under the “Loaded Modules” section. If it is not, you may need to rebuild Apache with mod_rewrite included.

3. Rebuild Apache with mod_rewrite:

• Navigate to EasyApache 4.
• Customize your profile.
• In the Apache Modules section, search for mod_rewrite and ensure it is selected.
• Save and provision the profile to rebuild Apache with the selected modules.

Enabling mod_userdir in WHM

mod_userdir is an Apache module that allows users to access their web content using URLs like http://yourdomain.com/~username.

1. Log in to WHM:

• Access WHM by navigating to http://yourdomain.com/whm and logging in with your credentials.

2. Enable mod_userdir:

• Go to the Security Center section.
• Click on Apache mod_userdir Tweak.
• Enable the mod_userdir protection by unchecking Enable mod_userdir Protection. This will allow access to user directories via ~username.

3. Configure User Directories:

• You can configure specific user directory access and exceptions in the same section. This is useful if you want to allow or restrict user directory access for certain users or IP addresses.

Example .htaccess for mod_rewrite

To use mod_rewrite, you typically need to create or edit a .htaccess file in your web directory. Here is an example of a basic .htaccess file to rewrite URLs:

RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?url=$1 [L,QSA]

• RewriteEngine On: Enables the rewrite engine.
• RewriteCond: Conditions to check before applying the rewrite rule.
• RewriteRule: The rule to rewrite the URL.

Example Configuration for mod_userdir

To configure user directory access, you can use the Apache configuration file. Here is an example configuration snippet:

<IfModule mod_userdir.c>
    UserDir public_html
    UserDir disabled root
    UserDir enabled user1 user2

    <Directory /home/*/public_html>
        AllowOverride All
        Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
        Require method GET POST OPTIONS
    </Directory>
</IfModule>

• UserDir public_html: Specifies the directory name within the user’s home directory that contains their web files.
• UserDir disabled root: Disables user directory access for the root user.
• UserDir enabled user1 user2: Enables user directory access for user1 and user2.

Summary

By enabling and configuring mod_rewrite and mod_userdir in WHM, you can take advantage of Apache’s powerful URL rewriting and user directory features. This configuration allows for cleaner URLs and provides user-specific web directories, enhancing the flexibility and usability of your server.