Resolved Azure DNS - ServiceController.php:82

[SimonB]

I'm trying to activate the Azure DNS Zone using the Microsoft Azure DNS extension but when I click Activate it errors saying:

ERROR: TypeError: Cannot access offset of type string on string (ServiceController.php:82)

I am running Plesk Obsidian Version 18.0.61 Update #5 on a Windows 2019 Server

Has anyone see this before or know how to fix this issue?

I have tried updating the credential in the Azure Authorization section and deactivatings the zone first, but nither of them worked.

 

[Kaspar@Plesk]

@SimonB that doesn't sound good. To get a better understanding of the issue could you perhaps clarify to following: When exactly are you getting this error? After installing the extension and clicking the Authorize button? Or after authorizing, selecting a domain and clicking the activate button?

 

[SimonB]

I get it what I click the "Activate" button below, I tick the checkbox for the domain, then click activate.

The Azure authorisation worked OK, and if I go to DNS Managment and click "Sync All Zones" I get the message "Information: The following DNS zone was created: xxxxx.com" so I asume the authorisation is working ok.

 

[Kaspar@Plesk]

Thank you for clarifying. One last question so I can submit this as bug internally. Which Microsoft Azure DNS extension are you using on your server?

 

[SimonB]

It's the "Microsoft Azure DNS" version; 1.1.2-42 / vendor Plesk

I am not sure if this helps but the PHP version enabled are

PHP handlers
8.3.8 FastCGI application
8.1.29 FastCGI application

I just tried the Diagnose & Repair tool to see if that sorted it, but it didn't

 

[Kaspar@Plesk]

Thank you. I've submitted the issue for analysis to our engineers. Unfortunately there seems to be no workaround for this issue currently.

 

[SimonB]

Thanks for your help, if the Devs want any more info or would like me to try anthing please let me know.

 

[Kaspar@Plesk]

@SimonB it look like this issue needs further investigation by our engineers. Any chance you can open a support ticket so engineers can investigate the issue directly on your server? You can mention case PPS-16229 in the ticket as a reference to the issue.

 

[SimonB]

I've submitted a support ticket, thanks for you help.

 

[SimonB]

Just a follow up on this, the Plesk engineers got me sorted. I turned out I had forgotten to assign a role to the plesk application in Azure Entra ID (AD).
Once i fixed that it worked as expected.

Feel free to mark this as Resolved, thanks to everyone for the qick help