• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  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...
Back
Top