• Dear Pleskians! The Plesk Forum will be undergoing scheduled maintenance on Monday, 7th of July, at 9:00 AM UTC. The expected maintenance window is 2 hours.
    Thank you in advance for your patience and understanding on the matter.

Search results

  1. A

    Resolved let's encrypt error ipv6

    That's awesome. Appreciate that!
  2. A

    Resolved let's encrypt error ipv6

    Glad I could help.
  3. A

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

    I had setup DNSSEC in Cloudflare and on the Registrar for the domain, but hadn't added the DS record to the DNS zone in Plesk. I've done that now and still receive the same error when saving the Hosting Settings.
  4. A

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

    In Plesk Obsidian 18.0.61 Update 6 running on Debian 10 we are getting the error 'JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 23643 of the JSON data' while saving the settings in the Hosting Settings for a Domain. We were updating a Dedicated IP for a domain...
  5. A

    Resolved let's encrypt error ipv6

    I appreciate that Tony. I am glad I was able to help. I have to admit this has given me a lot of grief as a service provider until I figured it out.
  6. A

    Resolved Please Migrator critical error

    I actually discovered the answer a different way, but totally appreciate the answer you provided and will use it next time. When the server credentials were provided for the hardware they only give DEBIAN or UNIX users, so I actually ended up creating a named ROOT user and it worked. Thank you...
  7. A

    Resolved Please Migrator critical error

    Is there any further help on this? I have the same issues, both logins from source and destination are root and it's been nothing but issues trying to migrate sites. This is a critical task that needs to work. Failed to fetch basic information about resellers, clients and domains data from...
  8. A

    Resolved Immunify360 and iptables version

    UPDATE: SOLVED using this article: https://cloudlinux.zendesk.com/hc/e...lation-process-iptables-required-on-Debian-10 Thank you for your help!
  9. A

    Resolved Immunify360 and iptables version

    This didn't work for me, I get the error below. E: The value 'buster-backports' is invalid for APT::Default-Release as such a release is not available in the sources
  10. A

    Issue Plesk Docker OwnCloud: how to migrate from "devicemapper" to "overlay2"?

    Is this still an issue and did you ever find a fix?
  11. A

    Issue Domain Connect + Cloudflare fails with a 404

    How do you get helpful posts without being able to post? Why pay for a product and support when the support requests are unable to be posted. Sigh.
  12. A

    Issue Domain Connect + Cloudflare fails with a 404

    Have tried and get this error on the site when attempting to do so. Oops! We ran into some problems. You do not have...
  13. A

    Issue Domain Connect + Cloudflare fails with a 404

    Bump. Same issue...
  14. A

    Resolved let's encrypt error ipv6

    This is due to Cloudflares SSL Setup. In order to get rid of the added and hidden AAAA records, goto the SSL/TLS Tab of the domain (IN CLOUDFLARE) and change your setting from FLEXIBLE to FULL. Then proceed with your SSL setup and you should be good.
Back
Top