• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by umarkhan

  1. U

    Issue Plesk not synchronizing with route53

    I created the hosted zones manually in route 53 with TTL of my choice. Then I made delegation set as default and synced all the domains in plesk to route53. Keep in mind, I don't have Manage NS and SOA records on. Then all the records were synced successfully
  2. U

    Issue 2 Post migration error

    [Post-migration checks] The HTTP status code of a web page has changed after the migration. The status code returned by the server '1xx.xx.xx.xxx': '301' The status code returned by the server '3x.xxx.xxx.x': '500' The web page URL: 'xxx.com' A changed HTTP status code might signify either the...
  3. U

    Resolved Migration from Plesk 11..0.9 to Onyx (17.0.5 stable)

    Did you solve this, If Yes, how?
  4. U

    Resolved Migration from Plesk 11..0.9 to Onyx (17.0.5 stable)

    Did you solve this, If Yes, how? Thanks in advance
  5. U

    Issue Plesk not synchronizing with route53

    Yes, I have enabled it
  6. U

    Issue Plesk not synchronizing with route53

    I created hosted zones using delegation sets in Route53 for my domains in plesk. I installed Route53 extension in Plesk and and when I performed a synchronization from plesk, hosted zones were created in route53 and had different NS records for each zone.
  7. U

    Resolved Problem with migrating from Plesk ubuntu to Plesk ubuntu

    Thank you so much!!! that solved the problem
  8. U

    Resolved Problem with migrating from Plesk ubuntu to Plesk ubuntu

    I am using ecc2 instances for Plesk and want to migrate customers from one Plesk server to to another but the keys are not able to be authorized. By default you don't have private keys stored in an ec2 instance and public keys are stored in /root/.ssh/authorized_keys and tried the public keys...
Back
Top