Adding and Removing Domains in Plesk Obsidian

Plesk Obsidian empowers users with the flexibility to manage multiple domain names and websites efficiently. If your hosting package permits the use of more than one domain, you can effortlessly add these domains to your server. It is crucial to ensure that any new second-level domain name, such as example.com, is properly registered before attempting to add it within Plesk. Depending on your hosting provider, domain name registration services might be available directly through the Customer Panel. Alternatively, you will need to register your domain name with an accredited domain name registration authority.

Plesk offers robust options for configuring various types of websites. You can set up the following site configurations:

• Website Addressed by a Second-Level Domain Name: This configuration provides a complete set of services for your primary online presence. These services include:

  • A unique internet address, such as example.com, serving as your main domain.
  • Additional domain names, also known as domain aliases, to point multiple addresses to the same website.
  • Subdomains, which are distinct sections of your site accessible via easy-to-remember addresses like mail.example.com, extending your main domain's functionality.
  • Separate FTP accounts, enabling collaborative content management with specific directory access permissions for each account.
  • Tools for content creation, including the intuitive Sitejet Builder.
  • Streamlined deployment of popular web applications, such as content management systems, photo galleries, e-commerce platforms, and blogging tools.
  • Secure data exchange facilitated by the SSL/TLS protocol, ensuring encrypted communication. For this, a dedicated IP address, not shared with other users or sites, is often required.
  • Comprehensive email services, including mailboxes and mailing lists.
  • Detailed statistics to monitor website visits and user engagement.

• Website or a Division of a Website Addressed by a Third-Level Domain Name (Subdomain): Typically used to create distinct sections or applications within an existing main site, a subdomain features an internet address composed of three parts separated by dots (e.g., blog.yourdomain.com). Key services available for subdomains include:

  • A separate document root from the main site, defining where the subdomain's web pages are stored on the server.
  • FTP access specifically for managing the subdomain's content.
  • Content creation capabilities using Sitejet Builder.
  • Simplified deployment of various web applications tailored for the subdomain.
  • Secure data exchange through the SSL/TLS protocol, enhancing security.
  • Access to site visit statistics for monitoring the subdomain's performance.

Adding More Domains

To successfully host a new website using a second-level domain name within Plesk, follow these steps:

1. Navigate to the Websites & Domains section, then click on Add Domain. Proceed by following the intuitive on-screen instructions.

   Note: The specific information and options presented on the Add Domain screen may vary depending on your Plesk edition and the configurations set by your hosting provider.

   Important DNS Configuration: If you opt for the recommended setup, it is essential to correctly link your domain name's DNS settings with your registrar. This typically involves updating the NS (Name Server) record at your registrar's portal with the Plesk name server IP address. To locate this crucial IP address:

   • Go to Websites & Domains.
   • Select your domain name.
   • Access DNS Settings.
   • Locate the NS record (e.g., example.com. NS ns.example.com*).
   • Find the corresponding A record for the NS record value (e.g., ns.example.com. A 192.0.2.12).

   The resulting IP address, such as 192.0.2.12, is the Plesk name server IP you need to enter at your domain registrar.

2. Click OK to confirm the addition. The newly added domain name will then appear in the list at the bottom of the screen, signifying its successful integration into your Plesk environment.

3. If your account permissions allow for modifications to hosting settings, you can further customize your website by clicking on the new domain name. This action enables you to view or change various hosting configurations, as detailed in the section dedicated to Changing Hosting Settings.

With your new domain successfully added, you can now proceed to develop your website content. You can either begin creating your site using the integrated Sitejet Builder or upload your existing web content directly to the new website's subscription. For more comprehensive guidance on this process, refer to the section on Website Content.

Choosing a Domains View Mode

The presentation and functionality of the "Websites & Domains" screen in Plesk can be customized to suit your preferences and the number of domains you manage. The layout, visible controls, and overall user experience (UX) vary significantly based on the selected domain view mode:

• Dynamic List: This mode is often considered the optimal choice as it seamlessly integrates the benefits of other view modes. It offers a concise layout ideal for managing a large number of domains while providing an expandable list that reveals all available controls when needed. Unique to the Dynamic List, it also displays domain favicons, enhancing visual identification.

• Active List: This mode is particularly well-suited for users who manage a moderate number of domains and require immediate access to all available controls directly on the screen.

• Classic List: Designed for environments with an extensive number of domains (typically more than 100), the Classic List mode prioritizes conciseness. While efficient for large lists, it's important to note that not all controls may be directly visible, requiring additional navigation to access certain functionalities.

To change your domain view mode, navigate to Websites & Domains, click on the view mode icon, and then select your preferred display mode from the options provided.

Adding a Domain Favicon

A domain favicon is a distinctive small image displayed by Plesk alongside a domain name when you are utilizing the Dynamic List view mode. These favicons are visible directly on the Websites & Domains screen, providing an at-a-glance identifier for your various sites.

Upon the creation of a new domain, Plesk automatically generates and displays a default favicon, typically derived from the first two characters of your domain name. However, for enhanced brand recognition and easier navigation, you have the option to upload a custom favicon, often matching the one used for your website in browser tabs. Custom domain favicons offer several advantages:

• They facilitate quicker identification of the desired website within your Plesk interface.
• They enable clear visual differentiation between multiple domains, especially when managing numerous sites.

To add or update a custom favicon for your domain in Dynamic List view, please follow these instructions:

