• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Recent content by KeTa

  1. K

    Resolved Extension catalog doesn't show

    actually on my cloud provider the template "AlmaLinux OS 8.x 64-bit - Plesk" is also available. At this point I could eliminate the one with CentOS 7 and start from scratch with AlmaLinux. AlmaLinux is an OS that I have never used. Does using it with Plesk require the same hardware resources as...
  2. K

    Resolved Extension catalog doesn't show

    first, thank you so much for replying with all the steps ♥ updating that server scares me terribly .. :p as well as its reboot hahaha Hasn't been restarted for 4 years. Is a production server with around 30 web / mail domains. I would not like running all updates to lead to incompatibilities...
  3. K

    Resolved Extensions: Internal server error

    unfortunately it was not enough to solve the problem
  4. K

    Resolved Extension catalog doesn't show

    i have the same problem, but unfortunately your method didn't work [root@plesk ~]# sed -i 's/mozilla\/DST_Root_CA_X3.crt/!mozilla\/DST_Root_CA_X3.crt/g' /etc/ca-certificates.conf sed: can't read /etc/ca-certificates.conf: No such file or directory [root@plesk ~]# wget Plesk Extensions...
  5. K

    Resolved Extensions: Internal server error

    I have the same problem and YES I see certificate error. What can I do to solve the problem? [root@plesk ~]# wget Plesk Extensions --2022-04-28 20:25:09-- Plesk Extensions Resolving ext.plesk.com... 212.102.55.131, 212.102.55.139, 2a02:6ea0:d500::5, ... Connecting to...
  6. K

    Resolved Extensions: Internal server error

    I have the same problem and YES I see certificate error. What can I do to solve the problem? :( [root@plesk ~]# wget Plesk Extensions --2022-04-28 20:25:09-- Plesk Extensions Resolving ext.plesk.com... 212.102.55.131, 212.102.55.139, 2a02:6ea0:d500::5, ... Connecting to...
Back
Top