Sorry, the subdomain cannot be removed because it is linked to the addon domain(s). Solution:

"Sorry, the subdomain cannot be removed because it is linked to the addon domain(s)" Solution

This error message, frequently encountered on web hosting platforms, appears when attempting to delete a subdomain and indicates that this subdomain is linked to one or more addon domains. This situation usually arises from your website's structure and domain name configurations. In this article, we will examine the causes of this error, solutions, and precautions that can be taken to avoid such problems in the future in detail.

Meaning and Causes of the Error Message

The error "Sorry, the subdomain cannot be removed because it is linked to the addon domain(s)" technically means that your subdomain is linked to an addon domain, which is used to serve a different website or content than your main domain. Your hosting control panel (cPanel, Plesk, etc.) detects this connection and does not allow you to delete the subdomain. This connection usually occurs for the following reasons:

• Addon Domain Configuration: An addon domain allows you to host a different website using a subdirectory of your main domain. In this case, the subdomain may be set as the root directory of the addon domain.
• Incorrect Redirection: Your subdomain may have been accidentally redirected to the addon domain. This may have been done through the .htaccess file or redirection settings in the hosting panel.
• DNS Records: The DNS records of your subdomain may be pointing to the IP address of the addon domain.
• Database Connection: Rarely, an application or website used by your subdomain may be connected to the addon domain's database.

Relationship Between Addon Domain and Subdomain

Understanding the relationship between addon domains and subdomains is critical to resolving this error. An addon domain is actually part of your main domain, but it acts like a different website. When you create an addon domain in your hosting account, a subdirectory is usually created under your main domain, and this subdirectory is used as the root directory of the addon domain. If your subdomain is also linked to this subdirectory, you must break this connection before deleting the subdomain.

Solutions: Step-by-Step Guide

To resolve this error, you can follow these steps in order:

1. Checking Addon Domain Settings

The first step is to check the addon domain settings from your hosting control panel (cPanel, Plesk, etc.). These settings will show how your subdomain is associated with the addon domain.

For cPanel Users:

1. Log in to cPanel.
2. In the "Domains" section, find and click the "Addon Domains" option.
3. You will see a list of your addon domains. Find the addon domain that is linked to the subdomain you are getting the error for.
4. In the "Document Root" column, check which directory this addon domain is directed to.
5. If this directory is related to the subdomain you are trying to delete, you may need to delete the addon domain or change its "Document Root".

For Plesk Users:

1. Log in to Plesk.
2. Go to the "Websites & Domains" section.
3. You will see a list of your addon domains. Find the addon domain that is linked to the subdomain you are getting the error for.
4. Enter the settings of the addon domain and check the "Hosting Settings" section.
5. In the "Document Root" field, check which directory this addon domain is directed to.
6. If this directory is related to the subdomain you are trying to delete, you may need to delete the addon domain or change its "Document Root".

If you do not want to delete the addon domain, you can redirect the "Document Root" to a different directory (for example, a new folder in the root directory of your main domain). This will break the connection between your subdomain and the addon domain.

2. Examining the .htaccess File

The .htaccess file is a file used to modify the Apache web server configuration. A misconfigured .htaccess file can cause your subdomain to be redirected to the addon domain.

1. Access your hosting account via FTP or file manager.
2. Find the .htaccess file located in the root directory of your main domain.
3. Open the file with a text editor.
4. Look for redirection rules like the following:

    RewriteEngine On
    RewriteCond %{HTTP_HOST} ^subdomain\.example\.com$ [NC]
    RewriteRule ^(.*)$ http://addondomain.com/$1 [R=301,L]
  

1. If you find such a rule and think that this rule is accidentally redirecting your subdomain to the addon domain, delete these lines or comment them out (by putting a # sign in front of them).
2. Save the changes and reload the .htaccess file.

Caution: Making incorrect changes to the .htaccess file can cause your website to not work. Therefore, it is important to back up the file before making any changes.

3. Checking DNS Records

The DNS records of your subdomain may be pointing to the IP address of the addon domain. In this case, you need to check and correct the DNS records.

1. Access DNS management from your hosting control panel or your domain registrar's website.
2. Find the A record or CNAME record for your subdomain.
3. Make sure this record points to the correct IP address or domain name. If it points to the IP address of the addon domain, enter the correct IP address or domain name.
4. Save the changes. DNS changes may take some time to take effect (usually 24-48 hours).

4. Examining Database Connections

Rarely, an application or website used by your subdomain may be connected to the addon domain's database. In this case, you need to check and correct the database connections.

1. Find the configuration files of the application or website running on your subdomain (for example, wp-config.php for WordPress).
2. Check the database connection information (database name, username, password, server address) in these files.
3. If this information belongs to the addon domain's database, enter the correct database information.
4. Save the changes.

5. Contacting Your Hosting Provider

If the problem persists despite following the above steps, contacting your hosting provider will be the most accurate solution. Your hosting provider can check the server-side configurations, identify the source of the problem, and assist you.

Example Scenario and Solution

Let's say your main domain is "example.com" and your subdomain is "blog.example.com". You have created an addon domain called "news.com" and accidentally set the "Document Root" of this addon domain to the "blog.example.com" directory. In this case, you will get an error when you try to delete the "blog.example.com" subdomain.

Solution:

1. Log in to cPanel.
2. Click the "Addon Domains" option in the "Domains" section.
3. Find the "news.com" addon domain.
4. Make sure you see the "blog.example.com" directory in the "Document Root" column.
5. Change the "Document Root" of the "news.com" addon domain to a different directory (for example, you can create a new folder named "news" and redirect it to that).
6. You can now delete the "blog.example.com" subdomain without any problems.

Avoiding Such Problems in the Future

To avoid encountering such problems again, you can take the following precautions:

• Understand the relationship between addon domains and subdomains well.
• Make the settings in your hosting control panel carefully.
• Always back up the .htaccess file before making any changes.
• Check your DNS records regularly.
• Carefully review the configuration files of your website and applications.
• Use the documentation and support resources offered by your hosting provider.

Conclusion and Summary

The error "Sorry, the subdomain cannot be removed because it is linked to the addon domain(s)" usually occurs because your subdomain is accidentally associated with an addon domain. In this article, we have examined the causes of this error, solutions, and precautions that can be taken to avoid such problems in the future in detail. Checking addon domain settings, examining the .htaccess file, checking DNS records, and examining database connections are the basic steps you can take to resolve this error. If the problem persists despite following these steps, contacting your hosting provider will be the most accurate solution. Remember, you can prevent such problems with careful planning and correct configuration.