Issue Error When Modifying DNS SOA Settings

[Ankebut]

Server operating system version

Ubuntu 22.04.4 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.61 Update 3

When I change the DNS SOA settings or select "Use Default Settings," I receive an error message.

 

[Ankebut]

Internal errorSyntaxError: Unexpected non-whitespace character after JSON at position 104 (line 1 column 105)

This error i mean

 

[Kaspar@Plesk]

I can't replicate the issue. Best suggestion I can give is to contact support for help.

 

[Ankebut]

ok

 

[Ankebut]

I have the following in the pnale.log

[2024-05-23 20:48:27.682] 70812:664f8f7b9db5d ERR [panel] Error during doitauto.de 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: :

 

[Ankebut]

I have just noticed that Plesk has not created a zone file for doitauto.de. Is this normal?

 

[Ankebut]

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.

doitauto.de. IN DS 8752 8 1 C7C37C75FF553C3D4929F637BAEEAE625E85F436
doitauto.de. IN DS 8752 8 2 BC96B190B8DBA32F51E01F387F00343A3732BE3419683FED1E5509D780720215
doitauto.de. IN DS 64531 8 1 35A8ABC6F748AC06E5AC1F95D826C0047A72745D
doitauto.de. IN DS 64531 8 2 681AE5F0CD1837D0456FD86C10B2E5E1593CE92A97C7869CAB2FF44DD8E9850E

 

[Ankebut]

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.

 

[Ankebut]

[2024-05-24 10:58:29.183] 63983:665056b52cae8 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-05-24 10:58:29.631] 63987:665056b59a3b8 ERR [panel] Call to a member function getParam() on null
[2024-05-24 10:58:30.190] 63980:665056b62e635 ERR [panel] Call to a member function getParam() on null
[2024-05-24 10:58:30.777] 63986:665056b6bdb1f ERR [panel] Call to a member function getParam() on null
[2024-05-24 11:00:18.966] 65296:66505722e3df0 ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/dnsmng' '--update' 'calhan.de' '--without-reverse'] with exit code [1]
[2024-05-24 11:00:18.966] 65296:66505722e3df0 ERR [panel] '/opt/psa/admin/bin/dnsmng' '--update' 'calhan.de' '--without-reverse' failed with code 1.

 

[Kaspar@Plesk]

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.

 

[Ankebut]

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.

 

[Kaspar@Plesk]

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.

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. [...]

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.

[...] 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. [..]

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.