• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Automated plesk updates failed for HTTPS.

NetProducts

New Pleskian
Hello,

Automatic plesk updates fail for the panel it self.
Debian-based packages install fine, so the update service is functioning correctly.
Problem: plesk downloads a binary or archive file from a HTTP-based domain, not via SSL like the apt/dpkg tools do.
Likely cause: Our enterprise firewall does not like this. Probably because of the mitm vulnerability possibilities regarding sending executable files over unsecured connections and then automatically starting them as a privileged user.

The line in the relevant log file reads:

E: Failed to fetch http://autoinstall.plesk.com/debian/PSA_17.5.3/../../PSA_17.5.3/dist-deb-Debian-8.0-x86_64/base/psa-updates_17.5.3-debian8.0.build1705170810.18_all.deb Connection failed

Interestingly, Index of /PSA_17.5.3/dist-deb-Debian-8.0-x86_64/base exists and contains the file it wants. Manually downloading it and running it would resolve the current problem, but the real question is:

Can we, and if so, how do we reconfigure Plesk Onyx for Linux so it uses the https:// version of the domain?


Note: I've used the linux 'find' utility to try to find where this path is stored, but complicated XML files and executables turn up.
 
Hi NetProducts,

Can we, and if so, how do we reconfigure Plesk Onyx for Linux so it uses the https:// version of the domain?
The standart configuration for your sources.lists is always the "http" - source, while you are certainly able to add additional sources.list with "https".

Running the command ( logged in as user "root" over SSH ):
Code:
plesk installer --select-product-id plesk --select-release-current --reinstall-patch --install-component base
will force Plesk to temporarily create the needed Plesk sources inside the folder "/etc/apt/sources.list.d" on Debian/Ubuntu based systems, which you are able to copy to your very own and unique Plesk sources.list, editing the sources as "https" instead of "http".
 
Back
Top