• 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 MaximilianH

  1. M

    Resolved JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 23643 of the JSON data

    After I created also ln -s /usr/bin/named-checkzone /usr/sbin/named-checkzone it works now on our server.
  2. M

    Resolved JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 23643 of the JSON data

    are maybe other files affected too that were updated in Ubuntu 20? -rwxr-xr-x 1 root root 39328 Jul 16 20:48 /usr/bin/named-checkconf -rwxr-xr-x 1 root root 35304 Jul 16 20:48 /usr/bin/named-checkzone -rwxr-xr-x 1 root root 35304 Jul 16 20:48 /usr/bin/named-compilezone -rwxr-xr-x 1 root root...
  3. M

    Resolved JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 23643 of the JSON data

    The workaround does not fix it for us. Even after creating that symllink lrwxrwxrwx 1 root root 24 Jul 24 14:21 /usr/sbin/named-checkconf -> /usr/bin/named-checkconf the error still appears and the DNS configuration can not be updated: 2024-07-24 14:24:50 ERR panel...
  4. M

    Resolved JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 23643 of the JSON data

    Hello, we are using DNS on that server since June - before we had external Nameserver. The DNSSEC extension was installed, but not used yet. I uninstalled it - no change with the issue. Also after reinstalling (still no use of DS records). In the panel log I found the first appearance of an...
  5. M

    Resolved JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 23643 of the JSON data

    Hello, I have now also the same issue here when I try to create/change DNS zones. OS: Ubuntu 20.04.6 LTS Product: Plesk Obsidian Version 18.0.62 Update #1, zuletzt aktualisiert: 4. Juli 2024 06:26:49 When I try to change settings for a DNS zone or synchronize/desynchronize an alias this error...
  6. M

    Backup Failing after Upgrade from 10.1 to 10.3.1

    Hello, we got the same error after updating to Plesk 10.3.1 Because of the error description "Unable to get Global settings for APS Applications (ErrorCode: 3, STDOUT: )" and because of the fact we do not use Applications on that server until now - I have deleted the APS applications we...
See more
Back
Top