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

Recent content by MrSpock

  1. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    Since the issue could not be solved with all the advices I found here or in other places, I selected to change to a "dedicated server with limited available hardware" so that the price was only 4€ more per month compared to my V-Server. On the new dedicated server I installed ubuntu22 and the...
  2. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    Hi Peter, I checked with my provider Strato. My Plesk licence is not eligible for direct plesk support and Strato cannot help to solve specific problems. I have a V-Server with Strato and it was initially used with ubuntu 16. So I used the plesk description for upgrading the operating system in...
  3. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    Hello Peter, Unfortunately this did not solve the problem, I still have (among others) the No_Pubkey error mainly for BD11A6AA914BDF7E
  4. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    It seems that especially the key BD11A6AA914BDF7E cannot be found. I tried several keyservers. But I only receive the error „No Data“ apt-key adv --keyserver keys.openpgp.org --recv-keys BD11A6AA914BDF7E Executing: /tmp/apt-key-gpghome.0cRFlEpseY/gpg.1.sh --keyserver keys.openpgp.org --recv-keys...
  5. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    Sorry, I didn't see this explanation: Err:1 http://autoinstall.plesk.com/pool/PHP_7.1.33_96 focal InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E Hit:8 http://autoinstall.plesk.com/NODE_0.0.2 all InRelease Get:9...
  6. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    Hello Peter, I tried the sequence: First error is still the same:
  7. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    in the log file or the error file that I showed above is no keyserver mentioned so I tried: do I have to use another keyserver?
  8. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    continued: after several additional warnings and another ftp disabled error, the installation fails due to: The last two error message quotes are identical to those I receive when I try to install th version through the admin panel. I have attached the full error log in the first post of this...
  9. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    I started the installer with the above shown command. The installer then tried to install plesk 18.0.44, which is already installed. I want to upgrade to 18.0.51. So I followed the instruction on Plesk documentation: Upgrade von Plesk für Linux mithilfe der Installationskonsole There it says to...
  10. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    I tried to manually update my ubuntu server and see that the initial messages after: is I checked the autoinstall.plesk.com and in fact there is no PSA_18.0.44 folder, but it starts only with PSA_18.0.45. That might be the reason, for my plesk upgrade from 18.0.44 to 18.0.51 cannot find...
  11. M

    Resolved Error updating from 18.0.44 to 18.0.51 on ubuntu 20

    When trying to update from version 18.0.44 to 18.0.51 an error occurs. I also tried to update via the console, but the same error occurs also there. What can I do to successfully upgrade? The error log is attached.
Back
Top