• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Recent content by SimonB

  1. S

    Resolved Azure DNS - ServiceController.php:82

    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 :)
  2. S

    Resolved Azure DNS - ServiceController.php:82

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

    Resolved Azure DNS - ServiceController.php:82

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

    Resolved Azure DNS - ServiceController.php:82

    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
  5. S

    Resolved Azure DNS - ServiceController.php:82

    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...
  6. S

    Resolved Azure DNS - ServiceController.php:82

    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...
    • SimonB
    • Thread
    • azure dns dns
    • Replies: 9
    • Forum: Reports
  7. S

    Issue STMP QUIT / Disconnect Problem with TLS

    Hi We recently updated to Plesk v18.0.48 and with it MailEnable Standard v10.42 After the update we are experiencing some problem using SMTP with TLS (port 587), it appears the QUIT command no longer causes the server to disconnect the STMP connection. We have Plesk running on an Azure VM...
  8. S

    Resolved Azure DNS access token

    Thanks for your help it's much appreciated, after updating the secret I can now get into the Azure DNS extension and the new DNS values are been pushed to Azure. For anyone else reading this who is having the same problem, to get the correct module_id, run the below SQL first and look for the...
  9. S

    Resolved Azure DNS access token

    Update: Just updated to Plesk ObsidianVersion 18.0.41 Update #1, and the same problem, unable to get into the Azure DNS extension page.
  10. S

    Resolved Azure DNS access token

    We are using the Azure DNS extension with Plesk Obsidian (Version 18.0.40 Update #3) on a Windows 2019 Server. It was all working fine a few months ago, but we just got a message from Let's encrypt saying the SSL cert is about to run out on one of the domains. After a bit of fault finding I...
See more
Back
Top