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

Search results

  1. A

    Resolved REST API /api/v2/cli/* returns 404

    Solved.... after playing around, the trailing slash was the issue. No clue why it changed, could be something else than the new IP, such a change in PHP version of the script calling the API... In brief: https://<IP_ADDRESS>:8443/api/v2/cli/commands/ returns 404...
  2. A

    Resolved REST API /api/v2/cli/* returns 404

    Hi, Since I migrated my Plesk vm to a new IP, I realized the REST API calls to CLI returns 404: https://<IP_ADDRESS>:8443/api/v2/cli/commands/ returns 404 https://<host.domain.tld>:8443/api/v2/cli/commands/ returns 404 command curl -k -u 'admin:password' -X GET...
  3. A

    Resolved xml api creat role for user deprecated

    https://IP_ADDRESS:8443/api/v2/cli/user/call now returns 404... based on the Swagger, there's no more user/call... Any alternative?
  4. A

    Resolved a recurrent task generating a lot of IO delays

    Thx!
  5. A

    Question vhostmng-find processe consume CPU

    Same question here. Anyone knows?
  6. A

    Resolved a recurrent task generating a lot of IO delays

    Hi, Just running into some IO delays on daily basis, and I can see this command being run on my Plesk box (CentOS Linux 7.9.2009 & Plesk Obsidian Version 18.0.39 Update #2) Would anyone know what it's related to? I could not find what is triggering this command so far. The only page I could...
  7. A

    Issue dovecot fts_squat is deprecated - how to activate full text search?

    Hi Benjamin, Did you ever had a chance to find an answer to this question? I'll be also interested in enabling full text search in dovecot. Seen as well a plugin for elasticsearch: https://github.com/filiphanes/fts-elastic Let me know.
  8. A

    Question Error: Failed to update the ModSecurity rule set

    FYI - waf.comodo.com authentification is now working fine - I just got an email from their support team and tried, and all back to normal. Nevertheless, latest update of their WAF rules is November 2020. So not so fresh.
  9. A

    Question Error: Failed to update the ModSecurity rule set

    @Peter Debik I've now tried to switch to Atomic Basic ModSecurity, but there are no rules.... it's like empty. When I navigate to the WAF settings under a domain, it doesn't allow to browse the rules to exclude some of them for instance. The rules are empty. Nevertheless, in the logs, I could...
  10. A

    Question Error: Failed to update the ModSecurity rule set

    Thx Peter - I have also checked on the comodo forum and others encountered the same issue - definitely seems to be on Comodo side...
  11. A

    Question Error: Failed to update the ModSecurity rule set

    Hi, Since early this week, I get the following message once logged into Plesk: Error: Failed to update the ModSecurity rule set I've double-checked login/password, all looks good but it keeps failing. I have also noted that I can't login anymore to Free ModSecurity Rules from Comodo I even have...
  12. A

    Issue Unable to download comodo rule set

    Hi, Same here since beginning of June. Unsure if it's related to Plesk. Any idea? Thx
  13. A

    Resolved xml api set user locale language

    Ended up with this and it works well: curl -k -X POST -u 'admin:PaSSword' "https://IP_ADDRESS:8443/api/v2/cli/user/call" -H "accept: application/json" -H "Content-Type: application/json" -d '{ "params": [ "-c", "myUsername", "-role", "myRole", "-passwd", "PaSSword!", "-cname", "myName"...
  14. A

    Resolved xml api creat role for user deprecated

    Yep, ended up with this and it works well: curl -k -X POST -u 'admin:PaSSword' "https://IP_ADDRESS:8443/api/v2/cli/user/call" -H "accept: application/json" -H "Content-Type: application/json" -d '{ "params": [ "-c", "myUsername", "-role", "myRole", "-passwd", "PaSSword!", "-cname", "myName"...
  15. A

    Resolved xml api creat role for user deprecated

    Encountering same issue here - was used to the user/add packet through XML API. Any alternative?
  16. A

    Resolved xml api set user locale language

    That's my conclusion too. Thx
  17. A

    Resolved xml api set user locale language

    @IgorG thx, that's a great alternative. So do we confirm that for Plesk prior to Onyx 17.8, where only XML API is available, there's no way to set the language of a user?
  18. A

    Resolved xml api set user locale language

    Hi, any update on how to set the language of a user through the XML API? Thx
  19. A

    Question Restrict FTP access by IP / user

    Actually I found the way to make it work - perfectly working with Plesk Onyx - content of the .ftpaccess file: <Limit ALL> Order allow, deny Allow from 127.0.0.1 Allow from IP1 Allow from IP2 Allow from IP3 DenyAll </Limit>
  20. A

    Preferred Domain Setting through RPC API

    and in case you want to set the non-www domain as preferred, such as domain.tld (and not www.domain.tld), you have to use property non-www: <property> <name>seo-redirect</name> <value>non-www</value> </property>
Back
Top