• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question I want to reconstruct the site structure

Zoo3

Regular Pleskian
It seems that my Plesk has a problem with the site composition. The influence appears clearly in the setting of Let's Encrypt.

It is a topic I made before.
Question - Let's Encrypt can not be set properly

It seems that certificates share with each other on a newly created website. ID is duplicated.
In the example of the table below, when I create a new subdomain ID is created with '22', certificates share among ID 22.

+----+-------------------------------------+--------+------------------------+
| id | name | rep_id | name |
+----+-------------------------------------+--------+------------------------+
| 2 | Backup sign certificate | NULL | NULL |
| 10 | Lets Encrypt site4.exmample.com | 3 | site4.exmample.com |
| 11 | Lets Encrypt site2.exmample.com | 2 | site2.exmample.com |
| 22 | Lets Encrypt exmample.com | 4 | exmample.com |
| 22 | Lets Encrypt exmample.com | 4 | site3.exmample.com |
+----+-------------------------------------+--------+------------------------+​


So I would like to remodel the site configuration manually. Because it is not repaired with 'Plesk repair' command. I want to create a new subdomain (site) without duplicating the site ID. If subdomains are created normally, IDs will be duplicated. Can I forcibly change the internal source after creating the subdomain once?
 
Back
Top