Facebook
Twitter-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion -
Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here
I can't replicate the issue. Best suggestion I can give is to contact support for help.
Ankebut
Regular Pleskian
I believe I've found the error. After generating with extension DNSSEC DS resource records and manually adding them to the DNS settings, I receive the following error message. I suspect that Plesk makes a mistake when entering the signature, causing a syntax error. If I delete the DS entries listed below, everything works fine again and there are no more problems.
Ankebut
Regular Pleskian
After I insert the DNSSEC entry under DNS settings and then click on "Update," I receive the response "DNS record successfully saved." However, I also get the warning "Permission denied" immediately below. There seems to be a permissions issue somewhere, but I'm not sure where.
If you think it's a bug, please create a detailed bug report here (with all steps needed for me to reproduce the issue on a test server). I can forward it to developers.
I you need a solution urgently, it's best to open a support ticket so the support team can investigate the issue.
I you need a solution urgently, it's best to open a support ticket so the support team can investigate the issue.
Ankebut
Regular Pleskian
I'm sorry, but this is really not a good solution from Plesk. This is a support forum, and I have already posted all the relevant information regarding the error. This is definitely a bug or an error on Plesk's part. I pay every month for a subscription with my provider, Hetzner. When I try to use Plesk support with my license key, I am told to contact Hetzner or purchase paid support. Why should I pay for errors caused by Plesk when I am already paying for the service every month? It's not acceptable that I have to pay extra for support. I have invested a lot of time and provided detailed information about the error. Now you're telling me to post everything again elsewhere and contact support? This is really not customer-friendly.
I have tried to replicate your issue, but even tough you posted a lot of information, I wasn't able to. That's why I suggested to either create a detailed bug report or to open a support ticket for further investigation.
For what it's worth, in most cases DS records should not be added to your own DNS zone, but to the parent zone at your domain provider.
I am sorry that you feel this isn't a good solution. I don't doubt there is an issue, your errors and screenshots proof that there is. However, I can not replicate the error based on your posts. That's why I unfortunately don't have any other options to offer. I also like to point out that this is a community forum. Available for users to discus Plesk and related technologies. But it is not an official channel for support.
Plesk license from resellers do not include direct support from Plesk. Because the reseller is responsible for providing direct support. Which is why reseller licenses are cheaper than Plesk retail licenses (which do include support).
For what it's worth, in most cases DS records should not be added to your own DNS zone, but to the parent zone at your domain provider.
Vertex
New Pleskian
Maybe I can add some more information @Kaspar@Plesk - btw. I use Plesk Obsidian 18.0.61 with Update #5. I just added the DS entries for DNSSEC and got the same warning message @Ankebut mentioned above. When I looked into Plesks panal log (I have modified some personal parts) I found these errors:
Code:
stderr:
[2024-06-16 16:20:38.885] 0000055:666ef4b60000 ERR [panel] Error during example.com updateZone: dnsmng failed: :
0: /opt/psa/admin/plib/Service/Dns/Connector/Plesk.php:14
Service_Dns_Connector_Plesk->commitChanges()
1: /opt/psa/admin/plib/Service/Dns/Connector/Proxy.php:207
Service_Dns_Connector_Proxy->commitChanges()
2: :
[2024-06-16 16:20:39.070] 0000319:666ef4b70000 ERR [panel] PleskPermissionDeniedException: Permission denied.
file: /opt/psa/admin/plib/CommonPanel/Controller/Action/Abstract.php
line: 194
code: 0
trace: #0 /opt/psa/admin/application/smb/controllers/DnsZoneController.php(292): CommonPanel_Controller_Action_Abstract->_postRequestRequired()
#1 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Action.php(516): Smb_DnsZoneController->updateAction()
#2 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Dispatcher/Standard.php(308): Zend_Controller_Action->dispatch(string 'updateAction')
#3 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(object of type Zend_Controller_Request_Http, object of type Zend_Controller_Response_Http)
#4 /opt/psa/admin/plib/Application/Web.php(48): Zend_Controller_Front->dispatch(object of type Zend_Controller_Request_Http)
#5 /opt/psa/admin/htdocs/application.php(15): Plesk\Application_Web->run()
[2024-06-16 16:21:30.998] 0000055:666ef4eaf0000 ERR [panel] The limit on serial number changes was reached. No more DNS zone changes can be carried out today.
[2024-06-16 16:21:31.450] 0000055:666ef4eaf0000 ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/dnsmng' '--update' 'example.com'] with exit code [1]
[2024-06-16 16:21:31.450] 0000055:666ef4eaf0000 ERR [panel] '/opt/psa/admin/bin/dnsmng' '--update' 'example.com' failed with code 1.
stdout:
stderr:
[2024-06-16 16:21:31.450] 0000055:666ef4eaf0000 ERR [panel] Error during example.com updateZone: dnsmng failed: :
0: /opt/psa/admin/plib/Service/Dns/Connector/Plesk.php:14
Service_Dns_Connector_Plesk->commitChanges()
1: /opt/psa/admin/plib/Service/Dns/Connector/Proxy.php:207
Service_Dns_Connector_Proxy->commitChanges()
2: :
[2024-06-16 16:21:31.638] 0000071:666ef4eb9bc8f ERR [panel] PleskPermissionDeniedException: Permission denied.
file: /opt/psa/admin/plib/CommonPanel/Controller/Action/Abstract.php
line: 194
code: 0
trace: #0 /opt/psa/admin/application/smb/controllers/DnsZoneController.php(546): CommonPanel_Controller_Action_Abstract->_postRequestRequired()
#1 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Action.php(516): Smb_DnsZoneController->syncZoneAction()
#2 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Dispatcher/Standard.php(308): Zend_Controller_Action->dispatch(string 'syncZoneAction')
#3 /opt/psa/admin/plib/vendor/plesk/zf1/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(object of type Zend_Controller_Request_Http, object of type Zend_Controller_Response_Http)
#4 /opt/psa/admin/plib/Application/Web.php(48): Zend_Controller_Front->dispatch(object of type Zend_Controller_Request_Http)
#5 /opt/psa/admin/htdocs/application.php(15): Plesk\Application_Web->run()@Vertex thank you, I apricate your input. However I am still unable to replicate the issue based on your information (and those from previous posts in this thread). I suspected that the issue might be caused when using a specific server configuration. Whiteout knowing what configuration is needed to replicate the issue it's hard to investigate. Which is why it's better to open a ticket with Plesk support so our support engineers can investigate the issue directly on your server.
Aside from the issue. It should not be necessary to add DS records to your DNS in Plesk. Those records are for use with the parent zone at your domain provider.
Aside from the issue. It should not be necessary to add DS records to your DNS in Plesk. Those records are for use with the parent zone at your domain provider.
Similar threads