1. Select an image file in PNG, SVG, or ICO format to serve as your favicon. These formats are widely supported and ensure optimal display quality.

2. Rename your chosen favicon image file to one of the following standard names:

   • favicon.svg
   • favicon-32x32.png
   • favicon.png
   • favicon-16x16.png
   • apple-touch-icon.png
   • favicon.ico

3. Using the File Manager, upload the renamed image file to one of the following specific directories within your website's structure:

   • The document root directory, which is typically httpdocs unless a custom document root has been configured by your hosting provider.
   • The /images subdirectory located within the document root directory.
   • The /assets/images subdirectory, also found within the document root directory.

   Crucial Note: It is imperative that your favicon is uploaded directly to one of the specified directories. Plesk performs a non-recursive search for exact file name matches within these exact directories. Uploading a file like favicon.svg to a subdirectory such as /images/favicon will result in Plesk not locating your custom image, as it is nested too deeply.

Once your custom favicon image has been uploaded, Plesk may require a short period to detect and display it. If the favicon does not appear immediately, a simple refresh of your Plesk page should resolve the issue.

WordPress Integration: For websites powered by WordPress, you can streamline the favicon creation process for both your website and your domain within Plesk simultaneously. The Favicon by RealFaviconGenerator plugin is highly recommended for this. Plesk is designed to automatically detect a website favicon created through this plugin's wizard and will consequently set it as the domain favicon in the Dynamic List view.

Moving Domains

Plesk Obsidian provides the capability to migrate add-on domains – those created subsequent to the primary domain of a subscription – between your existing subscriptions. This feature proves invaluable for various management strategies, such as maintaining separate staging environments for development and then seamlessly transitioning websites from development to production subscriptions.

When a domain is moved to a different subscription, it includes a comprehensive transfer of its associated assets. This encompasses all website content, configuration files, log files, PHP settings, APS applications, as well as any linked subdomains and domain aliases.

Prerequisite: The target subscription, to which you intend to move your domain, must possess adequate available resources. This includes sufficient allowances for additional websites, subdomains, domain aliases, or mail names to accommodate the incoming domain.

To initiate the transfer of an add-on domain to another subscription, follow these steps:

1. From the Websites & Domains section, locate the add-on domain you wish to move. Click on the move icon (usually represented by an arrow or similar symbol), and then select Move Domain.

2. A list of available subscriptions will be presented. Choose the desired target subscription from this list and click Move to confirm the transfer.

Upon successful completion of the moving process, your domain will be seamlessly reassigned to the chosen subscription, and its associated services will begin operating under the new subscription's resources.

Important Consideration for Applications: If the domain being moved hosts a web application (e.g., WordPress, Joomla!, or similar CMS), it's crucial to understand that the application's database is not automatically transferred with the domain. While this typically does not immediately impact the website's functionality, it is often advisable to manually move the database to the subscription the domain is now assigned to, ensuring all components are consolidated.

Known Issues and Limitations

While the domain moving feature is powerful, certain conditions and limitations apply:

• The following types of domains or related entities cannot be moved:
  • The default domain, which is the first domain created under a subscription.
  • A subdomain cannot be moved independently without its parent domain.
  • A domain alias cannot be moved independently without its parent domain.
• A domain cannot be transferred to a subscription that does not have hosting services enabled.
• Similarly, a domain configured with mail services cannot be moved to a subscription that lacks mail service capabilities.
• You are prevented from moving a domain if the target subscription already owns another domain utilizing the exact same document root value. To proceed with the move, you must first adjust the "Document root" value of the domain in its Hosting Settings.
• Should a domain with custom Apache or Nginx directives be moved, these directives are preserved during the transfer. However, it is highly recommended to review them post-migration to ensure they remain appropriate and functional within the new subscription context.
• If a domain is moved to a target subscription where the PHP settings significantly differ from those previously configured for the domain, the target subscription may enter a locked state, and a corresponding notification about it will be displayed.
• In scenarios where a domain hosting a web application (such as WordPress or Joomla!) also has an additional Plesk user designated as the application's administrator:
  • The additional user will unfortunately lose their direct access to the application.
  • The login credentials (username and password) for the application's administrator will be altered. You can typically find these updated credentials within the application's specific settings after the move.
• If a domain with an associated mail user is transferred to a subscription that belongs to another owner, the email address will be detached from the mail user.

Removing Domains

When a domain is deleted from your Plesk environment, it's critical to understand that all data and configurations associated with that specific website are permanently removed from the server. This action is irreversible and should be performed with caution.

Important Restriction: The primary domain of your subscription, which is the initial or default domain name established for your account, cannot be deleted. While direct deletion is not an option, you do have the ability to rename this main domain if necessary.

To safely remove a domain or subdomain from your Plesk account, follow these steps:

1. Navigate to the Websites & Domains section and precisely locate the name of the domain or subdomain you intend to remove from your server.

2. Click on either Remove Website (for full domains) or Remove Subdomain (for subdomains), depending on the type of entry you are deleting.

3. A confirmation prompt will appear. Carefully review the details to ensure you are deleting the correct domain, then click OK to finalize the removal process.

Domain Registration Notice: Please be aware that deleting a domain name from your Plesk Customer Panel solely removes its hosting configuration from your server. This action does not, however, cancel the actual registration of the domain name with its registrar. If you have registered these domain names, they remain under your ownership and can be utilized for future websites or services by reconfiguring their DNS settings.